Sent in a patch to meta-fsl-arm-extra to bump the u-boot-script-boundary recipe to add a sanity check for 6x_bootscript looking for the board variable. If it's not there then u-boot is far outdated and its a non-starter. That should help address this issue.
A bit off topic: That patch should apply to master, jethro, and fido. What's the etiquette for sending in patches to apply to multiple branches like that? Three separate patches with the tag of each branch? On Fri, Nov 6, 2015 at 12:56 PM, Otavio Salvador < [email protected]> wrote: > On Fri, Nov 6, 2015 at 6:37 PM, Ian Coolidge <[email protected]> > wrote: > >> Ok; will try that on Monday however be prepared for people to report > >> errors ;-) To be honest, I would make a backward compatible script > >> which checks the version and ask for the upgrade in case it is old so > >> user does not get an ugly error on their screen. > > > > > > Did you see this message as u-boot started? > > > > > https://github.com/boundarydevices/u-boot-imx6/blob/boundary-v2015.07/board/boundary/nitrogen6x/6x_bootscript-yocto-3.14.txt#L89-L93 > > No; it failed here: > > > https://github.com/boundarydevices/u-boot-imx6/blob/boundary-v2015.07/board/boundary/nitrogen6x/6x_bootscript-yocto-3.14.txt#L26 > > as board is undefined. > > -- > Otavio Salvador O.S. Systems > http://www.ossystems.com.br http://code.ossystems.com.br > Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750 >
-- _______________________________________________ meta-freescale mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-freescale
