You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I suggest on elaborating more on the pico-examples/bootloaders/encrypted example. As far as I dug into the documentation this example might become a reference implementation for those with the need to execute encrypted code on RP2350 devices. This capability is of great importance for most commercial users here.
The problem I encountered is, that the bootloader often fails with other binaries than the hello_serial example. The encryption and signature worked. But in the very end
returns with a value of -4. This means according to the headers BOOTROM_ERROR_NOT_PERMITTED.
It keeps me puzzled since I have used the bootloader, the partition table etc exactly as in the example. Make the binary bigger sometimes helped and it worked.. The binary should be small enough with 75 kbyte and lots of free space for the heap.
What I also don't understand is that I assumed that the bootloader does not write to the flash, but only to RAM. So why can there be a permission problem?
Having those error codes mentioned in the readme with an explanation would be helpful.
The text was updated successfully, but these errors were encountered:
I've managed to reproduce this with the hello_usb example, and it seems to be an issue in picotool encrypt when there is a gap between the .text and .rodata sections in the ELF file. I will investigate further, but for a temporary fix you can apply this diff to the pico-sdk and it should work.
That is interesting! Thanks!
I'm still working on my minimal example. It seems that if I add tinyusb to hello_serial example, causes the error. But only if I add some arrays to bloat the code.
But this seem to be consistent with your findings on hello_usb.
I suggest on elaborating more on the pico-examples/bootloaders/encrypted example. As far as I dug into the documentation this example might become a reference implementation for those with the need to execute encrypted code on RP2350 devices. This capability is of great importance for most commercial users here.
The problem I encountered is, that the bootloader often fails with other binaries than the hello_serial example. The encryption and signature worked. But in the very end
returns with a value of -4. This means according to the headers BOOTROM_ERROR_NOT_PERMITTED.
It keeps me puzzled since I have used the bootloader, the partition table etc exactly as in the example. Make the binary bigger sometimes helped and it worked.. The binary should be small enough with 75 kbyte and lots of free space for the heap.
What I also don't understand is that I assumed that the bootloader does not write to the flash, but only to RAM. So why can there be a permission problem?
Having those error codes mentioned in the readme with an explanation would be helpful.
The text was updated successfully, but these errors were encountered: