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

DM368 and UART1 issue

John Anderson
Genius 5240 points

I'm using the DM368 chip and UART1 appears to not be operational.  If I "cat /proc/tty/driver/serial" is shows UART1 as unknown.  I've checked the kernel code and by all appearances UART1 is activated.  So my next guess is that it's activated in the kernel but maybe some GPIO pins are configured wrong and the H/W doesn't respond to the kernel.  Off hand I'm thinking that the GPIO is just for routing the signals to the outside, but I'm open to anything at this point and need to do some more research on how the GPIO and UART interact.

 Anyone run into this yet?

John A

  • 0
    Genius 5240 points

    In case anyone is interested, I found the solution.

    1) The address of UART1 in the kernel is wrong.  Check the memory map of the DM368/DM365 against the value of DAVINCI_UART1_BASE.  That's why the UART doesn't respond to the kernel.

    2) There are two different GPIO pins that can be assigned to UART1.  Make sure that you have the correct pins enabled.

    John A

  • 0 in reply to John Anderson
    TI__Mastermind 19985 points

    Hi John,

    Thanks for sharing the information. BTW, i just wanted to clarify that we should use DM365_UART1_BASE. This is because on DM365 the base address for UART1 is changed and hence a separate definition is created. BTW, i am saying this w.r.t. LSP 2.10. Not sure though, how it is on LSP 3.xx

     

    Regards,

    Anshuman

  • 0 in reply to Anshuman Saxena
    Genius 5240 points

    I'm using dvsdk_4_00_00_22.  Also it seems to me that the pin mux assignments should be in the board specific code instead of dm365.c.  Pin assignments are specific to the board design, not the DM365.

    John A