SDCard load problem

GoogleGroups
1

I am using the factory default uboot.

I tried to open a 17MB binary using:

mmcinit
fatload mmc 0 0x80000000 image.bin
go 0x80000000

It hangs in the fatload cmd (45 min - 1 hour later I do not get the prompt).

It never happened to me before, since all my images were in the 500kB-3MB range. Now I have rootfs in the image binary.

I tried to do the same thing on a different uboot. The one from: Google Code Archive - Long-term storage for Google Code Project Hosting.

Same problem.

Is it from the SDcard batch (Apacer 2GB, 60x), or did somebody see this before.

Thank you,
Gabi Voiculescu
|

2

I really dont know for sure, but my guess is that fatload has a maximum
file size the command supports. A bit like TFTP - has a maximum size you
can tftp into memory. And uboot on beagleboard will hang as soon as
anything goes wrong, because its exception handling vectors dont work (i
fixed them for myself when i needed).

So you might be getting some data abort exception, but it is never
handled. The effect of this is you 'perceive' the beagleboard as 'hung'.

Gabi Voiculescu wrote:

3

It seems to have something to do with uboot settings.

By default the factory uboot has these settings:
- U-Boot start @ 0x80E80000
- U-Boot end @ 0x80EE5958

My setup was to load binaries at 0x80000000. Once I got beyond 0x80e80000 (so above 14.5MB, I would overwrite uboot, so the fatload would have nothing to return to).

For this case the entry point should be changed for binaries loaded on uboot…

Gabi Voiculescu

— On Fri, 10/23/09, Danielius Kudinskas danielius.kudinskas@gmail.com wrote:


> From: Danielius Kudinskas danielius.kudinskas@gmail.com
> Subject: [beagleboard] Re: SDCard load problem
> To: beagleboard@googlegroups.com
> Date: Friday, October 23, 2009, 1:34 AM
>
> I really dont know for sure, but my guess is that fatload has a maximum
> file size the command supports. A bit like TFTP - has a maximum size you
> can tftp into memory. And uboot on beagleboard will hang as soon as
> anything goes wrong, because its exception handling vectors dont work (i
> fixed them for myself when i needed).
>
> So you might be getting some data abort exception, but it is never
> handled. The effect of this is you ‘perceive’ the beagleboard as ‘hung’.
>
> Gabi Voiculescu wrote:
> > I am using the factory default uboot.
> >
> > I tried to open a 17MB binary using:
> >
> > mmcinit
> > fatload mmc 0 0x80000000 image.bin
> > go 0x80000000
> >
> > It hangs in the fatload cmd (45 min - 1 hour later I do not get the
> > prompt).
> >
> > It never happened to me before, since all my images were in the
> > 500kB-3MB range. Now I have rootfs in the image binary.
> >
> > I tried to do the same thing on a different uboot. The one from:
> > http://code.google.com/p/beagleboard/wiki/BeagleboardRevCValidation
> >
> > Same problem.
> >
> > Is it from the SDcard batch (Apacer 2GB, 60x), or did somebody see
> > this before.
> >
> > Thank you,
> > Gabi Voiculescu
> >
> >
> >
> > >

|