search

esp-rs / esp32-hal

A hardware abstraction layer for the esp32 written in Rust.
Apache License 2.0
193 stars 28 forks source link

Example ram RTCWDT_RTC_RESET #63

Open KerryRJ opened 3 years ago

KerryRJ commented 3 years ago

I pulled down the latest crates and successfully ran alloc and mem(thank you) but ram is now failing

ets Jun 8 2016 00:22:57

rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) configsip: 0, SPIWP:0xee clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00 mode:DIO, clock div:2 load:0x3fff0048,len:12 ho 0 tail 12 room 4 load:0x3fff0054,len:4800 load:0x40078000,len:17448 load:0x4007c428,len:4840 entry 0x4007c6a0 ets Jun 8 2016 00:22:57

rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) configsip: 0, SPIWP:0xee clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00 mode:DIO, clock div:2 load:0x3fff0048,len:12 ho 0 tail 12 room 4 load:0x3fff0054,len:4800 load:0x40078000,len:17448 load:0x4007c428,len:4840 entry 0x4007c6a0

Are you able to confirm it working on your side @MabezDev?

KerryRJ commented 3 years ago

Info from Jtag session

Reading symbols from C:\Dev\Github\esp32-hal\target\xtensa-esp32-none-elf\debug\examples\ram... done. 0x40000288 in ?? () Program stopped, probably due to a reset and/or halt issued by debugger Register cache flushed.

After a debug restart

JTAG tap: esp32.cpu0 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1) JTAG tap: esp32.cpu1 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1) esp32.cpu0: Debug controller was reset. esp32.cpu0: Core was reset. esp32.cpu0: Target halted, PC=0x500000CF, debug_reason=00000000 esp32.cpu0: Core was reset. esp32.cpu0: Target halted, PC=0x40000400, debug_reason=00000000 esp32.cpu1: Debug controller was reset. esp32.cpu1: Core was reset. esp32.cpu1: Target halted, PC=0x40000400, debug_reason=00000000 Register cache flushed. Continuing. Note: automatically using hardware breakpoints for read-only addresses. esp32.cpu0: Target halted, PC=0x400003C0, debug_reason=00000001 Set GDB target to 'esp32.cpu0' esp32.cpu1: Target halted, PC=0x400076DD, debug_reason=00000000

Program received signal SIGTRAP, Trace/breakpoint trap. 0x400003c0 in ?? ()

I cannot get a breakpoint at the start of main to work.

MabezDev commented 3 years ago

Works for me: Ignore that, was running the wrong example cargo +esp-dev espflash --tool cargo --chip esp32 --speed 460800 --example mem --features alloc /dev/ttyUSB0

Are you enabling the external-ram feature? If you are, without psram connected that will almost certainly end in trouble :D

MabezDev commented 3 years ago

Scratch what I said above, not working for me either!