• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 82 subscribers
  • Views 970 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.

Original question:

CCS/LAUNCHXL-F28379D: USING SCI_A and SCI_B simultanously

CCS/LAUNCHXL-F28379D: SCI-B and C no activity on Oscilloscope

Cristobal Cardenas
Prodigy 20 points

Part Number: LAUNCHXL-F28379D
Other Parts Discussed in Thread: C2000WARE

Tool/software: Code Composer Studio

Hello everyone,

Im working with the LAUNCHXL-F28379D and im currenly trying to use the SCI. Currenlly, the SCI-A is working with USB, i make a simple program to test de SCI:




This send the data throw SCI-A (USB) to a Hyperterminal, as you can see in the next image:

The problem is when i tried to look the data in the osciloscope, but, with the SCI-B (Pin 18) and SCI-C (Pin 56). In the simulink program, i only change the SCI module, from A to B or C, to conect my osciloscope an look the data but, no data is registered. 

How can I configure SCI_B or SCI_C on the board, to make it work?  

  • 0
    TI__Mastermind 19795 points

    Hi,

    Thanks for your question! From a hardware standpoint, the board only has SCI-A routed to the UART / XDS100 transceiver/debugger. And these are only specifically for the GPIO pins GPIO42 and GPIO43. Please search for "ISO7231CDWR" in the schematic section of the LAUNCHXL-F28379D Overview User's Guide document (which can be found in <C2000Ware>\boards\LaunchPads\LAUNCHXL_F28379D\R2.0\documentation, or at this link here).

    If you are required to use the SCI-B and SCI-C, you can purchase an external UART transceiver (like the FT2232HQ-REEL used on the board for debug/serial comms, or similar FTDI connection that is compatible with the information outlined in the SCI section of the TRM), wire to the particular pins for SCI-B/C, and then communicate with your PC.

    Regards,

    Vince

  • 0 in reply to Vince
    Prodigy 20 points

    Thanks for answering my question. I dont want to use SCI-B/C to communicate with my PC, i just want to look the data in the osciloscope, but, no data is registered. I dont know if i need a simulink configuration or a Jumper configuration to let de SCI start, not internally, like the SCI A, but a externally configuration with the pins. 

    Now i´m trying to look in the osciloscope a easier code, justo a Digital Output with a pulse generator, but again, no data is registered on the pinout. I need to make another configuration? I already install all the things to make the embedded coder work, CCS and more, but i cant make the signals get out in the pinouts. 

  • 0 in reply to Cristobal Cardenas
    TI__Mastermind 19795 points

    Hi Cristobal,

    Thanks for the follow up, it makes sense what you are trying to do then.

    From a hardware perspective, the pins you chose should be fine as long as you have done the following:

    1. Ensure that when you say pin 18 and pin 56, you are talking about GPIO18 and GPIO56, not the pin numbers listed on the top of the LaunchPad. The pin numbers on the top of the launchpad are not the GPIO number. Those silkscreen numbers on the top to be matched to the correct GPIO, and the pin#-to-GPIO# values are in the Overview User's Guide document I mentioned above. For example, SCITXDC is on GPIO56, which is J5-pin 44.

    2. Ensure to properly configure the pin mux for the device in Simulink.

    Please keep in mind that in the E2E forums, we are not familiar with MATLAB/Simulink which use our devices, and therefore cannot debug software developed for it. We can however debug Code Composer Studio and our C2000Ware example projects with you if you would like to debug using that.

    However, from what you are trying to do, I think I can help point you in the right direction. The SCI-B and C communications will need to be configured to repeat the same exact information that SCI-A is outputting. In CCS, what you would need to do is configure all three SCI ports (I think you have done), and then every time you transmit on SCI-A, you must repeat the same transmit function on SCI-B and SCI-C. In CCS, this would be the SCI_write* commands. For example, it would be necessary to have three back-to-back write commands like the following:

    SCI_writeCharArray(SCIA_BASE, (uint16_t*)msg, 12);
SCI_writeCharArray(SCIB_BASE, (uint16_t*)msg, 12);
SCI_writeCharArray(SCIC_BASE, (uint16_t*)msg, 12);

    Notice how all three SCIA/B/C are sending the message.

    Again, for how this is implemented in Simulink, we cannot really debug further than this, but I do believe the above information will point you in the right direction. If you have any additional questions, please make sure to follow up with this question on the Simulink forums!

    Regards,

    Vince