• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 31 subscribers
  • Views 847 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.

Trouble with loopback test when using MIBSPI1 on launchxl2-RM46

shruthi v
Intellectual 435 points

Other Parts Discussed in Thread: LAUNCHXL2-RM46, HALCOGEN

Hi,


I am working on mibspi1 module of launchxl2-rm46. when i externally short these two pins (mibspi1somi_1(J10-24pin) and mibspi1simo_1(J10-26pin) )and send the data i am not able to see anything on scope. and mibspi1clk is low....attaching the entire project for reference.


1. should i use any internal event to trigger the clock?? or trigger the transfer?

2. Is my pinmux settings correct and the directions for mibspi1somi_1 and mibspi1simo_1 and clock ?

Can anyone please guide me on when to use direction tab in halcogen and importance of pull select and pull down.

Thanks and Regrads,

Shruthi4061.SPI_SDCARD.zip

  • 0
    TI__Guru**** 191886 points
    Hi Shruthi,

    First of all, I wonder why you are using mibspi1somi_1 and mibspi1simo_1 rather than mibspi1somi and mibspi1simo on the J9 connector. The MibSPI1 module can support parallel mode in which 2 SOMI and 2 SIMO pins can be used to transfer data in order to increase throughput. When you are not in parallel mode, the mibspi1somi_1 and mibspi1simo_1 are not used in functional mode. However, you can still use them as regular GIO.

    The pinmux setting is fine if you are truly going to use parallel mode. If you are using only SIMO and SOMI pair then you don't have really have to configure the pinmux.

    As far the pull select is concerned these are only relevant if you are using the pins in GIO mode. Their configuration has no effect if you are in functional mode.