Searched refs:layers (Results 1 – 25 of 38) sorted by relevance
12
| /Zephyr-latest/samples/modules/tflite-micro/magic_wand/train/ |
| D | train.py | 53 tf.keras.layers.Conv2D(
58 tf.keras.layers.MaxPool2D((3, 3)), # (batch, 42, 1, 8)
59 tf.keras.layers.Dropout(0.1), # (batch, 42, 1, 8)
60 tf.keras.layers.Conv2D(16, (4, 1), padding="same",
62 tf.keras.layers.MaxPool2D((3, 1), padding="same"), # (batch, 14, 1, 16)
63 tf.keras.layers.Dropout(0.1), # (batch, 14, 1, 16)
64 tf.keras.layers.Flatten(), # (batch, 224)
65 tf.keras.layers.Dense(16, activation="relu"), # (batch, 16)
66 tf.keras.layers.Dropout(0.1), # (batch, 16)
67 tf.keras.layers.Dense(4, activation="softmax") # (batch, 4)
[all …]
|
| /Zephyr-latest/modules/cmsis-nn/ |
| D | Kconfig | 19 This option enables the NN libraries for the activation layers
20 It can perform activation layers, including ReLU (Rectified
32 This option enables the NN libraries for the concatenation layers.
57 This option enables pooling layers, including max pooling,
63 This option enables the NN libraries for the reshape layers.
68 This option enables the NN libraries for the softmax layers (exp2 based).
74 This option enabled the NN libraries for Single Value Decomposition Filter layers.
|
| /Zephyr-latest/doc/services/portability/ |
| D | index.rst | 6 OS abstraction layers (OSAL) provide wrapper function APIs that
11 These sections describe the software and hardware abstraction layers
|
| /Zephyr-latest/doc/connectivity/bluetooth/ |
| D | index.rst | 8 operation of the layers and how they were implemented.
|
| D | bluetooth-arch.rst | 18 .. _bluetooth-layers:
23 There are 3 main layers that together constitute a full Bluetooth Low Energy
59 The three separate layers of the protocol and the standardized interface make
64 implements all three layers and the application itself. This can also be called a
92 include only the features and layers that are required to reduce RAM and ROM
|
| D | features.rst | 35 * Conformance tests run regularly on all layers (Controller and Host, except
|
| D | bluetooth-le-host.rst | 9 layers of the host.
13 :alt: Bluetooth Host protocol & profile layers
15 Bluetooth Host protocol & profile layers.
|
| /Zephyr-latest/doc/develop/west/ |
| D | sign.rst | 24 all these layers can causes issues typical when the layers don't abstract
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | w1.rst | 38 In Zephyr this API is split into the following layers.
88 Functions that are not directly related to any of the networking layers.
|
| /Zephyr-latest/subsys/mgmt/ec_host_cmd/ |
| D | Kconfig | 33 Some backend layers can define their own buffer, so the size can be zero to
46 Some backend layers can define their own buffer, so the size can be zero to
|
| /Zephyr-latest/subsys/sip_svc/ |
| D | Kconfig | 74 layers using SMC/HVC calls.
|
| /Zephyr-latest/samples/modules/tflite-micro/hello_world/train/ |
| D | README.md | 57 simple feed forward deep neural network with 2 fully connected layers with
|
| /Zephyr-latest/samples/modules/thrift/hello/ |
| D | README.rst | 9 .. figure:: thrift-layers.png
48 layers in thrift can be combined to build an application with desired features.
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | ieee802154.rst | 84 network layers (L3+), its socket and network context abstractions. This API is
|
| D | net_l2.rst | 18 The upper layers are unaware of implementation details beyond the net_if
26 Currently, there are L2 layers for :ref:`Ethernet <ethernet_interface>`,
|
| D | net_mgmt.rst | 78 Note that in order to receive events from multiple layers, one must have
|
| /Zephyr-latest/doc/connectivity/networking/ |
| D | net-stack-architecture.rst | 13 for Zephyr OS. It consists of layers, each meant to provide certain services
14 to other layers. Network stack functionality is highly configurable via Kconfig
|
| D | overview.rst | 143 Additionally these network technologies (link layers) are supported in
|
| /Zephyr-latest/tests/bsim/bluetooth/mesh/ |
| D | README.rst | 118 avoid regressions on changes in the underlying layers.
|
| /Zephyr-latest/doc/services/device_mgmt/ |
| D | ec_host_cmd.rst | 33 host. SHI does not have API itself, thus the backend and peripheral driver layers are combined into
|
| /Zephyr-latest/drivers/modem/ |
| D | Kconfig | 152 API calls through the command handler call back layers).
|
| /Zephyr-latest/doc/services/pm/ |
| D | device.rst | 27 influenced by higher layers of the software stack.
31 layers because the subsystem uses reference count to check when it needs
|
| /Zephyr-latest/doc/safety/ |
| D | safety_overview.rst | 198 into layers. As a result, each layer can be assigned a specific role in the system. This model has
199 the advantage in safety that interfaces between different components and layers can be shown at a
|
| /Zephyr-latest/boards/ti/cc3220sf_launchxl/doc/ |
| D | index.rst | 17 internet logical layers
|
| /Zephyr-latest/boards/native/doc/ |
| D | arch_soc.rst | 15 provide the foundation, architecture and SOC layers for a set of virtual test
337 :ref:`inf_clock<posix_arch_design_socl>` SOC layers.
|
12
