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.

RM46L852: Development kit out of the box question

Part Number: RM46L852
Other Parts Discussed in Thread: HALCOGEN

Hello, I've just been assigned to a project using: 

 http://www.ti.com/tool/TMDXRM46HDK

and I need to know if the kit out of the box had a bootloader or any type of code installed prior to our previous engineers who jtagged it in its current state, I am getting USB descriptor failures as a slave device when I plug it into a windows 10 computer.

USBView is saying USB descriptor failure upon enumeration. 

I ask because if there is a default image that can be restore to the dev kit, it would put us back on track to sort out what went wrong in the previous engineers development path.

Thank you for any help or insight you can provide.

Chris

  • Hello Chris,

    There is no bootloader on the device on the HDK. It may contain the HDK connectivity test code. The HDK manufacturer tests the HDK functionality before pack it. The code does the selftests, then wait for the user's input (PC GUI) to do tests (Ethernet loopback, ADC, GIO, CAN communication between CAN 1 and CAN2, LED blinky, etc).

    This code should not affect the JTAG connection.
  • Ok, so to wrap my head around my issue, if I am getting USB descriptor failures with the dev board set as a device and not a host, is that issue stemming from the HAL creation parameters? 

    We have it set to usb device drivers just to get a basic startup to attached to a windows pc and usbview shows us descriptor failures.....so there is no PID/VID or are we able to proceed to load either a class compliant driver or TI specific driver for the device.

    Any thoughts on what may cause that particular error?

    Thank you,

    Chris

  • Hi Chris,

    I am sorry that I may misunderstand your question. My understanding is that the new HDK (out of box) has JTAG connection issue (USB description error, the HDK has a built-in emulator XDS100V2).
  • Well as it turns out, the halcogen software is where the problem is. We set up the USB and set the crossbar options we want, when the code is generated, the pinmux.c file is created, but what we found is AFTER the pinmux generation is completed (which match a "working" project found on Google), comparing the two files showed the values to not be equal.

    There is "additional" pinmux definitions being readjusted which directly affect the USB lines post setup of the halcogen routine. We are not sure where the extra lines of pinmux codes are coming from (clearly somewhere in halcogen, but not sure where/why) but after commenting out the extra lines of code that affect the USB pinmux setup, the pcb came right up as a device/host and all was good.

    This affect both device and host modes as the lines affected redirected to some other function other than USB.

    Halcogen is a buggy tool, while I see its benefit in the big picture, it surely isn't ready for prime time unless this is the only process and tool chain you'll ever use in your lifetime.

    Given a choice going forward, I would steer clear of using any device that requires the use of this buggy software.