We have developed a custom board with an mDot installed on it as per spec. However for debugging purposes prior to going to pre-production we use the MTSLog to assess the state of the application.
In the UDK board the debug output shows up without any issues on the debug virtual COM USB port. However on our custom board I don’t see anything being displayed. We are able to upload the custom firmware successfully via the ymodem and the bootloader indicates that the application was loaded successfully.
I see the bootloader related log info show up on the debug com ports but not the application related log info.
So we also tried uploading the AT firmware, via the ymodem, and it loaded successfully. Normally the AT firmware sends a message to the debug output indicating “MDot Ready”, but we don’t see that message either.
Is there anything specifically required on our custom board to enable these debug outputs to show up and any guidance related to this issue will be greatly appreciated as we want to finalize on our board design ASAP.
Thanks,
Ajay