I am wondering if anyone can explain the purpose of the debug UART driver (DUART1) with the i.MX28 Windows CE BSP, and perhaps the difference between the debug uart and an application uart?
The debug UART is set up very low level from the OEMDebugInit function. This is necessary so that the early boot up code can output messages via the debug port.
I have included the catalogue item for the debug uart (DUART1). I have noticed that once this driver loads I no longer see debug output messages during the boot process.
The debug uart compiles to debug_serial.dll. I assume that by including this in the build my application can access the uart to send / receive data as I think it enumerates as COM0.
Does this then prevent the debug port from outputting retailmsg debug messages from driver code? I.e. does the dll block the CE debug output and present this port for application use only?
Unfortunately this is not covered in the BSP documentation, just the application UART 2 and 5.
Thanks in advance, Mark