Re: sheeveplug u-boot environment
On Jan 5, 2016, at 10:12 PM, Vagrant Cascadian <vagrant@debian.org> wrote:
> On 2016-01-05, Rick Thomas wrote:
>> On Jan 5, 2016, at 12:17 PM, Vagrant Cascadian <vagrant@debian.org> wrote:
>>> Well, I would like to know if the newer versions in Debian are or aren't
>>> working, if you'd be willing to try. They do still build in 2016.01~rc3,
>>> so newer versions probably have converted over to generic-board (or just
>>> haven't been removed yet).
>>>
>>> There are a couple bugs reported against u-boot which may be relevent:
>>>
>>> https://bugs.debian.org/781874
>>> https://bugs.debian.org/782293
>>>
>>> I don't recall if the requested patches got into mainline u-boot, and I
>>> haven't included them as patches in the debian u-boot packages.
>>
>> Which version/package would you like me to test? I see the following versions available:
>
> All of them. :)
>
>> Version: 2015.10+dfsg1-4
> ...
>> Version: 2014.10+dfsg1-5
>
> There's also 2016.01~rc3+dfsg1-3 in experimental, and 2016.01 it
> scheduled to release on the 11th, and I plan to upload to unstable soon
> after. Better to know about issues *before* a release than after.
>
> I don't have a sheevaplug to test u-boot on; I won't be able to test and
> troubleshoot it myself. So knowing if it works on all of the versions in
> Debian would be a starting point, and committing to testing future
> versions would be ideal...
>
>
> live well,
> vagrant
I’ll try your 2016.01~rc3+dfsg1-3 from experimental as soon as I can.
Just to be sure of what I need to do:
1) Install the new versions of Debian packages for u-boot and u-boot-tools on my test SheevaPlug Debian (currently running Sid)
2) I do not need to worry about getting any experimental version of mtd-utils, right?
3) install the /usr/lib/u-boot/guruplug/u-boot.kwb file as u-boot following the instructions at Martin’s page
http://www.cyrius.com/debian/kirkwood/sheevaplug/uboot-upgrade/
except that I should use 0x80000 for the length of the “nand write” because modern u-boot binaries are bigger than 0x70000.
4) Do not use the procedure described in /usr/share/doc/u-boot/README.Debian to install the new u-boot because the information in /etc/fw_env.config is suspect, and may confuse the issue.
5) restart and check whether the environment has been preserved. If not, restore it manually.
6) reboot and see if it comes up? If it doesn’t, replace the old u-boot and environment and hope we haven’t clobbered something vital.
7) Report to you and the debian-arm list on the results…
Right?
Thanks for all your help!
Rick
Reply to: