Ok. the problem is that resetting the firmware also reset the nonce sent from the Lora to the TTS server and the server refuse the join because the nonce now is lower than that in the server db…
SicheoSrl
Posts
-
Building the firmware from source -
Building the firmware from sourceI was testing my F1 starter kit since May. everything worked fine (LTE, Lora).
Yesterday I made a complete erase of flash (because the board was hanging) with./fw_builder.sh --board SGW3501-F1-StarterKit flash --port /dev/ttyUSB0
and reflash teh firmware with
./fw_builder.sh --board SGW3501-F1-StarterKit flash --port /dev/ttyUSB0
from then on the Lora radio was unable to join…do have I erased some Lora parameter?
-
Communication with external USB deviceI solved my issue using the UART directly from the Pins P21(TX) and P22(RX). I’ve also deduped UART 1 and use it to communicate with my peripheral.
To monitor with the REPL I’m using /dev/ttyACM0 (Ubuntu system) -
Communication with external USB deviceBy default, MicroPython firmware configures J202 in device mode with an alternate serial REPL.
I would like to disable the REPL on the J202 port and use that USB port to talk to a device (probably in udp)
I tried to disable the REPL using micropython:- I loaded a boot.py file with os.dupterm(None,1)
- I loaded main.py script with uart_usb = machine.UART(0, baudrate=115200)
- I rebooted the board
- I opened a terminal with screen /dev/ttyACM0 115200
The problem is that when I try to call the:
uart_usb = machineUART(0,baudrate=115200)
I get the following error
Guru Meditation Error: Core 1 panic’ed (Interrupt wdt timeout on CPU1).
Core 1 register dump:
PC : 0x40376868 PS : 0x00050034 A0 : 0x4212a396 A1 : 0x3fca2790
A2 : 0x00000208 A3 : 0x3fcf4b80 A4 : 0x40379f50 A5 : 0x3fca2770
A6 : 0x60000000 A7 : 0x00050021 A8 : 0x82014f05 A9 : 0x403845f2
A10 : 0x00060123 A11 : 0x00000000 A12 : 0x00000000 A13 : 0x00000100
A14 : 0x00060023 A15 : 0x00000001 SAR : 0x0000001d EXCCAUSE: 0x00000006
EXCVADDR: 0x00000000 LBEG : 0x00000000 LEND : 0x00000000 LCOUNT : 0x00000000
Core 1 was running in ISR context:
EPC1 : 0x4212aa47 EPC2 : 0x00000000 EPC3 : 0x00000000 EPC4 : 0x40376868
Backtrace: 0x40376865:0x3fca2790 0x4212a393:0x3fcf4b80 0x4201af13:0x3fcf4ba0 0x40385750:0x3fcf4bc0
Core 0 register dump:
PC : 0x4212a396 PS : 0x00060e34 A0 : 0x8201af16 A1 : 0x3fcf4420
A2 : 0x3fca6958 A3 : 0x00060e20 A4 : 0x00060420 A5 : 0x3fcf3930
A6 : 0x00ffffff A7 : 0x00000003 A8 : 0x82014f05 A9 : 0x3fcf4410
A10 : 0x00060e23 A11 : 0x00000000 A12 : 0x00060e20 A13 : 0x3fcf4330
A14 : 0x00060023 A15 : 0x00000003 SAR : 0x0000001d EXCCAUSE: 0x00000006
EXCVADDR: 0x00000000 LBEG : 0x00000000 LEND : 0x00000000 LCOUNT : 0x00000000