This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
--- Begin Message ---
- From: Krzysztof Błaszkowski <info at sysmikro dot neo dot pl>
- To: <jifl at jifvik dot org>
- Date: Wed, 6 Nov 2002 13:40:46 +0100
- Subject: redboot RAM for EB40 v2.0
Hi,I am beginner to the eCos and I need assistance from expert. I have purchased Atmel's EB40 v2.0 starter kit and I have been stuck with building redboot ram from ecos 2.0 alpha release and ecos configtool 2.11 for longer time. I know that this old theme but I could not find solution from discuss list where the problem is a bit described. My own build release of redboot_RAM.elf starts immediatelly (almost always if it wouldn't hung up) gdb protocol as well as the precompiled one from ecos site. I have also observed that it works unstable. I mean that the same image uploaded with gdb first time sends massage I have logged in file test1.log and the second it sends that what is in test2.log and than hung up. It looks like redboot image used somewhere uninitialized data memory area. I was trying to understand why it starts gdb protocol and one entry point I can see is packages/redboot/current/src/main.c : 324#ifdef CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS
if (res == _GETS_GDB) {
...so I have inserted functions like mon_write_char or diag_printf to trace real program execution (like "###TP1" from test2.log) but it seems that image works another way I can see from source and I have also debugged image with ARM STD v2.5. I am not sure but my image uses probably interrupt from serial as well as it pools serial status register in routines cyg_hal_plf_serial_putc and cyg_hal_plf_serial_getc but ARM STD 2v5 debugger don't emulate AT91x408xx so I have to set/clear status bits at 0xfffd0014 or 0xfffcc014 by my hand. Therefore this is the reason why image works in predicted manner under ARM STD and different in real I guess.But I really dont know how to configure redboot better even I have applied redboot_RAM.ecm from /packages/hal/arm/at91/misc. Another thing is gdb which could not connects to rdi target under cygwin and under linux is able to establish faultless transmission at speed not greater than 9600 bps.I use cygwin 1.3.12-4 and gcc 3.2, binutils 2.13, newlib 1.10, gdb 5.2.1for logging I used auxiliary terminal connected to TX line from EB40.Best regards,Krzysztof BlaszkowskiAttachment: TEST2.LOG
Description: Binary dataAttachment: TEST1.LOG
--- End Message ---
Description: Binary data
-- Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos and search the list archive: http://sources.redhat.com/ml/ecos-discuss
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |