Hi Bob,
Bob Furber wrote:
While I'm not familiar with the 5208, isn't dBUG in Flash, not SDRAM?
Once it stops running (by passing control to Linux) then any RAM it was
using should be fair game, provided that all its hooks (interrupt
vectors etc) are removed (which they should be).
My first re
Quoth Bob Furber [EMAIL PROTECTED]:
> I believe that amongst other things, the dBUG stack is near
> the bottom of SDRAM. So, it becomes a bit of a philosophical
> question: What do we want to happen when uClinux is shut
> down? Return to the dBUG> prompt?
>
> Perhaps if uClinux could trigger a sof
> While I'm not familiar with the 5208, isn't dBUG in Flash, not SDRAM?
> Once it stops running (by passing control to Linux) then any RAM it was
> using should be fair game, provided that all its hooks (interrupt
> vectors etc) are removed (which they should be).
My first reaction was "Duh! Why d
Hi martin,
Martin Voss wrote:
Thanks all for the feedback. I don’t feel that this gives any other
severe side effects either, besides incorrect values at boot and in
/proc/meminfo (and free command). But we will of course change to the
correct setting.
A couple of other details I have been
Quoth Martin Voss <>:
> I agree that useable SDRAM starts at 0x4002 since dBUG uses the
> first 0x2. The physical end address of the SDRAM is 0x4200
> (32MB).
[...]
> Since the first 0x2 is used by dBUG, why is MEM_BASE 0x4000
> and not 0x4002 ? Any shouldn't MEM_SIZE b
