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
@xobs I was recently working on a support for foboot in Renode. The current master, available on github supports Fomu platform capable of running foboot and booting software uploaded from host using dfu-util. The setup requires exporting virtual fomu device from Renode to the host system using USB/IP and from that moment on you interact with it the same way as with the real board.
During my adventure I tested two scenarios:
downloading software to the flash (works fine),
downloading it directly to RAM (had some problems).
As I understood from the sources, in order to direct the image to the RAM memory it must begin with a magic sequence followed by the address where this image should be stored.
What makes me wonder is that the whole image, inluding the magic sequence and the address, is written to RAM and then on reboot the CPU starts from it.
It seems to me that the first instruction CPU executes after reboot is the magic sequence. Shouldn't the start address be shifted by 8 to skip the metadata?
The text was updated successfully, but these errors were encountered:
I see. I wasn't precise enough - it's clear from the source code that the magic does not have to be exactly at the beginning of the image.
I simply didn't recognize the implications of this fact and the possibility to add a jump instruction before the magic - my bad.
@xobs I was recently working on a support for foboot in Renode. The current master, available on github supports Fomu platform capable of running foboot and booting software uploaded from host using
dfu-util
. The setup requires exporting virtual fomu device from Renode to the host system usingUSB/IP
and from that moment on you interact with it the same way as with the real board.During my adventure I tested two scenarios:
As I understood from the sources, in order to direct the image to the RAM memory it must begin with a magic sequence followed by the address where this image should be stored.
What makes me wonder is that the whole image, inluding the magic sequence and the address, is written to RAM and then on reboot the CPU starts from it.
It seems to me that the first instruction CPU executes after reboot is the magic sequence. Shouldn't the start address be shifted by 8 to skip the metadata?
The text was updated successfully, but these errors were encountered: