Devide ID/EUI is 0000000000000000 on new xDot

Home Forums mDot/xDot Devide ID/EUI is 0000000000000000 on new xDot

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #30728
    Oliver
    Participant

    Hello,
    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 of display_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 LoRaWAN
    

    Thank you for your help.
    Oliver

    #30734
    Jason Reiss
    Keymaster

    Did 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&WP

    #30755
    Oliver
    Participant

    I did erase it with an ST-LINK tool.
    I’ve tried now flashing the AT firmware xdot-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 Ready
    

    Though after that does not allow any inputs.
    Am I missing something?

    Thank you!

    #30756
    Jason Reiss
    Keymaster

    OK, 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?

    #30781
    Oliver
    Participant

    Ah, 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 3 years, 10 months ago by Oliver.
    #30783
    Jason Reiss
    Keymaster

    UART1 PA9/10 is the at command port.

    https://github.com/ARMmbed/mbed-os/blob/master/targets/TARGET_STM/TARGET_STM32L1/TARGET_XDOT_L151CC/PinNames.h

    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.h

    The 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.

    #30815
    Oliver
    Participant

    I contacted support and they were able to build me a UART0 firmware within a few hours. Awesome.
    Thanks a lot for your help Jason.

Viewing 7 posts - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.