Yes, sort of. Basically a tiny loader in OTP that enables nCS1 on some pin, copies code from there to ram on nCS0, reconfigures nCS1 to point to second ram. This does break usb flashing. Use swd.
Yes, sort of. Basically a tiny loader in OTP that enables nCS1 on some pin, copies code from there to ram on nCS0, reconfigures nCS1 to point to second ram. This does break usb flashing. Use swd.
Is there no way to do that without code in OTP? The bootrom is supposed to scan for an IMAGE_DEF on both memory banks, and can use nCS1 as specified in FLASH_DEVINFO. Unless there's something I'm missing, that should be sufficient.
I have not disassembled the production RP2350 rom (last i looked at it was ~year before release) so i do not know if it does indeed check nCS1 address space, but even if it did, which of the 4 possible pins would it configure as nCS1? surely trying all would be dangerous (possibly breaking customer logic attached to this pins that does not expect them to wiggle at boot). This seems like it could break customer designs so I would be worried if this did happen. I could be wrong. You can read out the rom with a debugger and look, of course :)
FLASH_DEVINFO (in OTP) has fields to set how large M1 is and what nCS pin to use for it. It's off by default.
Yes, you still have to write to OTP - but a few bits of configuration is a lot easier than an entire init routine.
ok, sorry, was trying to reply with regard to "no otp" as i understood your comment. i see i misunderstood. then yes it'll work