| Author |
Topic |
|
|
KnowledgeBase
296 Posts |
 Posted - 25 Feb 2002 : 18:22:58
|
Q: I want to use the debug serial port for my application, and don't want debug data to come out that port. Can I suppress the debug port output?
Yes, change the debug port entry in the ADSLOAD.HWT file as follows:
0xC0000F40 0x00000001 ; Debug output: [00=show] 01=suppress
You will see the initial boot information, but once CE starts, there will be no further output of the debug port.
Alternatively, if the serial device connected to the debug serial port can't tolerate any extraneous data, you can suppress debug port output altogether. With Graphics Client Plus boot ROMs 1.66 and later, set DIP switch position 2 to ON. No information will be displayed on the debug port when the system boots or at any time during CE operation.
------------------
ADS Knowledge Base |
|
|
fcarpen
3 Posts |
Posted - 21 Nov 2002 : 14:14:26
|
Is there a way to suppress debug port output altogether for the Bitsy? Alternatively, is there a way to direct all debug port output to a different serial port (com1 or com2).
|
 |
|
|
akidder
1519 Posts |
Posted - 21 Nov 2002 : 15:41:44
|
#redirect
Hi Frank. We don't currently have Bitsy boot code that suppresses the initial debug output. If you need to suppress it, drop us a note with your application requirements and we'll see what we can do. Debug information can be pretty important, especially if your system isn't behaving as expected.
You should be able to redirect debug port output to another port with an entry in the ADSLOAD.HWT file. Here is an excerpt from the Bitsy ADSLOAD.HWT file (revision 700111-1707B) that gives further details about redirection and suppression:
; Debug port output
; - Initial debug port output always comes out Serial Port 3.
; - Redirect becomes active after CE is launched.
; - The "Suppress" entry turns off debug port output after the
; message, "CE starts From DRAM" has been displayed
; - To use debug menu or to view CE load status, use Serial 3
0xC0000F48 0x00000003 ; Debug output: 01=COM1 02=COM2 [03=COM3]
0xC0000F40 0x00000000 ; Debug output: [00=show] 01=suppress
For other readers of this post, note that the GC Plus and GMaster use the same entries. See your ADSLOAD.HWT file for details. |
|
|
|
Susan
123 Posts |
Posted - 03 Dec 2002 : 07:51:01
|
Drew,
We also need to switch our debug output from COM3. Therefore, I changed the pertinent line to:
0xC0000F48 0x00000002 ; Debug output: 01=COM1 [02=COM2] 03=COM3
Now, the 'standard' debug generated is:
__________________________________________
Windows CE Kernel for ARM Built on Oct 18 2001 at 16:13:02
ProcessorType=0b11 Revision=8
sp_abt=ffff5000 sp_irq=ffff2800 sp_undef=ffffc800
Windows CE Image was built at 09:53:24 on Jan 30 2002.
Initializing Ethernet debug services.
Sp=ffffc7d0
InitializeJit
UDA1341 Init
__________________________________________
I no longer get the following 'standard messages' (which normally follow UDA1341 Init)
__________________________________________
SMARTIO Detected : PartType=0x8535 Firmware=0x1021 Revision=5
UCB1200 Detected : ID = 0x1004
Microsoft Windows CE Ver. 3.0 (build 126)
ADS BITSY Windows CE Ver.(3.19)
__________________________________________
My problem is that any debug I am generating (using RETAILMSG) is not appearing. In lieu of my
debug, I get garbage characters.
I've tried a different cable with no luck.
I get full debug when I switch the HWT entry back to COM3 (and physically switch the cable). |
|
|
|
Susan
123 Posts |
Posted - 03 Dec 2002 : 08:03:53
|
Drew,
I just switched to COM1 and received all my debug. Any idea as to why COM2 is giving me difficulty? |
|
|
|
ALDATA
1 Posts |
Posted - 12 Mar 2004 : 14:12:22
|
Hello,
Is there a DIP switch setting to suppress all debug output on the AGX board?
Markus |
|
|
|
iwabernethy
4 Posts |
Posted - 03 Jun 2004 : 10:01:43
|
Is this possible on the BitsyX system? I don't recognise either of the settings in my adsload.hwt file. I can only see;
0xA1E30044 0x0000003 ; Debug Port
Should I replace this with something?
Or is there some other way that I can get to use the third com port for my application?
Iain |
|
|
|
ctacke
877 Posts |
Posted - 03 Jun 2004 : 10:03:10
|
Set it to the following:
0xA1E30044 0x0000000 ; Debug Port |
|
|
|
madav
15 Posts |
Posted - 09 Jun 2004 : 20:22:48
|
I tried the mentioned change for the BitsyX and I was able to supress the messages generated after CE starts. Is there some way of supressing all the debug messages in BitsyX
Thanks,
Madav |
|
|
|
ctacke
877 Posts |
Posted - 10 Jun 2004 : 09:16:06
|
| What version of the boot ROM are you running? |
|
|
|
madav
15 Posts |
Posted - 10 Jun 2004 : 10:24:32
|
| I am using CE.Net Build 4.10.36 and the ROM is 1.10 |
|
|
|
alintz
12 Posts |
Posted - 15 Apr 2005 : 11:26:59
|
BitsyX bootrom version 1.12 successfully provides complete suppression of debug messages when 0xA1E30044 0x0000000. However, the redirection of debug messages from the 'standard' COM3 to another com port is not complete. When set to 0xA1E30044 0x0000001, initial debug messages are still on COM3:
Reset Detected
******* BitsyX Initialization*******
CPU ID = A0 PXA255
SDCLK[1] = MemClk
MemClk = 99.53 MHz
Run Mode = 4 * MemClk
Turbo Mode = Run Mode
Mode: RUN
then the remaining debug messages are on COM1. Seems like there is a hardcoded 'COM3' left in the boot code somewhere.
Is there any chance this could be addressed in the next version of BitsyX boot code? |
|
|
|
alintz
12 Posts |
Posted - 21 Apr 2005 : 11:42:11
|
| BitsyX bootrom version 1.14 fixed the problem reported 4/15/05. The debug redirection is complete on COM1. Thanks for the speedy response, Chris. |
|
|
|
janetjek
2 Posts |
Posted - 27 Oct 2006 : 19:53:44
|
| I need all three COM ports for my application; is it possible to redirect the debug output to the USB device port? |
|
|
|
beitman
63 Posts |
Posted - 28 Oct 2006 : 09:37:58
|
No, the debug messages are only output on the serial ports. You can shut off the debug output, by changing:
0xC0000F40 0x00000000 ; Debug output: [00=show] 01=suppress
to
0xC0000F40 0x00000001 ; Debug output: [00=show] 01=suppress
In akidder's post above. |
|
|
|
vboccanfuso
30 Posts |
Posted - 09 Sep 2008 : 17:25:30
|
I was able to suppress debug messages by changing the debug port entry in the ADSLOAD.HWT file as specified in the very first posting. However in my application I'm still not able to get a handle to the debug port using CreateFile() (get device doesn't exist error). It appears that the port is never released by the boot code. Can this be fixed? I need to be able to use all 3 serial ports for my application.
Here is my version information:
Sphere Bootloader Version 1.11 (Built Nov 6 2007, 16:35:22)
Sphere Windows CE Ver. 5.00.19 Sphere_Core
My hardware is a SphereII Dev kit
|
|
|
|
ljoy
22 Posts |
Posted - 09 Sep 2008 : 17:43:16
|
For the Sphere II, the adsload.hwt tag is:
0xA1E30040 0x00000000 ; DebugMsgStop - 0 to enable messages, 1 to inhibit messages |
|
|
|
ctacke
877 Posts |
Posted - 09 Sep 2008 : 17:45:10
|
| The port is actually never "grabbed" by the bootloader (or the kernel). They write directly to the UART and the serial driver has no idea that it's doing it nor any interaction with it. If you look int eh device registry, does the port show up? It should be in HKLM\Drivers\Active under some numbered key (the numbers can vary, so I can't tell you which). |
|
|
|
vboccanfuso
30 Posts |
Posted - 09 Sep 2008 : 18:08:47
|
| The debug port (COM1) doesn't show up in the registry. I only see entries for COM2 and COM3. |
|
|
|
ctacke
877 Posts |
Posted - 09 Sep 2008 : 18:12:16
|
| Does it show up in HKLM\Drivers\BuiltIn? It would likely be under Serial, SER, COM or similar (I don't have a device readily available). Look for entries with the Index value set for each port (1, 2 and 3). |
|
|
|
vboccanfuso
30 Posts |
Posted - 09 Sep 2008 : 18:32:05
|
I think I've discovered the secret - the Debug Port has to be set to 0 in adsload.hwt . When I make the change below, I'm able to get handles to both COM1 and COM2 and all 3 COM ports show up in the registry. This works when DebugMsgStop is 0 or 1.
0xA1E30044 0x00000000 ; Debug Port 1-COM1, 2-COM2, 3-COM3 |
|
|
|
vboccanfuso
30 Posts |
Posted - 09 Sep 2008 : 18:38:26
|
quote:
[i]Originally posted by ctacke[/i]
[br]Does it show up in HKLM\Drivers\BuiltIn? It would likely be under Serial, SER, COM or similar (I don't have a device readily available). Look for entries with the Index value set for each port (1, 2 and 3).
Yes I found COM2 in HKLM\Drivers\BuiltIn\18 and COM3 in HKLM\Drivers\BuiltIn\19, but no COM1 which was set as the debug port. I would have expected it to be in HKLM\Drivers\BuiltIn\17 but that 17 key didn't exist. I looked in all 41 keys just to be sure and COM1 was not in any of them. |
|
|
|
casner
8 Posts |
Posted - 15 Oct 2008 : 15:35:09
|
| I would like to do this on the Turbo IXP board. As far as I know the flags are all parameterized, not addresses. What would I set the debug port to off? Or would I set the debug port to zero as above? |
Edited by - casner on 15 Oct 2008 15:35:37 |
|
|
|
casner
8 Posts |
Posted - 16 Feb 2010 : 10:05:10
|
| I tried setting the debug port to zero in ADSLOAD.HWT, but debug messages still come out. Other suggestions? |
|
|
|
twhite
133 Posts |
Posted - 18 Feb 2010 : 10:52:20
|
casner,
Something to try is to place the following entry into your ADSLOAD.HWT file inside the [TAGS] section:
StopDebugMsg 0x00000001
...and let us know your progress. Thanks!
|
|
|
|
twhite
133 Posts |
Posted - 19 Feb 2010 : 17:26:44
|
From our software engineering group comes the following message:
The TurboIXP platform does not support suppression of debug messages.
Assigning any value for HWT field DebugPort other than 2, will default all debug messages to COM1.
|
|
|
|
casner
8 Posts |
Posted - 19 Feb 2010 : 22:24:43
|
| That would correlate with my experience. |
|
|
| |
Topic |
|
All Forums
Microsoft Windows CE
Suppressing Debug Output
Forum Locked
Send Topic to a Friend
Printer Friendly