• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 47 subscribers
  • Views 157 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.

PLC010935BP: PLC010935BP bring up

robin wesson
Prodigy 20 points

Part Number: PLC010935BP
Other Parts Discussed in Thread: LP-MSPM0G3507, TIDA-010935, MSPM0G3507, C2000WARE, LM5164

Hi all, I'm trying to test a pair of PLC010935BP PLC communication eval boards using the LP-MSPM0G3507 launchpads. So far they aren't doing anything, no flashing LED's, no response to COM ports etc. Only a couple of static LEDs on. I'm powering the launchpad through USB and the daughter board through the AUX connector. J2 and J3 are directly wired from board to board.

I see a few E2E queries from folks trying to make this work. For example, the answer to this question seems to imply there is a com port attached but probably not mounted over USB:
https://e2e.ti.com/support/tools/simulation-hardware-system-design-tools-group/sim-hw-system-design/f/simulation-hardware-system-design-tools-forum/1472355/tida-010935-power-line-communication-uart-test-question?tisearch=e2e-sitesearch&keymatch=TIDA-010935#

Do I need some sort of USB to jumper UART module then?

The design guide doesn't talk much about how to configure the demo system
www.ti.com/.../tiduf48c.pdf

Section 3 of that guide seems to imply the messages should be pinging back and forth automatically - no need for a COM port. Maybe I need to monitor some variables in debug mode? 
"
• External loopback: The first data package is sent through the TIDA-010935 configuring the correspondent
GPIOs to allow data transmission. After the data is sent, the configuration changes in receive mode to wait
for the data to be sent back
• Echo interrupt : First configured in receive mode after some data arrives, switches in transmitting mode and
sends the data back, after the transmission returns back in receive mode.
"

In short I need some kind of description of how to assemble and test the modules - maybe I missed something? 

  • 0
    TI__Expert 5015 points

    Hi,

    Thanks for reaching out.
    Please find a short description fo the setup below:

    1. Connect both PLC boards the MSP-M0G307 Launchpads via the launch pad connectors:
    2. Connect the two PLC PCBs to each other using connectors J2 and J3
      1. If there is voltage present between J2 and J3 (13.5V to 50V) then place jumper J4
      2. If there is no voltage present between J2 and J3 remove jumper J4 and connect an auxiliary power supply to the AUX_Supply screw terminal
    3. Connect the Launchpads via the USB cable to the PC
    4. Flash the according software projects TIDA_010935_UART_echo and TIDA_010935_UART_ext_looopback to the boards.
    5. After programming the software projects with CCS keep the in Debug view and you can obserev the sent and received data in the expressions window by observing the variables: txData and rxData in the echoback project
    6. You can change the carrier frequency and filter configuration by changing fCarrier.frequency.


    Hope this helps.

    Best regards,

    Andreas

  • 0 in reply to Andreas Lechner
    Prodigy 20 points

    Thanks Andreas. My colleague worked out that we need to remove jumper J18 on the launchpad LP-MSPM0G3507, and flip J14 / SW1 from PB23 to PA9. Also edit the code in the loopback end to "transmitActive = 1" (line 81). That's working for him but still not for me. Removing J18 allows the 12V rail to power up on the daughter board, and changing the code gives me a flashing blue LED on the loopback board, but still no current draw on the AUX power rail and no activity on the outputs. Also while I'm giving detailed feedaback, neither the UART or the Loopback projects would build until I excluded several files from the build process. These files were: mspmog3507.cmd and startup_mspm0g3507.tilang.c

    Errors with these two in the build are:

    [0]"syscfg/device_linker.cmd", line 40: error #10263: FLASH memory range has already been specified
    [1]"syscfg/device_linker.cmd", line 40: error #10264: FLASH memory range overlaps existing memory range FLASH
    [2]"syscfg/device_linker.cmd", line 41: error #10263: SRAM memory range has already been specified
    [3]"syscfg/device_linker.cmd", line 41: error #10264: SRAM memory range overlaps existing memory range SRAM
    [4]"syscfg/device_linker.cmd", line 42: error #10263: BCR_CONFIG memory range has already been specified
    [5]"syscfg/device_linker.cmd", line 42: error #10264: BCR_CONFIG memory range overlaps existing memory range BCR_CONFIG
    [6]"syscfg/device_linker.cmd", line 43: error #10263: BSL_CONFIG memory range has already been specified
    [7]"syscfg/device_linker.cmd", line 43: error #10264: BSL_CONFIG memory range overlaps existing memory range BSL_CONFIG
    [8]error #10056: symbol "interruptVectors" redefined: first defined in "./startup_mspm0g350x_ticlang.o"; redefined in "./ticlang/startup_mspm0g3507_ticlang.o"
    [9]error #10010: errors encountered during linking; "TIDA_010935_UART_ext_loopback.out" not built

  • 0 in reply to robin wesson
    Prodigy 20 points

    Update... After another debugging session I discovered that, although I had 13V5 in from the AUX connector, I only had 3.0V on the power supply for the line driver IC. For eg: on C35. On the schematic the net name '12V' is the same on the 12V PSU as the power inlet to the driver, so there is nothing in between. Sure enough there was only 3.0V on L4 the 12V PSU inductor, and that 3.0V was there even if I switched off the 13V5 from my PSU.

    Long story short, I managed to get the 12V switcher to start by prodding the power good pin with a scope probe. Same issue on both my boards.

    My colleague hasn't seen this issue on the pair of boards he purchased. Is there a defective batch of the LM5164QDDARQ1 devices? 

    Thanks and best, Rob.

  • 0 in reply to robin wesson
    TI__Expert 5015 points

    Hello Robin,

    Thank you for the detailed feedback.
    Regarding the problems with building the code can you please share which version of CCS and C2000Ware you are using?
    The test software was written some time ago, so i could imaging there is some conflict in the dependencies.

    Does the 12V enable when you increase your auxiliary supply to 15 or 20V? There is a UVLO of TPS26624 at 13.5V but maybe the threshold is not to accurate. SO please check the voltage on C20 and confirm if the e-fuse is turning on or not.
    There is also UVLO at 13.5V from LM5164 so if there is Voltage on C200 but not on C21 then there might be an issue with LM5164.

    Hope this helps.

    Best regards
    Andreas