• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 134 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TM4C123GE6PM: CUSTOM BOARD NOT RECOGNIZING AS A STELLARIS DRIVER

user5223470
Prodigy 205 points
Part Number: TM4C123GE6PM

Tool/software:

Hello,

I have two questions.

1. The USB connection in theTM4C123G launchjpad workshop pdf file is as follows. But R25 and R30 is not mounted on the TM4C123G launchpad. Then i guess for usb bootloader app GND, USB_DP and USB_DM is enough. PB0 and PB1 is not needed. I wonder if I understand the situation correctly?

 

2.  I designed a custom board. When I connect the custom board to the laptop, the laptop does not detect the custom board. I am using an unprogrammed blank processor. I can't see stellaris driver in the device manager.

When I try the same thing with launchpad, there is no problem. So, if I first erased the mcu on launchpad with icdi and then connect the launchpad to the laptop, launchpad appears as a stellaris driver in the device manager. 

The custom board has an external power supply. First, I power the board, then connect the USB cable to the laptop. MCU is TM4C123GE6PM. Crystal is 25Mhz

Regards

Erdem

  • 0
    TI__Guru**** 183736 points
    user5223470 said:

    1. The USB connection in theTM4C123G launchjpad workshop pdf file is as follows. But R25 and R30 is not mounted on the TM4C123G launchpad. Then i guess for usb bootloader app GND, USB_DP and USB_DM is enough. PB0 and PB1 is not needed. I wonder if I understand the situation correctly?

     

    That is correct. You do not need to populate R25/R30 if you are only operating in device mode. 

    user5223470 said:

    2.  I designed a custom board. When I connect the custom board to the laptop, the laptop does not detect the custom board. I am using an unprogrammed blank processor. I can't see stellaris driver in the device manager.

    When I try the same thing with launchpad, there is no problem. So, if I first erased the mcu on launchpad with icdi and then connect the launchpad to the laptop, launchpad appears as a stellaris driver in the device manager. 

    The LaunchPad has an onboard ICDI debug probe that is enumerated by another TM4C123 chip. The ICDI chip will enumerate as a Stellaris In-Circuit Debug Interface.  Look closely next to the USB Debug connector on the LaunchPad.

    There is another USB Device connector on the LaunchPad. When the flash is erased and If you connect a USB cable to the USB 'Device' connector, you will see a Stellaris DFU device enumerated. 

    I suppose your board has only a JTAG connector. You would need an external debug probe like XDS110/XDS200  to debug and program the target device on our custom board. 

  • 0 in reply to Charles Tsai
    Prodigy 205 points

    Thank you Charles for the answer.

    No The board has icdi jtag connector(micro ab) and usb connector.. 

    Jtag uses PC0-PC1-PC2-PC3

    And i can program the board using launcpad.

    And for usb, usb_dp(pin 44 PD5) AND usb_dm(pin 43 PD4) ports connected

    When i connect the board to laptop over usb connector laptop does not detect the board(Mcu is empty).

    Regards

    Erdem

  • 0 in reply to user5223470
    TI__Guru**** 183736 points

    You are saying you have another TM4C123 chip on your customer besides the target TM4C123 chip. Is that correct? What I'm not clear is why would you want to have two TM4C123 chips on the board. Once you are in production, the ICDI chip will not be used. If you need to debug, why wouldn't you use an external debug probe as all you need is a JTAG connector on your board. 

    Your TM4C123 for ICDI is empty. Therefore, there is no ICDI firmware in it. Without the firmware it does not function as a ICDI debug probe. However, as an empty chip, it should enumerate as a DFU device. Do you see that?

    If you don't have any hardware issue then you can try to update the firmware. See below.