Project Home
Project Home		 Documents
Documents		 Wiki
Wiki		 Discussion Forums
Discussions		 Project Information
Project Info
QNX Operating System/Discussion/OSTech/Initial Baudrate for Console/List of Posts
Forum Topic - Initial Baudrate for Console: (6 Items)
   
Update
Marc Roessler
12/22/2008 8:10 AM
post19128
Initial Baudrate for Console   
See subject..

We are trying to bootstrap a system (mpc8313) using the BDI2000 debugger.
I'm loading the QNX image to address 0x200000, then jumping there with "go 0x200000" (while this isn't how it should be 
done officially, it works fine when doing this from UBoot).

Now the problem is, besides some little burps of garbage on the serial console not much happens. I suppose the Baudrate 
is set wrong.
What Baud Rate does QNX use when there is no ROM monitor or Bootloader
(such as UBoot) to set it?

I tried modifying the const struct debug_device debug_devices[] in the
startup code to read "0xe0004500^0.115200.333333333.16" for the first serial port, but it didn't really change a thing..
.

Any help is appreciated.

Thanks & Merry Christmas,
 Marc
Elena Laskavaia
12/22/2008 9:17 AM
post19131
Re: Initial Baudrate for Console   
I don't know the answer but we have some docs about JTAG debugging:

http://www.qnx.com/developers/docs/6.4.0/ide_en/user_guide/debug.html#JTAGAbtron
and
http://www.qnx.com/developers/articles/article_921_1.html


Marc Roessler wrote:
> See subject..
> 
> We are trying to bootstrap a system (mpc8313) using the BDI2000 debugger.
> I'm loading the QNX image to address 0x200000, then jumping there with "go 0x200000" (while this isn't how it should 
be done officially, it works fine when doing this from UBoot).
> 
> Now the problem is, besides some little burps of garbage on the serial console not much happens. I suppose the 
Baudrate is set wrong.
> What Baud Rate does QNX use when there is no ROM monitor or Bootloader
> (such as UBoot) to set it?
> 
> I tried modifying the const struct debug_device debug_devices[] in the
> startup code to read "0xe0004500^0.115200.333333333.16" for the first serial port, but it didn't really change a thing
...
> 
> Any help is appreciated.
> 
> Thanks & Merry Christmas,
>  Marc
> 
> _______________________________________________
> OSTech
> http://community.qnx.com/sf/go/post19128
>
Marc Roessler
12/23/2008 4:07 AM
post19167
Re: Initial Baudrate for Console   
Hi,

I found that by modifying the mentioned struct I get _one_ message,
"Starting on-board ethernet with TCP/IP stack.."
but that's it... it seems this speed setting only affects parts of the system,
the Neutrino Kernel itself seems to log to someplace else regardless of what
baud rate I set...?

Greetings,
 Marc
Marc Roessler
12/23/2008 8:30 AM
post19173
Re: Initial Baudrate for Console   
some new details...

kernel messages are not displayed during boot,
after starting devc-ser8250 starting display_msg seems to work from the startup bsh script,
starting drivers (tcpip, nand, pci, spi, ...) seems to freeze the system..
when i start the system with all drivers commented out (except devc-ser8250) I get a Shell prompt ("#"), but giving any 
commands or pressing enter seems to lock up the system again/no reaction any more..

any ideas? maybe some memory areas not mapped right?
Marc Roessler
01/07/2009 10:46 AM
post19541
Re: Initial Baudrate for Console   
bump...
still stuck at that problem..
Can't really start and driver as it seems when booting.. any idea?
Serial Driver seems to work, but nothing else.. ETFS, PCI, NET..they all just get stuck..
Dell Drummond(deleted)
01/16/2009 4:35 PM
post20269
Re: Initial Baudrate for Console   
The debug callouts and devc-ser8250 are more or less independent, other than both drive the same hardware. You should be
 able to get the debug callouts working with the settings used for the serial driver. Most startups permit the debug 
callouts to be setup using the -D and -K options, which should shorten your turn around time. 

As for the other problems - offen I think it comes down to having the memory and/or interrupts incorrectly configured. 
The initial state of the system is also something to examine. If the system is booting from u-boot you might want to try
 comparing the initial system state with and without uboot.  

> bump...
> still stuck at that problem..
> Can't really start and driver as it seems when booting.. any idea?
> Serial Driver seems to work, but nothing else.. ETFS, PCI, NET..they all just 
> get stuck..

Return


  A subsidiary of BlackBerry             All content ©2004-2013, QNX Software Systems