UPGRADE YOUR BROWSER

We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

cancel
Showing results for 
Search instead for 
Did you mean: 
Observer andrewsi
Observer
2,213 Views
Registered: ‎02-05-2012

Sending SREC image from flash to SRAM instead of block RAM - how?

Jump to solution

So, I am successfully able to store a HelloWorld SREC image in flash, and then use the sample EDK bootloader to read that SREC image and it executes fine. (Presumably it's small enough.)

 

However, it is always storing the SREC image (generated with mb-objcopy) to address 00000000, which is the block RAM.  I need to write it to address 0x43000000 and then jump to there, not to block RAM.  It does this even though I used the Linker Script Generator to specify that ALL sections should go into the PSRAM memory at 0x43000000.

 

Shouldn't the SREC file generated by mb-objcopy have some sort of record that tells the bootloader to copy the image store the image somewhere other than 0x0 (like the PSRAM)?  Or do I need to do some sort of manual manipulation to make this work?


Thanks-

Andy

 

0 Kudos
1 Solution

Accepted Solutions
Observer andrewsi
Observer
2,760 Views
Registered: ‎02-05-2012

Re: Sending SREC image from flash to SRAM instead of block RAM - how?

Jump to solution
Actually, on further inspection I think it's doing exactly what I want it to - it's just setting up the vectors first and then jumping to the reset vector at 0x0, which then takes it to the code in the SRAM. At least, I think that's what's happening. I'll debug a little more closely tomorrow.
0 Kudos
1 Reply
Observer andrewsi
Observer
2,761 Views
Registered: ‎02-05-2012

Re: Sending SREC image from flash to SRAM instead of block RAM - how?

Jump to solution
Actually, on further inspection I think it's doing exactly what I want it to - it's just setting up the vectors first and then jumping to the reset vector at 0x0, which then takes it to the code in the SRAM. At least, I think that's what's happening. I'll debug a little more closely tomorrow.
0 Kudos