gdamjan / rust-embedded-intro

My Playground for the nrf5340-dk devkit and Rust
MIT License
0 stars 0 forks source link

Core 1 Locked #1

Open djovanoski opened 2 weeks ago

djovanoski commented 2 weeks ago

Hello, im trying out your code and get error for :

Im using embed version 0.24, but as far everything i try i get warning from probe-rs about Core 1 is locked and could not clear all hardware breakpoints woulld be great to help me

gdamjan commented 2 weeks ago

what hardware, paste the exact errors you get and what exactly were you doing at that time.

djovanoski commented 1 week ago

Hello, thanks on answering this is my log with info:

RUST_LOG=info cargo r 
    Finished `dev` profile [optimized + debuginfo] target(s) in 0.01s
     Running `probe-rs run --chip nRF5340_xxAA --allow-erase-all target/thumbv8m.main-none-eabihf/debug/tz_nrf`
 INFO probe_rs::config::target: Using sequence Arm(Nrf5340(()))
 INFO probe_rs::probe::jlink: J-Link: Firmware version: J-Link OB-nRF5340-NordicSemi compiled Apr 11 2024 17:44:26
 INFO probe_rs::probe::jlink: J-Link: Hardware version: J-Link 1.0.0
 INFO probe_rs::probe::jlink: J-Link: Target voltage: 3.30 V
 INFO probe_rs::probe::jlink::speed: Selecting speed: 400 Hz
 INFO probe_rs::architecture::arm::sequences: Debug port Default is powered down, powering up
 INFO probe_rs::vendor::nordicsemi::sequences::nrf: Checking if core 0 is unlocked
 INFO probe_rs::vendor::nordicsemi::sequences::nrf: Core 0 is already unlocked
 INFO probe_rs::vendor::nordicsemi::sequences::nrf: Checking if core 1 is unlocked
 WARN probe_rs::vendor::nordicsemi::sequences::nrf: Core 1 is locked. Erase procedure will be started to unlock it.
 WARN probe_rs::architecture::arm::core::armv8m: The core is in locked up status as a result of an unrecoverable exception
 WARN probe_rs::architecture::arm::core::armv8m: The core is in locked up status as a result of an unrecoverable exception
 INFO probe_rs::flashing::download: Found loadable segment, physical address: 0x00050000, virtual address: 0x00050000, flags: 0x4
 INFO probe_rs::flashing::download: Matching section: ".vector_table"
 INFO probe_rs::flashing::download: Found loadable segment, physical address: 0x00050154, virtual address: 0x00050154, flags: 0x5
 INFO probe_rs::flashing::download: Matching section: ".text"
 INFO probe_rs::flashing::download: Found loadable segment, physical address: 0x000512e8, virtual address: 0x000512e8, flags: 0x4
 INFO probe_rs::flashing::download: Matching section: ".rodata"
 INFO probe_rs::flashing::download: Found loadable segment, physical address: 0x00051734, virtual address: 0x2003fbc0, flags: 0x6
 INFO probe_rs::flashing::download: Matching section: ".data"
 INFO probe_rs::flashing::loader: Found 4 loadable sections:
 INFO probe_rs::flashing::loader:     .vector_table at 0x00050000 (340 bytes)
 INFO probe_rs::flashing::loader:     .text at 0x00050154 (4500 bytes)
 INFO probe_rs::flashing::loader:     .rodata at 0x000512E8 (1100 bytes)
 INFO probe_rs::flashing::loader:     .data at 0x00051734 (56 bytes)
 INFO probe_rs::flashing::flash_algorithm: Chosen RAM to run the algo: RamRegion { name: None, range: 20000000..20040000, cores: ["application"], access: None } INFO probe_rs::flashing::flash_algorithm: Data will be loaded to: RamRegion { name: None, range: 20000000..20040000, cores: ["application"], access: None } INFO probe_rs::flashing::flash_algorithm: The flash algorithm will be configured with 512 bytes of stack               INFO probe_rs::flashing::flash_algorithm: Stack top: 0x20002740                                                       ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ INFO probe_rs::flashing::flash_algorithm: Chosen RAM to run the algo: RamRegion { name: None, range: 20000000..20040000, cores: ["application"], access: None }
 INFO probe_rs::flashing::flash_algorithm: Data will be loaded to: RamRegion { name: None, range: 20000000..20040000, cores: ["application"], access: None }
 INFO probe_rs::flashing::flash_algorithm: The flash algorithm will be configured with 512 bytes of stack
 INFO probe_rs::flashing::flash_algorithm: Stack top: 0x20002740
 INFO probe_rs::flashing::flasher: Erasing sector at address 0x00050000
 INFO probe_rs::flashing::flasher: Done erasing sector. Result is 0. This took 119.978131ms
 INFO probe_rs::flashing::flasher: Erasing sector at address 0x00051000
 INFO probe_rs::flashing::flasher: Done erasing sector. Result is 0. This took 119.978141ms
 INFO probe_rs::flashing::flasher: Took 150.428435ms to download 4096 byte page into ram
 INFO probe_rs::flashing::flasher: Took 150.153465ms to download 4096 byte page into ram
 WARN session_drop: probe_rs::session: Could not clear all hardware breakpoints: An ARM specific error occurred.

Caused by:
    A timeout occurred during an operation.                                                                             INFO probe_rs::architecture::arm::sequences: Powering down debug port Default                                          INFO probe_rs::architecture::arm::sequences: Powering down debug port Default                                         Error: The flashing procedure failed for 'target/thumbv8m.main-none-eabihf/debug/tz_nrf'.

Caused by:
    0: Something during the interaction with the core went wrong
    1: An ARM specific error occurred.
    2: A timeout occurred during an operation.
gdamjan commented 1 week ago

report the issue to probe-rs, including the exact hardware version.