Hi, What if I compile a new u-boot but to try it I will load and flash new created image after original u-boot and will run it from withing original reboot manually just pointing a new image address? Can it work?
On Mon, Oct 29, 2012 at 10:38 AM, Andreas Bießmann < andreas.devel@googlemail.com> wrote:
Dear Dimax,
On 29.10.2012 07:55, Dimax wrote:
HI, So you say I have to rebuild u-boot with expanded CONFIG_SYS_MALLOC_LEN. So far I have used rebuild images from: http://people.debian.org/~tbm/u-boot/2011.12-3/sheevaplug/u-boot.kwb http://people.debian.org/%7Etbm/u-boot/2011.12-3/sheevaplug/u-boot.kwb
I see following files in the parrent directory:
[ ] u-boot_2012.04.01-2.debian.tar.gz <
http://people.debian.org/%7Etbm/u-boot/2012.04.01-2/u-boot_2012.04.01-2.debi...
[ ] u-boot_2012.04.01-2_armel.deb <
http://people.debian.org/%7Etbm/u-boot/2012.04.01-2/u-boot_2012.04.01-2_arme...
[ ] u-boot_2012.04.01.orig.tar.bz2 <
http://people.debian.org/%7Etbm/u-boot/2012.04.01-2/u-boot_2012.04.01.orig.t...
so if you are using a distributed version of u-boot, why don't file a bug there?
Is it all I need to rebuild?
Yes, after increasing the size of malloc arena (supposed my suspicion is correct).
Are there any general instructions?
Does <u-boot-src>/README section 'Building the Software' fit your needs? BEWARE! If you never built u-boot you should know you may brick your device, see the countless de-bricking guides for sheevaplug and prove you can de-brick it before you brick it ;)
Best regards
Andreas Bießmann