• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 98 subscribers
  • Views 136 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.

AM5728: Facing issue with configuring the UART1 AM5728

Hanmant Gaikwad
Prodigy 110 points
Part Number: AM5728
Other Parts Discussed in Thread: PMP

Tool/software:

Hi All,

Custom Board : Based Ti sitara AM5728
OS version :VxWorks 21.07.

I'm facing issue with configuring Uart1 on Custom board.
I have been added its property in dts file as below,
serial1: serial@4806A000 
{
compatible = "ti,am5-uart";
reg = <0x4806A000 0x1000>;
interrupts = <72 0 4>;
clocks = <&uart1_gfclk_mux>;
clock-names = "uart1_gfclk_mux";
pinmux-0 = <&uart1_pads>;
};

//pin information
uart1_pads: uart1pads /* */
{
pin-set = <
0x17E0 0xE0000 /* rxd -> ball pin B27 */
0x17E4 0xA0000 /* txd -> Ball pin C26*/
>;
};

and i can serial port ,

-> devs
drv refs name
1 [ 3] /
0 [ 3] /dev/null
7 [ 3] /devm
4 [ 5] /eeprom/0
15 [ 3] /input/event
18 [141] /mmc1
0 [ 3] /null
9 [ 3] /ram
14 [ 3] /romfs
6 [ 3] /shm
3 [ 5] /ttyS0
3 [ 5] /ttyS1
2 [ 3] /tyCo/0 ==> /ttyS0
2 [ 3] /tyCo/1 ==> /ttyS1 //this uart1

I'm not able send and receive data over on it .Can anyone please help me with this.

Also , can you guys confirm me is this configuration correct for uart1 in dts file.

  • 0
    TI__Mastermind 31945 points

    Hello  Hanmant,

    The pin-muxing for theis device cannot be done from the DTS, it has to be done via u-boot, mux_data.h file.

    See https://e2e.ti.com/support/processors-group/processors/f/processors-forum/984326/am5728-pin-muxing-question

    -Josue

  • 0 in reply to Josue Zamitiz-Ayala
    Prodigy 110 points

    Hello Josue,

    I can able see the u-boot messages on console but im not able to see application side debug log message 

    U-Boot 2016.05 (Mar 07 2025 - 17:10:15 +0530)

    CPU : DRA752-GP ES2.0
    Model: TI AM5728 IDK
    Board: AM572x IDK REV <NULL>
    DRAM: 2 GiB
    MMC: no pinctrl for sdr104
    no pinctrl for ddr50
    no pinctrl for sdr50
    no pinctrl for sdr25
    no pinctrl for sdr12
    OMAP SD/MMC: 0, OMAP SD/MMC: 1
    reading uboot.env

    ** Unable to read "uboot.env" from mmc0:1 **
    Using default environment

    I2C chip 50: requested alen 2 does not match chip offset_len 1
    SCSI: SATA link 0 timeout.
    AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
    flags: 64bit ncq stag pm led clo only pmp pio slum part ccc apst
    scanning bus for devices...
    Found 0 device(s).
    Net: <ethaddr> not set. Validating first E-fuse MAC
    cpsw
    Hit any key to stop autoboot: 0
    switch to partitions #0, OK
    mmc0 is current device
    SD/MMC found on device 0
    reading boot.scr
    ** Unable to read file boot.scr **
    reading uEnv.txt
    2146 bytes read in 4 ms (523.4 KiB/s)
    Loaded env from uEnv.txt
    Importing environment from mmc0 ...
    Running uenvcmd ...
    reading vxWorks.bin
    ## Starting application at //till here i can see message only

  • 0 in reply to Hanmant Gaikwad
    TI__Mastermind 31945 points

    Hello Hanmant,

    Due to low bandwidth, I will have to take a look next week. 

    Please use previous e2e threads as guidance for now.

    Please keep in mind that TI does not support application level debugs, for this you should contact Wind River support.

    -Josue

  • 0 in reply to Josue Zamitiz-Ayala
    TI__Mastermind 31945 points

    Hanmant,

    Please correct me if I am understanding you correctly. 

    You are using UART1 for your terminal logging prints. You can see your prints fine up to u-boot prompt and then once it does the handoff to the filesystem you no longer see anything else?

    So it is an issue at your application level that you can no longer see more prints?

    If this is the case than it could be that you have a conflict in how the FS has the uart  enabled. Essentially. u-boot DTS vs Linux image DTS conflict of sorts. We do not support vxWorks in this forum. 

    -Josue