Ouss4 commented on PR #5966:
URL: https://github.com/apache/incubator-nuttx/pull/5966#issuecomment-1092850402
@zhuyanlinzyl
Since you have revision-1 of ESP32-C3, can you check if the correct efuse is
burnt:
(this is required for revision-1 since the internal USB-JTAG is
non-functional).
```sh
$ espefuse.py --port /dev/ttyXXX summary | grep JTAG
JTAG_SEL_ENABLE (BLOCK0) Set this bit to enable
selection between usb_to_jt = False R/W (0b0)
SOFT_DIS_JTAG (BLOCK0) Software disables JTAG.
When software disabled, JT = 0 R/W (0b000)
DIS_PAD_JTAG (BLOCK0) Permanently disable JTAG
access via pads. USB JTAG = False R/W (0b0)
DIS_USB_JTAG (BLOCK0) Disables USB JTAG. JTAG
access via pads is control = True R/W (0b1)
```
If `DIS_USB_JTAG` is false, then you can burn it with: `espefuse.py -p
/dev/ttyXXX burn_efuse DIS_USB_JTAG`
To be honest the issue you are having doesn't seem to be related to the
efuse, as I see that JTAG was initialized and the chip was detected correctly.
However, I see those stacking errors, did you add those logs or are they
already there?
If the issue is from FreeRTOS, you can disable that by running OpenOCD like:
`openocd -c 'set ESP_RTOS none' -f board/esp32c3-ftdi.cfg`
Note however if you want to try debug awareness, it's still not in the repo.
Actually, there isn't even RISC-V stacking info. I have it in my local copy
along changes to use `g_tcbinfo` and `g_pidhash`, coincidently I'm seeing some
issues with ESP32-C3 as well (not sure if it's related to ESP32-C3 or I got the
RISC-V stacking incorrect somehow):
```
$ riscv64-unknown-elf-gdb nuttx
(gdb) target extended-remote :3333
(gdb) c
(gdb) info threads
Id Target Id Frame
* 1 Thread 1070088200 "Idle Task" (Name: Idle Task, pid:0, RUNNING)
up_idle () at chip/esp32c3_idle.c:265
2 Thread 1070145128 "lpwork" (Name: lpwork, pid:1, WAIT_SEM)
0x3fc92108 in ?? ()
3 Thread 1070148120 "nsh_main" (Name: nsh_main, pid:2, WAIT_SEM)
0x3fc92cb8 in ?? ()
4 Thread 1070151352 "rt_timer" (Name: rt_timer, pid:3, WAIT_SEM)
0x3fc93958 in ?? ()
5 Thread 1070155832 "wifi" (Name: wifi, pid:4, WAIT_MQNOTEMPTY)
0x3fc94ad8 in ?? ()
```
Trying to figure out issues with the backtrace of tasks other than the Idle.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
