Devide ID/EUI is 0000000000000000 on new xDot
- This topic has 6 replies, 2 voices, and was last updated 5 years, 5 months ago by
Oliver.
-
AuthorPosts
-
June 15, 2020 at 7:41 am #30728
Oliver
ParticipantHello,
Currently having an issue with a new custom xDot breakout board I have just completed. When getting the device ID/EUI using a slightly modified version of the OTA config, the id is returned as 0.
Is there anything I’m doing wrong, this should be set at factory I thought?
This is the output ofdisplay_config();[INFO] ===================== [INFO] general configuration [INFO] ===================== [INFO] version ------------------ 3.2.5-mbed51304 [INFO] device ID/EUI ------------ 0000000000000000 [INFO] default channel plan ----- AU915 [INFO] current channel plan ----- AU915 [INFO] frequency sub band ------- 2 [INFO] public network ----------- Public LoRaWANThank you for your help.
OliverJune 15, 2020 at 9:24 am #30734Jason Reiss
KeymasterDid you happen to erase the flash with a ST-LINK tool?
https://github.com/MultiTechSystems/Dot-AT-Firmware
The xDot debug firmware can be used to set the devEUI
AT+DI=0011223344556677
AT&WPJune 17, 2020 at 3:41 am #30755Oliver
ParticipantI did erase it with an ST-LINK tool.
I’ve tried now flashing the AT firmwarexdot-firmware-3.3.5-AU915-mbed-os-5.15.1-debug, though when I open the serial monitor I’m unable to send any commands. It initially prints[INFO] Set radio to Public Mode [INFO] xDot ReadyThough after that does not allow any inputs.
Am I missing something?Thank you!
June 17, 2020 at 8:15 am #30756Jason Reiss
KeymasterOK, the ST-Link tool will erase the entire flash which contains the application and the eeprom configuration data. That explains the deveui of 00’s.
It looks like you have the debug serial port connected.
There is another serial port for entering commands, do you only have access to the other serial ports or only the debug pins?
June 20, 2020 at 8:44 pm #30781Oliver
ParticipantAh, right – wasn’t aware I could overwrite that.
I currently have SWDIO/SWCLK, UAR0T_TX/UART0_RX, GND, VCC and NRESET connected. Is that all that is required?Thank you very much
-
This reply was modified 5 years, 5 months ago by
Oliver.
June 21, 2020 at 9:47 am #30783Jason Reiss
KeymasterUART1 PA9/10 is the at command port.
Thr deveui is at the beginning of the flash eeprom section. An xdot eeprom api can be used to restore.
https://github.com/ARMmbed/mbed-os/blob/master/targets/TARGET_STM/TARGET_STM32L1/TARGET_XDOT_L151CC/xdot_eeprom.hThe 3.3.5 version of library will allow setting and saving deveui to the “protected” config.
Or contact support.multitech.net for an at cmd firmware working on the debug port.
June 24, 2020 at 6:00 pm #30815Oliver
ParticipantI contacted support and they were able to build me a UART0 firmware within a few hours. Awesome.
Thanks a lot for your help Jason. -
This reply was modified 5 years, 5 months ago by
-
AuthorPosts
- You must be logged in to reply to this topic.