05:56 <M0xada3[m]> Has anyone else noticed that probe-rs halts unexpectedly sometimes? For example if I set a breakpoint on main, hit that breakpoint and then try to continue execution, it halts on the next instruction unexpectedly and then another continue will work as expected.

07:04 <juliand[m]> <M0xada3[m]> "Has anyone else noticed that..." <- Maybe some code has been optimized away or you're getting an interrupt?

07:04 <juliand[m]> You could also try asking in the probe-rs chat https://matrix.to/#/#probe-rs:matrix.org

09:31 <M0xada3[m]> I am just starting out with the embedded Rust Discovery book for the micro:bit so I am building unoptimized debug builds and the example code itself isn't using interrupts but there is nothing saying that some of the library code being pulled in doesn't use them under the covers. I do have quite a bit of experience with GDB on embedded platforms but with C and C++ and there optimization and interrupts wouldn't lead to the issue I

09:31 <M0xada3[m]> described above. Thanks for the pointer to the probe-rs room. I may try there as well.

13:16 <justacec[m]> Hey everybody! :). I have been trying to understand why the RP chips need the second bootloader. All of the memory.x examples that I can find to support the RP2040 or the RP235X chips seem to carve out space for the rp2040_boot2 package. I thought that the XIP would auto translate to the external chip and therefore your code would be automatically execute as long as it was started at the 0x1000000 position. Am I missing

13:16 <justacec[m]> something substantial somewhere in there? Also, associated side question: It seems that the default secondary bootloader is hardcoded to the BOOT_LOADER_W25Q080. Do all QSPI flash chips just support this by default?

13:16 <JamesMunns[m]> The rp2040 hardware only boots enough to pull the first 256 bytes off of the flash, in a very slow + compatible way

13:17 <JamesMunns[m]> boot2 is a firmware bootloader you provide, which configures the hardware in a way that matches your board, in particular what flash chip you use, which might use different commands (there are a couple common ones, not all chips support all commands), and things like how fast of a speed does your flash chip support

13:18 <justacec[m]> Ok

13:18 <JamesMunns[m]> there are a couple of "stock" ones, which cover *most* common flash parts out there. You could write your own, but the job of boot2 is to set up the rp2040 enough so that it can talk to whatever flash chip you chose, so that you can then get to running your specific firmware

13:18 <justacec[m]> I will continue digging through the boot process in the datasheet

13:19 <justacec[m]> I am assuming that the 2040 boot2 will work on the 2350 chips

13:20 <JamesMunns[m]> yeah, the rough overview is something like:... (full message at <https://catircservices.org/_matrix/media/v3/download/catircservices.org/jIfhesTpJQciNibzNbmUZMZi>)

13:20 <JamesMunns[m]> justacec[m]: that I have no idea about.

13:20 <JamesMunns[m]> You can also ask in #rp-rs:matrix.org, but I think most folks there also hang out here :)

13:21 <justacec[m]> Thanks for the info.

13:22 <justacec[m]> I will try to focus my RP questions to that channel in future.

13:22 <GrantM11235[m]> The 2350 bootloader is more complex, I don't think it uses a boot2

13:23 <JamesMunns[m]> yeah, all my comments above are specific to the RP2040, I'm not familiar with the 2350 family yet, it has a lot more options for booting, and a chunk of "one time write" burnable code you can use for a bootloader

13:25 <GrantM11235[m]> You need special headers in your binary, with optional signatures and partitioning

13:26 <justacec[m]> Cool. thanks again everybody. I will keep digging through the datasheet

13:30 <MurrayToddWillia> <justacec[m]> "I am assuming that the 2040 boot..." <- Refer to thejpster 's [blog entry](https://thejpster.org.uk/blog/blog-2024-08-08/) about the rp235x boot process. It's definitely different.

17:43 <thejpster[m]1> Hi five on https://github.com/rust-embedded-community/pc-keyboard/pull/46 please

17:52 <JamesMunns[m]> <thejpster[m]1> "Hi five on https://github.com/..."; <- high fived!

18:17 <thejpster[m]1> thanks

18:17 <thejpster[m]1> I'll prepare a 0.7.1 with the fix (I'm sat in the hotel lobby)

18:19 <thejpster[m]1> wait, no, semver-checks says I need to make it 0.8.0

18:29 <thejpster[m]1> https://github.com/rust-embedded-community/pc-keyboard/pull/47

18:36 <JamesMunns[m]> <thejpster[m]1> "https://github.com/rust-embedded..."; <- +1'd

18:39 <thejpster[m]1> ah, hmm, clippy is having opinions again

18:55 <thejpster[m]1> done