Post Go back to editing

sharc 21489 boot from spi slave in CCES

Hi .

I am using sharc 21489 long time , before I always use VDSP++ on developmenting. 

Now I move to CCES, all things is working fine but spi slave boot. 

The kenel 489_spi is the same with VDSP ,I only do compile that!

So I don't know what's happens.  I am sure in VDSP++ the all sequency is right .

 it 's the same hardware,  why VDSP++ is ok ,CCES can not !

In CCES, My application program config is following.

I will attach my kernel 489_spi . it's the same with my VDSP kernel.489_spi.rar

Parents
  • Hi,

    If you are don't customized your kernel file, please enable "use default kernel" in Loader> general tab. Also, try to make the LDR file format as 'include 32 bit'.

    For your reference, Please find the attached SPI slave booting code for ADSP-21479 processor using CCES  in the below ezone link.
    ez.analog.com/.../405902

    Regards,
    Anand Selvaraj.

  • The current situation is that I use a simple blink LED program, and I can start it by removing ifndef DEBUG in the kernel.
    //#ifdef DEBUG
    // kdebug: jump (pc,0); // do not completely execute kernel - allows ICE to break in.
    //#endif

    But my problem now is that when my actual program is a little large(our project code is a bit much), and I enable SDRAM, CCES will automatically map part of the seg_swco segment to SDRAM, so that it cannot be started. If it is not mapped to SDRAM, it will be normal to start up.  

    dxe_sdram_sw_code SW
    {
    FILL(0x1) /* fill in gaps in the memory with NOPs */
    INPUT_SECTIONS( $OBJS_LIBS(seg_ext_code seg_swco seg_pmco) )
    } > mem_sdram_swco

    How to modify the kernel?

Reply
  • The current situation is that I use a simple blink LED program, and I can start it by removing ifndef DEBUG in the kernel.
    //#ifdef DEBUG
    // kdebug: jump (pc,0); // do not completely execute kernel - allows ICE to break in.
    //#endif

    But my problem now is that when my actual program is a little large(our project code is a bit much), and I enable SDRAM, CCES will automatically map part of the seg_swco segment to SDRAM, so that it cannot be started. If it is not mapped to SDRAM, it will be normal to start up.  

    dxe_sdram_sw_code SW
    {
    FILL(0x1) /* fill in gaps in the memory with NOPs */
    INPUT_SECTIONS( $OBJS_LIBS(seg_ext_code seg_swco seg_pmco) )
    } > mem_sdram_swco

    How to modify the kernel?

Children
No Data