• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 32 subscribers
  • Views 304 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-Q1: QSPI FLASH Read in Configuration Mode - SDK9.2

AndreTseng
Intellectual 2605 points
Part Number: AM2634-Q1


Tool/software:

Hi expert,

    I'm trying to test FLASH read/write in configuration mode. I use demo project  qspi_flash_diag_am263x-cc_r5fss0-0_nortos_ti-arm-clang as code base

and just modify one line as below: 

QSPI_norFlashReadIntr() is provided with SDK9.2

However, the test will suck during flash read in configuration mode.

I'm wondering do we fully test Flash read in configuration mode?

Regards

Andre

  • +1
    TI__Guru**** 198546 points

    Hi Andre,

    The QSPI_norFlashReadIntr() is an API for interrupt mode. But your project is for polling mode.

  • 0 in reply to QJ Wang
    TI__Intellectual 2605 points

    QJ,

        That's interesting. This is first time I learned that I can't modify code to enable interrupt support in a user project. I would like to learn more.

    Other drivers like SPI/I2C..., user just needs to call I2C_transfer(), MCSPI_transfer(). Lower layer driver  in SDK already takes care interrupt handling.

    From the debug observation, QSPI_norFlashReadIntr() will enable interrupt and register callback.  lower layer QSPI_lld_isr did execute. But something wrong during in its state machine, so transfer stuck in transaction, its callback function never be called.

    Anyway, customer needs an example to use interrupt mode to enable read in configure mode. If you don't think modify existing project is good ideal, please provide working sample code.

    Regards

    Andre 

  • 0 in reply to AndreTseng
    TI__Guru**** 198546 points

    HI Andre,

    The interrupt is enabled in QSPI_open(). In polling-mode example, attrs->intrEnable = False, the interrupt is not enabled in QSPI_open(). This is why the code gets stuck when calling QSPI_norFlashReadIntr() in polling mode.