Nicolas Thierry

Has anyone found a fix for the second report issue ? This is definitly causing accessibility issue on ios as when fully extand the bar is near the phone status...

I faced the same problem but couldn't downgrade because in my case I need angular 15. So for anyone in this case you can just add this in the declaration...

> Alright, I have gotten close to the root of the issue and I can get the local config to work with a caveat. Here are my steps: > >...

I dig a bit and wanted to try implementing a SIO interrupt like they did with the lockout function. For that, on core 0 I did: ```rust vt.init(&mut pac.PPB); vt.register_handler(pac::Interrupt::SIO_IRQ_PROC0...

Hey, Thanks, for looking at this issue! I'm going to write a small example to isolate the behavior I'm trying to achieve so hopefully it will makes more sense to...

Here is the example code: https://github.com/Captainfl4me/rust-2-rp/blob/master/multicore-lockout-irq/src/main.rs

Thank you so much for the insights! I did know about objdump I think it will be very useful to better understand what is actually going on. For the write_flash...

Well you're right after a close inspection of the dump file it seems like all the function calls (`rom_data::`, `critical_section_acquire`, `critical_section_release`, `read`, `read_blocking`) actually live in ROM (section .text) therefore...

I refactor the code to have the following (I push the changes if you want to take a look on the repos), ```rust #[inline(never)] #[link_section = ".data.ram_func"] extern "C" fn...

Okay my bad it was just a problem with the way I was passing the buffer to the `flash_range_program` function. Now, everything seems to work!! Code [here](https://github.com/Captainfl4me/rust-2-rp/blob/fea2eaa4c533fd3f030a600bda0ee22bcefe8067/multicore-lockout-irq/src/main.rs)