Re: [ECOS] How to make a code from RAM startup to ROM startup?

[Jesper Skov <jskov at cambridge dot redhat dot com>]

>>>>> "Ling" == Ling Su <lingsu@palmmicro.com> writes:

Ling> So, sounds to me it is no way to handle serial debugging with
Ling> the GDB stubs, since it is built on HAL_IO. The current

Correct, you cannot assume debugging to work on the same line you use
for IO with the serial device driver.

Ling> situation for me is, I realized that the HAL_IO and serial IO
Ling> might have conflict problems, so I removed all the diag_printf()
Ling> call. I just use GDB to download the code onto the board, then
Ling> issue a "continue" command to let it run, in this case, I am not
Ling> sure if the HAL_IO layer still alive to access serial port?

It should not be - the HAL_IO in ROM is used for the download. When
you issue the continue command, the RAM application will take control
of the board - and if it does not contain any diag_printf calls, it
should have no HAL_IO code either.

Ling> I remember there is some serial test cases, which use obviously
Ling> serial IO running under GDB, they are all working very
Ling> well. From Jesper's explanation, I guess they should fail at
Ling> least sometime, right?

No - they have been written carefully to allow both the IO serial
driver and GDB communication to coexist on the same line.   They use a
strict protocol that allow a clean separation of the two data streams
- you cannot guarantee the same with an application that uses the
serial while you try to debug it on the same line.

Jesper