[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[microblaze-uclinux] Newbie question about external ram executability



Hi,


  I've created a flash programmer/ram test/xmodem download program in order
to download the uClinux kernel to the board when it is just being brought
up in production (sometime later this year?!!).

 I used mb-objcopy to create a binary image from a small test program.

  I downloaded the program into external static ram at 0x80000000 and
verified it was there.

  I created a small boot program to jump to that address, and used mdm
assembly language stepping to prove that the "brild r9, r15" code was about
to jump to 0x80000000 (in r15).

  As soon as it gets to that address, it shows a blank screen in the
debugger, and then it reboots at 0 (the bitram).  If I just let it free
run, it reboots at zero (which is what caused me to break out the
debugger.)  We are doing this because we can't get uClinux to boot
properly, and we are now in the simple step by step phase.

  My hardware guy is stumped.  Is there a setting that needs to be made to
make external ram executable in this Harvard architecture processor?   I
really do like Von Neumann after all.

  I've included the system.mhs file, just in case.  This is a stripped down
version just for troubleshooting.

thanks,
wade


(See attached file: system.mhs)
***CONFIDENTIALITY NOTICE***
This communication (and any attachment) is confidential. It should only be
read by the person(s) to whom
it is addressed.  If you have received this communication in error, please
notify the sender by reply and delete this communication.
*****************************************

Attachment: system.mhs
Description: Binary data