Sign in

username:

password:



Not a member?

Search c55x



Search tips

Subscribe to c55x



c55x by Keywords

AIC23 | C5509 | CCS | CSL | EMIF | EVM | GEL | GPIO | HPI | Interfacing | JTAG | McBSP | OMAP | Omap15 | OMAP59 | RTDX | SDRAM | TMS320VC5509 | USB | XDS5

Discussion Groups

Discussion Groups | TMS320C55x | C5510 Application doesn't work after FlashBurn with .cinit allocated in SDRAM

Technical discussions about the TI C55x DSPs (including the c5501, c5502, c5503, c5507, c5509, c5510 and OMAP5910).

  

Post a new Thread

C5510 Application doesn't work after FlashBurn with .cinit allocated in SDRAM - x.sh...@surrey.ac.uk - Feb 7 12:16:09 2008



Hi all,

I am using a Spectrum Digital TMS320VC5510 DSK board to develop an application. The
application, after FlashBurn to the onboard FlashROM, runs OK if I allocate the Data
Initialization Section (.cinit) in the SARAM(or SARAM_A/_B) via the GUI BIOS/DSP Config
interface. However if I allocate the .cinit section in SDRAM and FlashBurn to the FlashROM, it
does not work (or boot). In the Linker option, I have tried both the Run-Time
Autoinitialization (-c) and the Load-Time Initialization (-cr); the results are same. 

My application has to use the SDRAM for .cinit allocation. Did I miss something or something in
my linker and hex55 option is wrong? 

I have used the following Hex55 options in the convert command file:

myApplication.out
-m2
-boot
-map myApplicationHex.map
-parallel16
-v5510:2
-o myAPplication.hex

ROMS {
PAGE 0 : ROM : o=0x400000 , l = 0x80000
}

Thanks for you help.

Regards,

Xiyu Shi
Check Out Industry's First Single-Chip, Multi-Format, Real-Time HD Video Transcoding Solution
for Commercial & Consumer End Equipment: www.ti.com/dm6467



(You need to be a member of c55x -- send a blank email to c55x-subscribe@yahoogroups.com )

Re: C5510 Application doesn't work after FlashBurn with .cinit allocated in SDRAM - swding - Feb 13 10:15:54 2008

U need to add some config EMIF regs code in HEX55 convert, examples:

-reg_config 0x6c00, 0x0001      /* Enable EMIF bus. */
-delay 0x100  
-reg_config 0x0800, 0x00e0      /* EMIF_GCTL1 */
-delay 0x100
-reg_config 0x0804, 0x4210      /* EMIF_CE01 */
-delay 0x100
-reg_config 0x0805, 0x1092      /* EMIF_CE02 */
-delay 0x100 
-reg_config 0x0802, 0x0410      /* EMIF_CE11 */
-delay 0x100
-reg_config 0x0803, 0x0155      /* EMIF_CE12 */
-delay 0x100

 myApplication.out
-m2
-boot
-map myApplicationHex.map
-parallel16
 -v5510:2
 -o myAPplication.hex
 
 ROMS {
 PAGE 0 : ROM : o=0x400000 , l = 0x80000
}

-david

--- In c...@yahoogroups.com, x.shi@... wrote:
>
> Hi all,
> 
> I am using a Spectrum Digital TMS320VC5510 DSK board to develop an 
application. The application, after FlashBurn to the onboard 
FlashROM, runs OK if I allocate the Data Initialization Section 
(.cinit) in the SARAM(or SARAM_A/_B) via the GUI BIOS/DSP Config 
interface. However if I allocate the .cinit section in SDRAM and 
FlashBurn to the FlashROM, it does not work (or boot). In the Linker 
option, I have tried both the Run-Time Autoinitialization (-c) and 
the Load-Time Initialization (-cr); the results are same. 
> 
> My application has to use the SDRAM for .cinit allocation. Did I 
miss something or something in my linker and hex55 option is wrong? 
> 
> I have used the following Hex55 options in the convert command 
file:
> 
> myApplication.out
> -m2
> -boot
> -map myApplicationHex.map
> -parallel16
> -v5510:2
> -o myAPplication.hex
> 
> ROMS {
> PAGE 0 : ROM : o=0x400000 , l = 0x80000
> }
> 
> Thanks for you help.
> 
> Regards,
> 
> Xiyu Shi
>

Check Out Industry's First Single-Chip, Multi-Format, Real-Time HD Video Transcoding Solution
for Commercial & Consumer End Equipment: www.ti.com/dm6467



(You need to be a member of c55x -- send a blank email to c55x-subscribe@yahoogroups.com )