• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 274 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CCS: Starterware:mcspiFlash is running wrong!

Hefa Zhuang
Prodigy 200 points
Other Parts Discussed in Thread: AM3354

Tool/software: Code Composer Studio

My board's cpu is am3354. The SPI FLash is SST25VF064C.I want to verify that spi flash works, so I simulated the board on CCS. The Starterware version I am using is AM335X_StarterWare_02_00_01_01. When I compile and run mcspiFlash.out, the serial port prints the information as follows:

Can you tell me why the data were verified failed?

I have verified that the spi flash on the board can be read ID normally.

  • 0
    Prodigy 200 points
    Anyone give me some help?Thanks!
  • 0 in reply to Hefa Zhuang
    TI__Guru** 116170 points
    Hefa,

    Probably not the best answer or solution to the problem that you are facing. The standalone starterware software package AM335x is no longer supported as this is legacy software that was supported for this device that did not integrate well for bare-metal and for RTOS use cases.

    We have now modified the starterware package and included a subset of the functionality in Processor SDK RTOS software package. Processor SDK RTOS is the only software package that we are supporting for AM335x family of devices. If this is a new design then we recommend that you migrate to Processor SDK RTOS software for getting the latest updates and support from TI. Please check general guidance for starterware users that we have provided as part of Processor SDK RTOS here:
    software-dl.ti.com/.../index_faq.html

    The general guidance when migrating to custom board with custom flash device are as follows:
    1. Compare the flash device used on custom design with TI evaluation hardware. Users need to check for mode requirements (phase and polarity where data is sampled), compatibility of protocol and commands to read and write to flash
    2. From SOC perspective, is the clocking, pinmux for MCSPI configured correctly. If the clock and MCSPI instance/ chip select are different, you need to modify the code accordingly.
    3. Connect a scope to the MCSPI pins and check signal integrity, timing for chip select, clock and if the data appears correctly on the SPI lines.

    The flash writer is provided in source so users can single step and debug the code. to figure out the root cause. Debugging on custom HW is responsibility of the user as we don`t have access to the HW. If it helps, you should run the code on the TI evaluation HW so you know what to expect from the flashing software.

    Regards,
    Rahul