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.

CC3200MODLAUNCHXL: SPI question regarding how to communicate with external memory chip

Part Number: CC3200MODLAUNCHXL
Other Parts Discussed in Thread: CC3200, CC3220SF

I am working with the CC3200 and an external memory chip, IS25LQ032B. They are on the same board and I have confirmed that the the CS on the memory chip is being selected and deselected by the SPI. The current SPI APIs that the CC3200 do not support what I am trying to accomplish, so I'm trying to write my own methods. I am using the external memory as storage for log events, so I need to be able to tell save data at certain addresses on the memory chip. The part I'm having trouble with is the actual communicating with the external memory. I have experimented with using HWREG() with the register's used in the SPITransfer methods in spi.c in the CC3200 libraries, but this seems to not be working. I'm not sure if I'm missing out on a step or a piece of information. I enabled the SPI like the spi_demo, except when configuring it I use SPI_HW_CTRL_CS, because I configure the CS manually. Please advise!

  • Hi Margaret,

    When using the GSPI lines, using the HWREG() calls to configure the peripheral and execute transfers should work fine. I would not recommend mixing driverlib calls (from spi.c) with the HWREG() accesses while testing since both modify the registers. I think it will be easier to test by using the driverlib calls alone.

    We have not worked on this type of approach with our device because storing this type of information could be done on the external flash that the device already uses. For a more direct path to what you are trying to accomplish, I would recommend you take a look at the CC3220SF which has on-chip flash. You could reserve one bank of the flash for this type of data if you need strict control over the addresses where log events are stored.

    Best Regards,
    Ben M