Hello,
I have flashed the nRF5340-dk with the official edge impulse firmware, both using nRF Programmer and just drag&drop. The device answers in the COM3 port when resetting, so the UART seems to work, at least in TeraTerm. However, the edge-impulse-daemon cli doesnt seem to work, while the edge-impulse-data-forwarder seems to work :
C:>edge-impulse-daemon
Edge Impulse serial daemon v1.31.0
Endpoints:
Websocket: wss://remote-mgmt.edgeimpulse.**com
API: https://studio.edgeimpulse.**com
Ingestion: https://ingestion.edgeimpulse.*com
? Which device do you want to connect to? COM3 (Microsoft)
[SER] Connecting to COM3
[SER] Serial is connected, trying to read config…
[SER] Failed to get info off device Timeout when waiting for > (timeout: 5000) onConnected
C:>edge-impulse-data-forwarder
Edge Impulse data forwarder v1.31.0
Endpoints:
Websocket: wss://remote-mgmt.edgeimpulse.com
API: https://studio.edgeimpulse.com
Ingestion: https://ingestion.edgeimpulse.*com
? Which device do you want to connect to? COM3 (Microsoft)
[SER] Connecting to COM3
[SER] Serial is connected (00:10:50:01:96:62)
[WS ] Connecting to wss://remote-mgmt.edgeimpulse.com
[WS ] Connected to wss://remote-mgmt.edgeimpulse.com
? To which project do you want to connect this device? (Use arrow keys)
I have now tested this with 2 PC’s with 2 different cables, installing and reinstalling the cli. I also tested with another nRF5340-dk. It came to mind that is the prebuilt firmware up to date? Have someone else encountered the some problem?
I have not tested to build the firmware myself.
Project ID:
Haven’t got this far…
Steps Taken:
Reproducibility:
- [x ] Always
- [ ] Sometimes
- [ ] Rarely