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.

How to enable multi UART support in AM335x BSP??

Hello Friends, 

I need to enable multi UART support for our board. Default UART0 is for debugging Purpose. Now, I want to use UART3 for our board..... 

In base board Expansion slot, the

X_UART3_RX is connected with pin 43

X_UART3_TX is connected with pin 45

In SOM, UART3_RX is using MII1_RXD3 signal.

So, in bsp_padcfg.h, bsp_padcfg.c .. I have to search for 

UART3 or MII1_RXD3

  • Hi,

    the Adeneo WEC7 ARM-A8 Version 02.30.00 BSP names the pads roughly in accordance with the names in the processor datasheet. I am not sure what pins 43 and 45 are, but If you are using pin L17 (for ZCZ package) or N17 (ZCE package) on your AM335X processor for uart3_rxd, then the pin/pad name is MII1_RXD3; you then need to configure that pad to run in Mode 1 to define it as a UART3_RXD as per Table 2-7 of the processor datasheet.

    The same process goes for the UART3_TXD.

    Cheers

    John

  • Hello John,

    Yes, the corresponding according to datasheet and schematic and pin configuration the corresponding pin is MII1_RXD3. But, the point is that how to  corresponding entry in the bsp_cfg.h and bsp_cfg.c .. WHat changes I have to do there...Please help me for this????

  • You really just need to do the same thing that has been done for UART0 and other pad config definitions within bsp_padcfg.h. Anyway, as it turns out, our BSP uses UART3 on the same pin for RX anyway:

    In bsp_padcfg.h:

    #define UART3_PADS \

    PAD_ENTRY(MII1_RXD3, (MODE(1) | PULLUDEN | RXACTIVE)) /* UART3_RXD */ \

    PAD_ENTRY(MII1_RXD2, (MODE(1) | PULLUDEN)) /* UART3_TXD */ \

    In basp_padcfg.c

    const PAD_INFO UART3Pads[] = {UART3_PADS END_OF_PAD_ARRAY};

    Then add

    { UART3Pads, AM_DEVICE_UART3},

    entry to

    const BOARD_PIN_MUX_T BOARD_PIN_MUX[] = {

  • Hello John

    What changes you said, I have done accordingly in my BSP code. Before these changes my 3.5 and 7" LCD was working fine. But after applying changes, the kernel images is not booting and hence display is not coming on the screen. still 4 different color squares are mentioned on the screen .... 

    After commenting all the changes and rebuilding I am facing the same problem; display is not coming...

    What do you think what may be the cause of this problem????

  • Hi Vijay,

    can you provide the trace of the messages output over UART0?  Also which UART driver are you enabling in your OS design Catalog?

    Cheers

    John

  • I have selected UART1, UART2, UART3 & UART3

  • Hello friends,

    I have enabled Kernel debugger and enable KITL and build my OS design in Debug mode.. Now I have found one thing that it stuck after Ethernet Init

    my logs are as -

    Windows CE Kernel for ARM (Thumb Enabled) Built on Jan 6 2011 at 16:15:31
    ProcessorType=0c08 Revision=2 CpuId=0x413fc082
    OEMAddressTable = 8000d6bc
    CPU CP15 Control Register = 0xc5387f
    CPU CP15 Auxiliary Control Register = 0x42
    Initializing VFP, FPSID=410330c3
    +OALTimerInit(1, 24000, 200)
    --- High Performance Frequecy is 24 MHz---
    Changed KITL zone mask to 0x0000B003
    +OALKitlStart
    +OALKitlInit(' s', 0x 8X - -2147257352/41/0x 8X, 0x 8X)
    DeviceId................. AM335X-
    pArgs->flags............. 0x29
    pArgs->devLoc.IfcType.... 0
    pArgs->devLoc.LogicalLoc. 0x4A100000
    pArgs->devLoc.PhysicalLoc 0x0
    pArgs->devLoc.Pin........ 0
    pArgs->ip4address........ 1
    pDevice->Name............ s
    pDevice->ifcType......... 0
    pDevice->id.............. 0x4A100000
    pDevice->resource........ 0
    pDevice->type............ 2
    pDevice->pDriver......... 0x83C7F000
    +OALKitlFindDevice(0/0/4A100000, 0x83C7F02C)
    -OALKitlFindDevice(pDevice = 0x83C7F02C(Internal EMAC), PhysicalLoc = 0x90500000)
    g_kitlLock = 0x83CBBD70
    +OEMKitlInit(0x83cbcee0)
    +OEMKitlInit(0x 8x)
    +OALKitlEthInit('AM335X-', 'Internal EMAC', 0x83C7F510, 0x83CBCEE0)
    +Cpsw3gInit(0x4A100000, 0x00000001, 0x83c7f528) v0.3

  • Hello Friends,

    My display is working fine after made certain changes in catalog items but still multi-UART is not working fine. 

    I have downloaded Terminal CE and installed it in WinCE OS. It is displaying three COM ports COM0(default),

    COM2 and COM5.

    and when i select COM5 with accurate baud rate and connect UART3 for loop back... It displays the message on the WinCE screen.. Unable to open port......

    I got these messages after enabling KITL with retail messages 

    IsValidMBR: MBR sector = 0x100 (valid MBR)
    OpenPartition: Partition Exists=0x1 for part 0x20.
    BP_SetDataPointer at 0x1d1b9f0
    BP_SetDataPointer at 0x0
    WriteData: Start = 0x0, Length = 0x1d1b9f0.
    NK image written
    Launch Windows CE image by jumping to 0x8000b4e0...

    Windows CE Kernel for ARM (Thumb Enabled)
    CPU CP15 Control Register = 0xc5387f
    CPU CP15 Auxiliary Control Register = 0x42
    +OALTimerInit(1, 24000, 200)
    --- High Performance Frequecy is 24 MHz---
    -OEMInit
    PID:00400002 TID:00410002 SetOpp: choosing AM335X_REV_ES1_0
    PID:00400002 TID:00410002 SetOpp to 3
    PID:00400002 TID:00510002 OALIoCtlHalInitRTC: Initializing RTC
    PID:00400002 TID:00510002 RTC_SetTime() = 2006.01.01 12:00:00.000
    PID:00400002 TID:00510002 Read: Attempts = 2
    PID:00400002 TID:00510002 Read: Attempts = 3
    PID:00400002 TID:00510002 Read: Attempts = 4
    PID:00400002 TID:00510002 Read: Attempts = 5
    PID:00400002 TID:00510002 WARN: I2C: Read failed (slave addr=0x68, register=0x00000000)
    PID:00400002 TID:00510002 Write: Attempts = 2
    PID:00400002 TID:00510002 Write: Attempts = 3
    PID:00400002 TID:00510002 Write: Attempts = 4
    PID:00400002 TID:00510002 Write: Attempts = 5
    PID:00400002 TID:00510002 WARN: I2C: Write failed (SA=0x68, register=0x00000004)
    PID:00400002 TID:00510002 Write: Attempts = 2
    PID:00400002 TID:00510002 Write: Attempts = 3
    PID:00400002 TID:00510002 Write: Attempts = 4
    PID:00400002 TID:00510002 Write: Attempts = 5
    PID:00400002 TID:00510002 WARN: I2C: Write failed (SA=0x68, register=0x00000000)
    PID:00400002 TID:00850006 CM3: input file [\windows\firmware.bin] is 9932 bytes long
    PID:00400002 TID:00850006 CM3: firmware file read ok!

    .Now also building the image in debug mode. will update you soon

  • This is the debug log 

    +OALTimerInit(1, 24000, 200)
    --- High Performance Frequecy is 24 MHz---
    -OEMInit
    NKStartup done, starting up kernel. nCpus = 1
    Windows CE KernelInit
    Error Reporting Memory Reserved, dump size = 0004b000
    Booting Windows CE version 7.00 for (ARM)
    Memory Configuring: Total pages: 103124, Filesystem pages = 32751
    Booting kernel with clean memory configuration:
    Total Memory Sections:3
    [0] (static): start: 83cdd000, extension/attributes: 00025000, length: 092d4000
    [1] (dynamic): start: 00960000, extension/attributes: 00028800, length: 0a000000
    [2] (dynamic): start: 00900000, extension/attributes: 00018800, length: 06000000
    Scheduling the first thread.
    PID:00400002 TID:00410002 PGPOOL: Reserved 768 pages for Loader pool
    PID:00400002 TID:00410002 PGPOOL: Reserved 256 pages for File pool
    PID:00400002 TID:00410002 OSAXST0: Platform Name = PhyCORE_AM335x RDK
    PID:00400002 TID:00410002 OSAXST1: >>> Loading Module 'kd.dll' (0x9E801ED0) at address 0xEFFE0000-0xEFFFE000 in Process 'NK.EXE' (0x83CBFAD0)
    PID:00400002 TID:00410002 KD: Starting kernel debugger software probe (KdStub) - KD API version 27
    PID:00400002 TID:00410002 OSAXST1: >>> Loading Module 'NK.EXE' (0x83CBFAD0) at address 0x80002000-0x80036000 in Process 'NK.EXE' (0x83CBFAD0)
    PID:00400002 TID:00410002 SetOpp: choosing AM335X_REV_ES1_0
    PID:00400002 TID:00410002 SetOpp to 3
    PID:00400002 TID:00410002 Message Queue support initialized, g_hMsgQHeap = a28c0010
    PID:00400002 TID:00500002 OSAXST1: >>> Loading Module 'filesys.dll' (0x9E802AD4) at address 0xEFC70000-0xEFD3A000 in Process 'NK.EXE' (0x83CBFAD0)
    PID:00400002 TID:00500002 OSAXST1: >>> Loading Module 'fsdmgr.dll' (0x9E802C0C) at address 0xEF810000-0xEF858000 in Process 'NK.EXE' (0x83CBFAD0)
    PID:00400002 TID:00520002 FileSystem Starting - starting with clean file system
    PID:00400002 TID:00520002 OALIoCtlHalInitRTC: Initializing RTC
    PID:00400002 TID:00520002 RTC_SetTime() = 2006.01.01 12:00:00.000
    PID:00400002 TID:00520002 WARN: TransactI2CPacket: No ACK from slave device with address 0x68, stat = 0x1002
    PID:00400002 TID:00520002 Read: Attempts = 2
    PID:00400002 TID:00520002 WARN: TransactI2CPacket: No ACK from slave device with address 0x68, stat = 0x1002
    PID:00400002 TID:00520002 Read: Attempts = 3
    PID:00400002 TID:00520002 WARN: TransactI2CPacket: No ACK from slave device with address 0x68, stat = 0x1002
    PID:00400002 TID:00520002 Read: Attempts = 4
    PID:00400002 TID:00520002 WARN: TransactI2CPacket: No ACK from slave device with address 0x68, stat = 0x1002
    PID:00400002 TID:00520002 Read: Attempts = 5
    PID:00400002 TID:00520002 WARN: TransactI2CPacket: No ACK from slave device with address 0x68, stat = 0x1002
    PID:00400002 TID:00520002 WARN: I2C: Read failed (slave addr=0x68, register=0x00000000)
    PID:00400002 TID:00520002 WARN: TransactI2CPacket: No ACK from slave device with address 0x68, stat = 0x1002
    PID:00400002 TID:00520002 Write: Attempts = 2
    PID:00400002 TID:00520002 WARN: TransactI2CPacket: No ACK from slave device with address 0x68, stat = 0x1002
    PID:00400002 TID:00520002 Write: Attempts = 3
    PID:00400002 TID:00520002 WARN: TransactI2CPacket: No ACK from slave device with address 0x68, stat = 0x1002
    PID:00400002 TID:00520002 Write: Attempts = 4
    PID:00400002 TID:00520002 WARN: TransactI2CPacket: No ACK from slave device with address 0x68, stat = 0x1002
    PID:00400002 TID:00520002 Write: Attempts = 5
    PID:00400002 TID:00520002 WARN: TransactI2CPacket: No ACK from slave device with address 0x68, stat = 0x1002
    PID:00400002 TID:00520002 WARN: I2C: Write failed (SA=0x68, register=0x00000004)
    PID:00400002 TID:00520002 WARN: TransactI2CPacket: No ACK from slave device with address 0x68, stat = 0x1002
    PID:00400002 TID:00520002 Write: Attempts = 2
    PID:00400002 TID:00520002 WARN: TransactI2CPacket: No ACK from slave device with address 0x68, stat = 0x1002
    PID:00400002 TID:00520002 Write: Attempts = 3
    PID:00400002 TID:00520002 WARN: TransactI2CPacket: No ACK from slave device with address 0x68, stat = 0x1002
    PID:00400002 TID:00520002 Write: Attempts = 4
    PID:00400002 TID:00520002 WARN: TransactI2CPacket: No ACK from slave device with address 0x68, stat = 0x1002
    PID:00400002 TID:00520002 Write: Attempts = 5
    PID:00400002 TID:00520002 WARN: TransactI2CPacket: No ACK from slave device with address 0x68, stat = 0x1002
    PID:00400002 TID:00520002 WARN: I2C: Write failed (SA=0x68, register=0x00000000)
    PID:00400002 TID:00520002 OSAXST1: >>> Loading Module 'romfsd.dll' (0x9E8032D0) at address 0xEFC60000-0xEFC67000 in Process 'NK.EXE' (0x83CBFAD0)
    PID:00400002 TID:00520002 OSAXST1: >>> Loading Module 'k.locale.dll' (0x9E805800) at address 0xEFDB0000-0xEFDF1000 in Process 'NK.EXE' (0x83CBFAD0)
    PID:00400002 TID:00520002 Warning! Kernel DLL 'k.locale.dll' is registered for thread creation/deletion notification.  To improve performance if you dont need thread notifications call DisableThreadLibraryCalls from inside DPID:00400002 TID:00520002 OSAXST1: >>> Loading Module 'k.normalize.dll' (0x9E805B78) at address 0xEFD60000-0xEFD80000 in Process 'NK.EXE' (0x83CBFAD0)
    PID:00400002 TID:00520002 Warning! Kernel DLL 'k.normalize.dll' is registered for thread creation/deletion notification.  To improve performance if you dont need thread notifications call DisableThreadLibraryCalls from insidPID:00400002 TID:00520002 OSAXST1: >>> Loading Module 'device.dll' (0x9E805EA8) at address 0xEF9B0000-0xEF9B5000 in Process 'NK.EXE' (0x83CBFAD0)
    PID:00400002 TID:00520002 OSAXST1: >>> Loading Module 'devmgr.dll' (0x9E806000) at address 0xEF970000-0xEF9A4000 in Process 'NK.EXE' (0x83CBFAD0)
    PID:00400002 TID:00520002 OSAXST1: >>> Loading Module 'k.ceddk.dll' (0x9E806138) at address 0xEE780000-0xEE795000 in Process 'NK.EXE' (0x83CBFAD0)
    PID:00400002 TID:00520002 OSAXST1: >>> Loading Module 'k.edmadrvr.dll' (0x9E806270) at address 0xEE6A0000-0xEE6BC000 in Process 'NK.EXE' (0x83CBFAD0)
    PID:00400002 TID:00520002 OSAXST1: >>> Loading Module 'pm.dll' (0x9E8063B8) at address 0xEF920000-0xEF94E000 in Process 'NK.EXE' (0x83CBFAD0)
    PID:00400002 TID:008B0006 OSAXST1: >>> Loading Module 'busenum.dll' (0x9E809EF0) at address 0xEF950000-0xEF95B000 in Process 'NK.EXE' (0x83CBFAD0)
    PID:00400002 TID:008B0006 OSAXST1: >>> Loading Module 'ccfgsvc.dll' (0x9E80A930) at address 0xEEAE0000-0xEEB0D000 in Process 'NK.EXE' (0x83CBFAD0)
    PID:00400002 TID:00520002 FSREG: Mounting clean system hive
    PID:00400002 TID:00520002 FSREG: Taking down boot registry.  Any open keys will be invalid.
    PID:00400002 TID:00520002 FSVOL: Using system database volume "\Windows\Registry\default.vol"
    PID:00400002 TID:00520002 OSAXST1: >>> Loading Module 'bcrypt.dll' (0x9E80BC20) at address 0xAAB70000-0xAABC2000 in Process 'NK.EXE' (0x83CBFAD0)
    PID:00400002 TID:00520002 Warning! Kernel DLL 'bcrypt.dll' is registered for thread creation/deletion notification.  To improve performance if you dont need thread notifications call DisableThreadLibraryCalls from inside DLLPID:00400002 TID:00520002 OSAXST1: >>> Loading Module 'k.sqlcese35.sys.dll' (0x9E80C30C) at address 0xEE7A0000-0xEE8FA000 in Process 'NK.EXE' (0x83CBFAD0)
    PID:00400002 TID:00520002 OSAXST1: >>> Loading Module 'k.fpcrt.dll' (0x9E80C668) at address 0xEFD40000-0xEFD5E000 in Process 'NK.EXE' (0x83CBFAD0)
    PID:00400002 TID:00520002 !!!WARNING: Mutually dependent DLL detected: FPCRT (pMod = 0x9e80c668)
                                                                                                    PID:00400002 TID:00520002 OSAXST1: >>> Loading Module 'k.ole32.dll' (0x9E80C7A0) at address 0xEE9F0000-0xEE9FF000 in Process 'NK.EXE' (0x83CBFAD0)
    PID:00400002 TID:00520002 Warning! Kernel DLL 'k.ole32.dll' is registered for thread creation/deletion notification.  To improve performance if you dont need thread notifications call DisableThreadLibraryCalls from inside DLPID:00400002 TID:00520002
    Initializing Database
    PID:00400002 TID:00520002 OSAXST1: >>> Loading Module 'k.sorting.dll' (0x9E80CD20) at address 0xEFD90000-0xEFDA5000 in Process 'NK.EXE' (0x83CBFAD0)
    PID:00400002 TID:00520002 Warning! Kernel DLL 'k.sorting.dll' is registered for thread creation/deletion notification.  To improve performance if you dont need thread notifications call DisableThreadLibraryCalls from inside PID:00400002 TID:00520002 OSAXST1: >>> Loading Module 'coredll.dll' (0x9E80D4A8) at address 0x40010000-0x40163000 in Process 'NK.EXE' (0x83CBFAD0)
    PID:00400002 TID:00520002 OSAXST1: >>> Loading Module 'oalioctl.dll' (0x9E80D5E0) at address 0xEFF50000-0xEFF55000 in Process 'NK.EXE' (0x83CBFAD0)
    PID:00400002 TID:00520002 CePerf.dll is absent - performance data will not be recorded
    PID:00400002 TID:008B0006 OSAXST1: >>> Loading Module 'am33x_cm3fw.dll' (0x9E80DA78) at address 0xEE750000-0xEE755000 in Process 'NK.EXE' (0x83CBFAD0)
    PID:00400002 TID:008B0006 CM3: input file [\windows\firmware.bin] is 9932 bytes long
    PID:00400002 TID:008B0006 CM3: firmware file read ok!
    PID:00400002 TID:008B0006 OSAXST1: >>> Loading Module 'am33x_gpio.dll' (0x9E80F98C) at address 0xEE650000-0xEE658000 in Process 'NK.EXE' (0x83CBFAD0)
    PID:00400002 TID:008B0006 OSAXST1: >>> Loading Module 'alpcd.dll' (0x9E80FD2C) at address 0xEEFC0000-0xEEFE9000 in Process 'NK.EXE' (0x83CBFAD0)
    PID:00400002 TID:008B0006 OSAXST1: >>> Loading Module 'tapi.dll' (0x9E8100E8) at address 0xEF0D0000-0xEF11D000 in Process 'NK.EXE' (0x83CBFAD0)
    PID:00400002 TID:008B0006 OSAXST1: >>> Loading Module 'waveapi.dll' (0x9E810528) at address 0xEF770000-0xEF7A6000 in Process 'NK.EXE' (0x83CBFAD0)
    PID:00400002 TID:008B0006 CePerf.dll is absent - performance data will not be recorded
    PID:01A6000A TID:01B3000A OSAXST1: >>> Loading Module 'coredll.dll' (0x9E80D4A8) at address 0x40010000-0x40163000 in Process 'udevice.exe' (0x9E810E40)
    PID:01A6000A TID:01B3000A OSAXST1: >>> Loading Module 'udevice.exe' (0x9E810E40) at address 0x00010000-0x0001E000 in Process 'udevice.exe' (0x9E810E40)
    PID:00400002 TID:01B3000A OSAXST1: >>> Loading Module 'locale.dll' (0x9E811C3C) at address 0x40170000-0x401B1000 in Process 'NK.EXE' (0x83CBFAD0)
    PID:01A6000A TID:01B3000A OSAXST1: >>> Loading Module 'locale.dll' (0x9E811C3C) at address 0x40170000-0x401B1000 in Process 'udevice.exe' (0x9E810E40)
    PID:00400002 TID:01B3000A OSAXST1: >>> Loading Module 'normalize.dll' (0x9E8120F0) at address 0x401E0000-0x40200000 in Process 'NK.EXE' (0x83CBFAD0)
    PID:01A6000A TID:01B3000A OSAXST1: >>> Loading Module 'normalize.dll' (0x9E8120F0) at address 0x401E0000-0x40200000 in Process 'udevice.exe' (0x9E810E40)
    PID:01A6000A TID:01B3000A CePerf.dll is absent - performance data will not be recorded
    PID:01A6000A TID:01B3000A udevice.exe $udevice_1001
    PID:01A6000A TID:01B3000A udevice: Registering udevice instance ($udevice_1001) with devmgr.
    PID:00400002 TID:008B0006 OSAXST1: >>> Loading Module 'softkb.dll' (0x9E8124A8) at address 0x40410000-0x40441000 in Process 'NK.EXE' (0x83CBFAD0)
    PID:01A6000A TID:008B0006 OSAXST1: >>> Loading Module 'softkb.dll' (0x9E8124A8) at address 0x40410000-0x40441000 in Process 'udevice.exe' (0x9E810E40)
    PID:0102001E TID:00B2001E OSAXST1: >>> Loading Module 'coredll.dll' (0x9E80D4A8) at address 0x40010000-0x40163000 in Process 'udevice.exe' (0x9E8128DC)
    PID:0102001E TID:00B2001E OSAXST1: >>> Loading Module 'udevice.exe' (0x9E8128DC) at address 0x00010000-0x0001E000 in Process 'udevice.exe' (0x9E8128DC)
    PID:01A6000A TID:008B0006 Deleting an uninitialized critical section 0x00030ed4, ignored!
                                                                                             PID:01A6000A TID:008B0006 Deleting an uninitialized critical section 0x00030ec0, ignored!
              PID:00400002 TID:008B0006 OSAXST1: >>> Loading Module 'ole32.dll' (0x9E8134A4) at address 0x40D60000-0x40E65000 in Process 'NK.EXE' (0x83CBFAD0)
    PID:01A6000A TID:008B0006 OSAXST1: >>> Loading Module 'ole32.dll' (0x9E8134A4) at address 0x40D60000-0x40E65000 in Process 'udevice.exe' (0x9E810E40)
    PID:00400002 TID:008B0006 OSAXST1: >>> Loading Module 'rpcrt4legacy.dll' (0x9E8135DC) at address 0x40F10000-0x40FB6000 in Process 'NK.EXE' (0x83CBFAD0)
    PID:01A6000A TID:008B0006 OSAXST1: >>> Loading Module 'rpcrt4legacy.dll' (0x9E8135DC) at address 0x40F10000-0x40FB6000 in Process 'udevice.exe' (0x9E810E40)
    PID:00400002 TID:008B0006 OSAXST1: >>> Loading Module 'lpcrt.dll' (0x9E813714) at address 0x40890000-0x40897000 in Process 'NK.EXE' (0x83CBFAD0)
    PID:01A6000A TID:008B0006 OSAXST1: >>> Loading Module 'lpcrt.dll' (0x9E813714) at address 0x40890000-0x40897000 in Process 'udevice.exe' (0x9E810E40)
    PID:0102001E TID:00B2001E OSAXST1: >>> Loading Module 'locale.dll' (0x9E811C3C) at address 0x40170000-0x401B1000 in Process 'udevice.exe' (0x9E8128DC)
    PID:00400002 TID:008B0006 OSAXST1: >>> Loading Module 'bcrypt.dll' (0x9E813F1C) at address 0x429F0000-0x42A42000 in Process 'NK.EXE' (0x83CBFAD0)
    PID:01A6000A TID:008B0006 OSAXST1: >>> Loading Module 'bcrypt.dll' (0x9E813F1C) at address 0x429F0000-0x42A42000 in Process 'udevice.exe' (0x9E810E40)
    PID:0102001E TID:00B2001E OSAXST1: >>> Loading Module 'normalize.dll' (0x9E8120F0) at address 0x401E0000-0x40200000 in Process 'udevice.exe' (0x9E8128DC)
    PID:0102001E TID:00B2001E CePerf.dll is absent - performance data will not be recorded
    PID:0102001E TID:00B2001E udevice.exe $udevice_0003
    PID:0102001E TID:00B2001E udevice: Registering udevice instance ($udevice_0003) with devmgr.
    PID:00400002 TID:00960006 OSAXST1: >>> Loading Module 'notify.dll' (0x9E8143CC) at address 0x40250000-0x4026B000 in Process 'NK.EXE' (0x83CBFAD0)
    PID:0102001E TID:00960006 OSAXST1: >>> Loading Module 'notify.dll' (0x9E8143CC) at address 0x40250000-0x4026B000 in Process 'udevice.exe' (0x9E8128DC)
    PID:00400002 TID:008B0006 ERROR! DEVMGR: Failed to load 'Drivers\BuiltIn\I2C'. dwStatus=0x2
    PID:00400002 TID:008B0006 OSAXST1: >>> Loading Module 'credsvc.dll' (0x9E81D618) at address 0x406A0000-0x406D5000 in Process 'NK.EXE' (0x83CBFAD0)
    PID:0102001E TID:008B0006 OSAXST1: >>> Loading Module 'credsvc.dll' (0x9E81D618) at address 0x406A0000-0x406D5000 in Process 'udevice.exe' (0x9E8128DC)
    PID:00400002 TID:008B0006 OSAXST1: >>> Loading Module 'fpcrt.dll' (0x9E81D970) at address 0x40210000-0x4022E000 in Process 'NK.EXE' (0x83CBFAD0)
    PID:0102001E TID:008B0006 OSAXST1: >>> Loading Module 'fpcrt.dll' (0x9E81D970) at address 0x40210000-0x4022E000 in Process 'udevice.exe' (0x9E8128DC)
    PID:0102001E TID:008B0006 !!!WARNING: Mutually dependent DLL detected: FPCRT (pMod = 0x00031250)
                                                                                                    PID:00400002 TID:017E0036 OSAXST1: >>> Loading Module 'credprov.dll' (0x9E81DEF0) at address 0x40CB0000-0x40CB6000 in Process 'NK.EXE' (0x83CBFAD0)
    PID:0102001E TID:017E0036 OSAXST1: >>> Loading Module 'credprov.dll' (0x9E81DEF0) at address 0x40CB0000-0x40CB6000 in Process 'udevice.exe' (0x9E8128DC)
    PID:00400002 TID:008B0006 OSAXST1: >>> Loading Module 'am33x_uart.dll' (0x9E81E0FC) at address 0xEE5D0ü

    I think so it stucks during the time of loading UART.dll...

    How to solve this problem...