• State Answer Suggested
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 423 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

cc1310 launchpad 430boost-sharp96 spi conflict?

siegfried
Prodigy 70 points
Other Parts Discussed in Thread: CC1310

I use CC1310 LP together with the booster pack sharp display. TIRTOS mw for the display works well.

It stops working after having implemented SPI functions to work with the on-board external flash memory. The display handle does not initialise any more (Display_open) after previous SPI operation to read/write the external flash. I think the previous SPI operation is correctly terminated by using the bspSpiClose function. The spiHandle becomes uninitialised.

By the way. In difference to the SPI handle the LCD handle (hDisplayLcd) stays initialised after having closed the session (Display_close). This indicates a different implementation in the firmware stack and maybe to a permanent allocation of the SPI bus.

  • 0
    TI__Guru**** 317180 points
    Do you have a minimal project that shows the issue?
  • 0 in reply to TER
    Prodigy 70 points
    The matter mostly is solved after having used the latest source files for ExtFlash from the latest tirtos release 2_20_00_06. Because there is no library element I copied the source code into the project.
    To avoid SPI conflicts I carefully have to open/close each device driver (Flash, Display) before use. I haven't seen any good documentation about that but technically SPI access just requires to activate device's select line. Having this in mind it seems that the software implementation in tirtos is a bit overdone.
    What still exists is that the Display handle is not cleared after Display_close and that this is different to the SPI handle. Maybe it is just a matter of the IDE itself, I use IAR.
    So the main issue issue is solved based on latest code from tirtos 2_20_00_06 and the ticket can be closed.