Forum Replies Created
-
AuthorPosts
-
FrankParticipant
My program exceeded 1M specified in the default partition table, writing a partition csv and generating a binary from that and editing esp32.xml to specify the correct partition table file solved my problems.
http://esp-idf.readthedocs.io/en/latest/partition-tables.html
Thanks anyway.
FrankParticipantI’ve turned on verbose mode for the linker. BuildLinkerOut
1> attempt to open ../../../../../../SysGCC/esp32/esp32-bsp/esp-idf/components/esp32/lib\librtc.a succeeded
1> (../../../../../../SysGCC/esp32/esp32-bsp/esp-idf/components/esp32/lib\librtc.a)bt_bb.o
1> (../../../../../../SysGCC/esp32/esp32-bsp/esp-idf/components/esp32/lib\librtc.a)pm.o
1> (../../../../../../SysGCC/esp32/esp32-bsp/esp-idf/components/esp32/lib\librtc.a)rtc_analog.o
1> (../../../../../../SysGCC/esp32/esp32-bsp/esp-idf/components/esp32/lib\librtc.a)rtc.o
1> (../../../../../../SysGCC/esp32/esp32-bsp/esp-idf/components/esp32/lib\librtc.a)rtc_clk.o
1> (../../../../../../SysGCC/esp32/esp32-bsp/esp-idf/components/esp32/lib\librtc.a)rtc_cntl.o
1> (../../../../../../SysGCC/esp32/esp32-bsp/esp-idf/components/esp32/lib\librtc.a)rtc_command.oI’ve run the nm.exe nm output Line 102 contains the function I’d like to call.
00000040 T temprature_sens_read
From rtc_analog.o:
FrankParticipantThanks!
FrankParticipantnot working logs: http://pastebin.com/AUYRLb2g
working logs: http://pastebin.com/AUYRLb2g
diff: http://pastebin.com/AUYRLb2git seems only cpu0 has halted in the notworking logs?
I would really like to figure this one out, manually halting and programming is becoming a pain.
FrankParticipantThe same does not happen when adding the code to “LEDBlink” example project.
1> ------------------- Memory utilization report ------------------- 1> Used DATA_FLASH: 43KB out of 8192KB (0%) [-1644] 1> Used INSTR_FLASH: 167KB out of 3264KB (5%) [-38K] 1> Used INSTR_RAM: 77KB out of 128KB (60%) [-1624] 1> Used DATA_RAM: 21KB out of 320KB (6%) [-712]
The same does however happen with the BLE Advertisement example project.
1> ------------------- Memory utilization report ------------------- 1> Used DATA_FLASH: 213KB out of 8192KB (2%) [+196] 1> Used INSTR_FLASH: 774KB out of 3264KB (23%) [+1544] 1> Used INSTR_RAM: 90KB out of 128KB (70%) [+148] 1> Used DATA_RAM: 64KB out of 320KB (20%) [+136]
FrankParticipantthis error occurs during the flashing of the device and does not succeed.
Screenshot:
https://1drv.ms/i/s!ArGQV6ObDq-t2SVmLSfc_BQhw0pqerror message:
VisualGDB version: 5.2.14.1318 ------------------ j31+l ------------------ j31+l: Failed to erase the FLASH region starting at 0x10000 at j31.j(qr1 a, ICustomStartupSequenceBuilder b) at j31.o1.b(qr1 a) at ot.e2.g3 1.d(qr1 a) at VisualGDB.Add_In.Tool_Windows.WPF.DockedProgressPresenter.a(Action 1 operation, String caption, eo exceptionHandler, String[] stages)
visualgdb remote console output:
http://pastebin.com/WNWrDye1- This reply was modified 7 years, 9 months ago by Frank.
FrankParticipantIt was the -Og flag forgot it in the new project.
But now that I have a working project and copied all my sources from my old project I’m presented with my first problem.
I’m using a library. When I enable the library my flash grows from 10 to 15% and I’m unable to flash the device.I am able to flash the program without the library and I am able to flash it with the library over my usb-serial.
But flashing with the library though the jtag debugger gives me this error:Visualgdb: flash read err, 1000 Serial: rst:0x3 (SW_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) flash read err, 1000 Falling back to built-in command interpreter. OK
FrankParticipantit seems the breakpoint is being hit but the debugger resets.
This issue is caused by OpenOCD resetting the debug controller??GDB:
esp32.cpu0: Target halted, pc=0x401074B8 esp32.cpu0: Debug controller was reset (pwrstat=0xFC, after clear 0xFC). esp32.cpu0: Core was reset (pwrstat=0xFC, after clear 0xFC). esp32.cpu1: Debug controller was reset (pwrstat=0xFE, after clear 0xFE). esp32.cpu1: Core was reset (pwrstat=0xFE, after clear 0xFE).
http://pastebin.com/fbiSrjRg for the full gdb output
OpenOCD:
Info : esp32.cpu0: Target halted, pc=0x401074B8 Warn : esp32.cpu1: target not halted Info : esp32.cpu1: Target halted, pc=0x40080340 esp32.cpu1: target state: halted Info : esp32.cpu1: placed hw breakpoint 0 at 0x401070FC Info : esp32.cpu0: placed hw breakpoint 0 at 0x401070FC Info : esp32.cpu0: Debug controller was reset (pwrstat=0xFC, after clear 0xFC). Info : esp32.cpu0: Core was reset (pwrstat=0xFC, after clear 0xFC). Info : esp32.cpu1: Debug controller was reset (pwrstat=0xFE, after clear 0xFE). Info : esp32.cpu1: Core was reset (pwrstat=0xFE, after clear 0xFE).
http://pastebin.com/zdzytQCt for the full openocd output
FrankParticipantI already made a blink example, flashing works but running causes the following problem:
I (1733) cpu_start: Pro cpu start user code Guru Meditation Error of type IllegalInstruction occurred on core 0 at pc=40118532. Setting bp and returning..
I have a Virtual machine running with visualgdb before the update, there it works fine without a problem.
Can I uninstall visualgdb and install a older version, and copy the esp32-bsp from my virtual machine?
On the virtual machine I have a other problem though, but ill make another thread about that.FrankParticipantI can build, just had to fix a few things.
The chip isn’t dead, I have programmed the chip over serial using a binary from an old project.My project wouldn’t program over jtag so I tried a clean project. In the clean project I can flash the chip through jtag but it goes into that guru meditation error.
The chip and the debugger are working perfectly.I removed the esp32 toolchain and downloaded it again but with the same results.
- This reply was modified 7 years, 10 months ago by Frank.
-
AuthorPosts