On 05.10.2012 03:43, Ken Yee wrote:
> Ilija Kocho wrote:
>> This may be example you are looking for:
>> http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001623
> Got decently far with this angle of changes.
> We created a new startup type, and fiddled with most of the options for
> RAM/ROM in the .cdl file. But from doing this, it's glaringly obvious that
> eCos does *NOT* support this setup; a ROM app run from Redboot, at least on
> the AT91, has to do a hybrid of the ROM and RAM startup types. The Redboot
> documentation should clearly state that only apps built in the RAM startup
> type are supported IMHO.
True, you won't find for ROM startup in standard RedBoot. FLASH startup
is [my] experiment for testing the concept. It seems to work, but it's
still experimental. Your tests are valuable, thanks.
>
> Anyways, simple test apps seem to run, but one this we hit was that anything
> that does diag_printf gets stuck in the IF_IN_PUTC call...it just deep spaces
> (runs until it hits that) there in the debugger. Single stepping into
> assembly doesn't even work if you put a breakpoint before that so we can't
> see where that goes (whether it's to a bad driver, etc.). The simplest app
> like this:
It's true for break points. The target code being in Flash, rather than
RAM, needs hardware break points that are not supported by RedBoor/eCos
GDB stubs at present.
> void cyg_user_start(void)
> {
> diag_printf("\r\nHello world!\r\n");
> }
> does the hang when compiled as an APPROM (that's what we called it instead of
> Flash as yours is called...maybe RBROMAPP for RedBootROMApp might be a better
> acronym?).
>
> Did you hit this problem in your setup at all? i.e., did you try diag_printf
> on your kinetis board?
Yes I have.
Try the real (instead of diagnostic) serial driver.
Ilija
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
