This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: console Implementation
- From: Jürgen Lambrecht <Jurgen dot Lambrecht at tiscali dot be>
- To: anupm at aftek dot com
- Cc: ecos-discuss at sourceware dot org
- Date: Fri, 30 Mar 2007 08:27:37 +0200
- Subject: Re: [ECOS] console Implementation
- References: <1174891853.4174.28.camel@anup.aftek.com>
If I remember will, in the Virtual Vector Table, there is a function pointer for diag_printf. Change that function pointer to your own USB printf function.
RedBoot does it as ROM monitor: RedBoot searches a communication port, and the RAM application loaded by RedBoot uses the same communication port.
Read Massa's book about it (on http://www.ecosforge.net/trac/wiki/EcosResources you can find it)
I don't know if you use a ROM application (without RedBoot) how to do it.
Kind regards,
Juergen Lambrecht
Anup Manakeshwar wrote:
Hi All
I am using eCos 2.0 in one of my project.
I want to divert all the debug messages to some other interface other
than standard serial console.
I have decided to use USB interface to get all the log messages.
So i already wrote driver for USB.
The Philips ISP1161x is the chip used for this.
The USB device is of serial class.
It works fine...
Now i want to divert all debug messages to this USB serial port.
I am not getting how i shud go abt it.
I am not sure how serial console is implemented...
can you provide some pointers regarding this.....this will be of great
help to me ...
Best Regards
Anup M
--
Jürgen Lambrecht
Diksmuidse Heerweg 338
8200 Sint-Andries
Tel: +32 (0)50 842901
GSM: +32 (0)476 313389
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss