* > Sorry for answering later, I've had COVID since Thursday and I take naps quite often :|
> usually with STM32 you need to use --connect-under-reset, are you doing that? Yes, I am, I managed to get it to display different messages, which I have attached as a text file as it's quite verbose.

> are you trying to flash known-good firmware, or are you trying to flash your WIP Rust code?
> For the part of the firmware that resides in internal flash: yes it's known good, but for the program I am trying to flash inside of the external OSPI flash, it's just one of the examples from the embassy repo, I am assuming that they're correct, only change I made is selecting the right GPIO pin for the LED.

> might be worth trying to change ap to 0 in core\_access\_options. not sure why the pack contains ap: 1
> I'll try that in a few minutes

> hm I guess probe-rs info is useful at this point as it scans through the APs,
> here is the output, hope this is helpful (this is with the modified version of probe-rs with the additional memory region, all-else is as it is on git/main)

```
 RUST_LOG=info cargo run -- info --chip STM32H7S7L8Hx --connect-under-reset
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.12s
     Running `target/debug/probe-rs info --chip STM32H7S7L8Hx --connect-under-reset`
Probing target via JTAG

 INFO probe_rs::probe: Custom reset sequences are not supported on ST-Link V3.
 INFO probe_rs::probe: Falling back to standard probe reset.
 INFO attach: probe_rs::probe::stlink: Target voltage (VAPP): 3.29 V
 WARN attach: probe_rs::probe::stlink: send_jtag_command 242 failed: JtagUnknownJtagChain
Error identifying target using protocol JTAG: An error with the usage of the probe occurred

Probing target via SWD

 INFO probe_rs::probe: Custom reset sequences are not supported on ST-Link V3.
 INFO probe_rs::probe: Falling back to standard probe reset.
 INFO attach: probe_rs::probe::stlink: Target voltage (VAPP): 3.29 V
 WARN probe_rs::probe::stlink: send_jtag_command 242 failed: SwdApWdataError
 WARN probe_rs::probe::stlink: send_jtag_command 242 failed: SwdApWdataError
ARM Chip with debug port Default:
Debug Port: DPv2, Designer: STMicroelectronics, Part: 0x4850, Revision: 0x1, Instance: 0x00
├── 0 MemoryAP
│   └── Error during access: The debug probe encountered an error.
└── 1 MemoryAP
    └── Error during access: Could not access romtable


Debugging RISC-V targets over SWD is not supported. For these targets, JTAG is the only supported protocol. RISC-V specific information cannot be printed.
Debugging Xtensa targets over SWD is not supported. For these targets, JTAG is the only supported protocol. Xtensa specific information cannot be printed.
```

Usually I get the right info, don't know why this time it didn't 🫠