Sascha, I figured out the issue. 'scp' was not copying my new version.. and not indicating failure. Once i deleted the old bin and copied a new one, i see it is running without relocation. Sorry. On Mon, Sep 30, 2013 at 10:38 AM, Sascha Hauer <s.hauer@xxxxxxxxxxxxxx> wrote: > Hi Allen, > > On Mon, Sep 30, 2013 at 09:24:17AM -0500, Allen Kennedy Jr. wrote: >> Hello, >> I have relocatable binary set to "n" and I load barebox into ram >> exactly where it is supposed to be, but it still runs the function >> "relocate binary" >> >> Is the option to not relocate barebox, not supported? >> >> Why would I want it not-relocated? Because relocate_to_current_adr() >> causes an exception every time, and barebox won't boot. And I can't >> figure out why the exception occurs. > > Generally relocatable barebox is not enforced and barebox runs happily > without it. However, there are some combinations of PBL/TEXT_BASE which > really do need relocation support. > > What SoC/board are you running? Could you post your .config file? > > Sascha > > -- > Pengutronix e.K. | | > Industrial Linux Solutions | http://www.pengutronix.de/ | > Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | > Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | > > _______________________________________________ > barebox mailing list > barebox@xxxxxxxxxxxxxxxxxxx > http://lists.infradead.org/mailman/listinfo/barebox _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
