• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 81 subscribers
  • Views 306 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.

LAUNCHXL-F28069M: Question regarding the availability of the dedicated CAN (and eQEP) interface when using Boosterpacks

Daniel Bubalik
Prodigy 30 points
Part Number: LAUNCHXL-F28069M
Other Parts Discussed in Thread: BOOSTXL-DRV8305EVM, C2000WARE, SYSCONFIG

Dear TI Community,

i am developing an autonomous vehicle and plan to use the several LAUNCHXL-F28069M Board with 2 BOOSTXL-DRV8305EVM BLDC Driver each. The Launchpad has dedicated Interfaces for CAN-bus and for 2 eQEP encoders. Those peripherals can also be interfaced through muxing of the 40-pin connectors used for connecting a boosterpack. However since i am already using 2 Boosterpacks, the corresponding pins will most likely be muxed and used for a different function. My question is, does this disable the functionality of the CAN and the eQEP entirely, or can i still access those through use of the dedicated headers?

Regards
Daniel

  • 0
    TI__Mastermind 45376 points

    Hi Daniel,

    I'd suggest reviewing the schematic for the board within C2000ware to review compatibility. Located in the directory below:

    C:\ti\c2000\C2000Ware_3_01_00_00\boards\LaunchPads\LAUNCHXL_F28069M

    On the F2806x LaunchPad GPIO30 and GPIO31 are only used for the CAN interface, so you're good to go there.

    The eQEP signals go to both the QEP headers on the board and the boosterpack headers. You'll need to check if the shared GPIOs are already being used.

    Best,

    Kevin

  • 0 in reply to Kevin Allen18
    Prodigy 30 points

    Hi Kevin,

    thanks for the reply.

    In the Document SPRUI11B i have checked the tables 3 - 6 for pin mux options and it appears that each input required for interfacing an encoder (A,B and I) is available on 2 pins each. For example EQEP1A is shared with GPIO20 (like in your picture) on pin 45 but also shared with GPIO50 on pin 13. Some of the pins however are already in use by the boosterpacks (for example GPIO50/pin 13). When configuring the eQEP peripheral can i chose which pins to use (the unused ones) and then just set the correct mux option for the corresponding pins?

    Regards

    Daniel

  • 0 in reply to Daniel Bubalik
    TI__Mastermind 45376 points

    Hi Daniel,

    While there are alternate MUX options for eQEP A and B signals like you've noted, only the GPIOs shown in the schematic image I previously posted go to the QEP headers at the bottom of the board. These signals are also level-shifted to 5V, the alternate ones won't be (check encoder for voltage level output).

    Please see the eQEP examples within C2000ware to see how to set the input/MUX options for the QEP peripheral:

    C:\ti\c2000\C2000Ware_3_01_00_00\device_support\f2806x\examples\c28\eqep_pos_speed

    C:\ti\c2000\C2000Ware_3_01_00_00\device_support\f2806x\examples\c28\eqep_freqcal

    Best,

    Kevin

  • 0 in reply to Kevin Allen18
    Prodigy 30 points

    Hi Kevin,

    I have checked and verified with the SysConfig Tool that the GPIOs that go to the QEP headers are not used by any BoosterPack and thus my design should work.

    I thank you very much for your help.

    Regards,

    Daniel