• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 30 subscribers
  • Views 372 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.

AM2634: Flash S25FL128SAGNFI000

Panda Bear
Intellectual 375 points
Part Number: AM2634

Hello 

For the Sitara AM263x we have 6 different Flash mode

What are differences for all Qspi boot mode? Could you explain them in more detail? I want to know, when is used individual boot modes ?

I have also got .cmm(am263x-S25FL128SA-qspi.cmm) file for the loading the software into the flash from you. Which mode should I use to load the code? Only DevBoot mode allows to load the code into the flash, but other modes do not allow me to load the code into the flash. Here in the .cmm file it is written I should choose Qsp_1. Which mode is Qsp_1 ? 

I am a  bit confused about this topic, maybe the topic is trivial but I need more information

Thanks in advance

  • 0
    TI__Mastermind 26145 points

    Hi ,

    Panda Bear said:
    What are differences for all Qspi boot mode? Could you explain them in more detail? I want to know, when is used individual boot modes ?

    These are the different boot modes supported by ROM boot.

    1. QSPI (4S) is 1s-1s-4s mode with and without fallback which means if the RBL does not find a valid image in the device, it will fallback to UART boot mode -- with fallback.
    2. QSPI (1S) is 1s-1s-1s mode with and without fallback which means if the RBL does not find a valid image in the device, it will fallback to UART boot mode -- with fallback.
    3. UART boot mode is a mode in which RBL captures the image via UART executing XMODEM.
    4. Dev Boot mode is a mode in which the RBL sets the device in a known state and the image is loaded via debugger/JTAG.

    Panda Bear said:
    .cmm(am263x-S25FL128SA-qspi.cmm) file for the loading the software into the flash from you

    This means that you are loading the image to the flash via Lauterbach script. The Dev Boot is mode apt mode for the same. The most apt documentation is to refer - TRM documentation for the same.

    Let me know if you have more questions.

    Best Regards,
    Aakash

  • 0 in reply to Aakash Kedia
    Intellectual 375 points

    Thank you for your reply

    So what is the difference between Qspi 4S and Qspi 1S Moodes ?What does it mean 1S 1S 1S or 1S 1S 4S?

    In .cmm file is written following txt:

    This means then i dip switch is in Qsp1S mode,right?

    If yes, why can I not load the code into the flash?

    What is apt documentation ?

    Thank you

  • 0 in reply to Panda Bear
    TI__Mastermind 26145 points

    Hi ,

    Panda Bear said:
    what is the difference between Qspi 4S and Qspi 1S Moodes ?What does it mean 1S 1S 1S or 1S 1S 4S?

    Please go through this documentation to get more information of what is QSPI and SPI mode of NOR Flashes - https://www.jblopen.com/qspi-nor-flash-part-3-the-quad-spi-protocol/

    Panda Bear said:
    In .cmm file is written following txt:

    This does not seem like a device or software specific documentation. I am not sure what this denotes.

    Panda Bear said:
    If yes, why can I not load the code into the flash?

    If the boot mode is QSPI, then the RBL will boot from Flash. Loading via JTAG is only supported via Dev Boot mode.

    Hope it helps.

    Best Regards,
    Aakash