• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 99 subscribers
  • Views 924 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.

[66AK2G02] Diagnostic for uart2usb

Naoki Kawada
Guru 19890 points

Hi,

I followed this wiki and everything seemed functional, but I have a question about uart2usb.

When I invoke diagnostic test for uart2usb, the control does not come back to console. Here is a snapshot.

What can I do for next ? I found a UART0_DB9_EN switch and tried to enable J23 USB connector. When I saw the above message via DB9, I additionally connected USB cable to J23 connector, but unfortunately, I could not see any messages via that port. 

Best Regards,
Naoki

  • 0
    TI__Guru* 81335 points
    Hi Naoki-san,

    I have assigned this thread to factory team for appropriate response. Thank you for your patience.
  • 0
    TI__Guru** 116780 points
    Naoki,

    I have reproduced the issue at my end. I will consult with the developer and get back to you.

    I also observed the issue when I directly load the uart2usb_diagExample_evmK2G_armv7.out from pdk_k2g_1_0_1\packages\ti\board\bin\evmK2G\armv7 folder.

    It appears as if the UART connect is lost with the SOC and there is no activity even if the code is executing on the ARM.

    I will get back to you on this issue shortly.

    Regards,
    Rahul
  • 0 in reply to Rahul Prabhu
    TI__Guru** 116780 points
    Naoki-san,

    We have debugged the issue with the example. It appears the example requires users to connect your host PC to the mini USB2UART connector and the RS232 connector. The first set of print messages will go to the RS232 connector (if CP2105_EN = OFF) then the messages to confirm the test passed are sent to the mini USB2UART connector and then the control returns back to the RS232 connector.

    If you look at the source the test case is driving the GPIO pin that determines if the output goes to miniUSB port or to the RS232 connector. The functionality needs to restore the GPIO setting that was done through hardware before exitting the test case which it doesn`t seem to be doing.

    I have filed a bug against this operation.

    Regards,
    Rahul