This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Boot C5505 from NOR-flash

Other Parts Discussed in Thread: TMS320C5505

We have own board with C5505, SDRAM and NOR-flash (SDRAM and flash are same as on EVM5515).

I can write and verify the same binary image to NOR-flash on EVM5515 and on our board. SDRAM also works successfully.

EVM5515 successfully booting from NOR, but bootloader on C5505 on our board always go to USB boot.

Does bootloader on C5505 have any errors or differences with VC5515?

  • Do you have own custom board with C5505 DSP?

    The same boot code works on EVM5515's NOR-flash and SDRAM, right?

    But the same boot code always go to USB on your custom board with C5505 DSP, correct?

    regards.

  • Yes. We have custom board with c5505.

    We flash the same binary image to NOR on our custom board and on EVM5515.

    EVM5515 boots correctly from NOR, but our custom board stays in bootloader in USB boot.

  • This is telling me that your custom board has a problem to boot from NOR. There is no different between the C5505 and C5515 boot.

    If you refere to the flow chart figure in data sheet, Bootloader Software Architecure, bootloader stays in USB Boot after all other peripherals.

    Regards.

  • This is not new information for me.

  • Any ideas?

    May be any hardware incompatibility?

    The nor-flash is PC28F128P30TF65 (Numonyx® Axcell™ P30-65nm Flash Memory).

  • Hi Oleg,

    It's hard to tell since you use a custom board. I assume that you can run your board successfully in debug mode (via JTAG). Can I have a look on the schematic, if you don't mind?

    Cheers,

    Cong-Van

  • Hi,

    The problem solved with changing TI DSP to XXX DSP :) cheers :)

    Joke ;)

     Well, if to be serious, the problem lies in the incorrect handling with NOR flash by bootloader.

     When bootloader tries to boot from NOR-flash, it writes a read array command (as I guess, and it must be a 0xFF) at first CS# and then reads a word (checking the first 2 bytes read from boot signature, which must be 0x09AA).

    C5505 bootloader (as VC5515 too) sends 0xF0, whereas must send a 0xFF. Memory installed on the EVM5515 board (PC28F128P30BF85, which has the EOL status on Micron site) apparently misses the wrong code, so remaining in the read mode, and returns the header 0x09AA.

    The newer memory, as PC28F128P30BF65 returns with this wrong code the value of status register, as I think, which after reset must be a 0x80, and so the loader fails.

    Disconnecting WE# line after programming the flash, for preventing any writes, confirms this, application boots and runs.

    I cannot find any command with code 0xF0 in this nor-flash datasheet, new Axcell and old StrataFlash generations both, and what memory CUI will do with wrong command code.

     

    And one more thing. Using hex55.exe v.4.3.6 util with option -v5505 generates .bin with 0x09AA header, while with option -v5515 generates without it.

    Regards

     

    information:
    TMS320C5505 data sheet, SPRS660D.pdf

    Numonyx® Axcell™ P30-65nm Flash Memory, 208033_P30_65_SBC_Discrete_DS.pdf

    Numonyx™ StrataFlash® Embedded Memory (P30), 306666_P30_Discrete_DS.pdf