You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/ApplicationUserGuide.md
+9-3Lines changed: 9 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -87,7 +87,7 @@ The NDP120 is configured by identifying the firmware images that will be loaded
87
87
88
88
-[Video Link (3 minutes)](http://avnet.me/RASynChangingMlModelsVideo)
89
89
90
-
There are two areas in the config.ini file to configure which NDP120 files are loaded to the NDP120 at startup.
90
+
There are two areas in the config.ini file to configure which NDP120 files/model(s) are loaded to the NDP120 at startup.
91
91
92
92
1.```[NDP Firmware]-->Mode=x```
93
93
@@ -101,6 +101,11 @@ Each ```[Function_x]``` block defines a description, and the three required NDP1
101
101
-```MCU``` refers to the ARM-M0 firmware that runs on the NDP120. This firmware manages the devices and data flow.
102
102
-```DSP``` refers to the dsp firmware that runs on the NDP120. This firmware does data pre-processing plus other functions.
103
103
-```DNN``` refers to the Nerual Network Parameters and ML model. This firmware implements the ML model.
104
+
-```Event_Watch_Mode``` tells the NDP120 what data streams to watch and needs to align with the model defined in the ```DNN``` entry.
105
+
- 1 == Audio
106
+
- 2 == IMU
107
+
- 3 == Combined Audio & IMU data
108
+
104
109
105
110

106
111
@@ -131,9 +136,10 @@ There are two different ways to redefine the decimation_inshift vaules at startu
131
136
132
137

133
138
134
-
135
139
## LED control
136
-
The ```[LED]``` block allows the user to assign different RGB LED colors to each inference index. When the NDP120 detects a feature in the data the inference results are passed to the application. The application uses the index of the inference result [0 - n] to identify how to light the RGB LED on the I/O board. The comments in the config.ini file associate each index with the 5-keyword model, but this feature works with any model that's loaded.
140
+
The ```[Led Network x]``` blocks allow the user to assign different RGB LED colors to each neural network and inference index. When the NDP120 detects a feature in the data the network number and inference results are passed to the application. The application uses the
141
+
neural network number and the index of the inference result [0 - n] to identify how to light the RGB LED on the I/O board. The comments
142
+
in the config.ini file associate each index with the 5-keyword model, but this feature works with any model that's loaded.
137
143
138
144
-[Video Link (3 minutes)](http://avnet.me/RASynChangeLedColorsVideo)
Copy file name to clipboardExpand all lines: releaseNotes.md
+21Lines changed: 21 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,24 @@
1
+
## Version: 1.6.1
2
+
Release type: **Feature Release**
3
+
4
+
Date: June 25, 2024
5
+
6
+
## Note: The V1.6.1 release is compatible with Edge Impulse Models generated after June 10th 2024
7
+
8
+
### New Features
9
+
- AAGBT-166: Add config.ini support to identify how the NDP120 pulls in data for each model (audio, IMU, or audio & IMU)
10
+
- AAGBT-168: Add config.ini support to identify which LED color lights by neural network number and inference index
11
+
12
+
### Bug Fixes
13
+
None
14
+
15
+
### Known Issues
16
+
- AAGBT-165: When capturing IMU data converted from ADC values to accelerometer and gyro units to debug sometimes the application hangs. This appears to be a floating point printf() issue and is currently masked by reducing the floating point precision to 3 places. For full precision data, please capture converted IMU data to the microSD card file system.
17
+
- AAGBT-159: The EVK does not power up with powered by just a battery. See [troubleshooting guide](https://github.com/Avnet/RASynBoard-Out-of-Box-Demo/blob/rasynboard_v2_tiny/docs/RASynTroubleshootingGuide.md#the-rasynboard-evk-io-board--core-board-does-not-power-up-when-using-just-a-lipo-battery) for a work around
18
+
- AAGBT-159: When powering EVK from a battery the RGB LEDs are not powered. See [troubleshooting guide](https://github.com/Avnet/RASynBoard-Out-of-Box-Demo/blob/rasynboard_v2_tiny/docs/RASynTroubleshootingGuide.md#the-rasynboard-evk-io-board--core-board-does-not-power-up-when-using-just-a-lipo-battery) for a hardware work around
19
+
- AAGBT-105: When using a custom BLE name, the OOB application is not able to connect to the Python GUI demo application
20
+
- AAGBT-123: When capturing audio, or IMU data if there is an issue receiving data from the NDP120 the application hangs
0 commit comments