From mboxrd@z Thu Jan 1 00:00:00 1970 From: Cristiano Ligieri Pereira To: Gary Thomas Cc: ecos-discuss@sourceware.cygnus.com Subject: RE: [ECOS] Port to XScale board Date: Mon, 20 Aug 2001 14:36:00 -0000 Message-id: References: X-SW-Source: 2001-08/msg00672.html Hi, I kind of solved my RAM redboot problem (however temporarily since I only removed the cause of the problem from the code instead of fixing it). I commented out (till I figure out why) the three function calls that were crashing... :-| The first is the call to function __clear_breakpoints() whithin the function __handle_exception (void), which is located in the file generic-stub.c. Actually this one I haven't commented out but only defined CYGNUM_HAL_BREAKPOINT_LIST_SIZE to 0, which in turn makes the function do not be called. The second and third are the function calls __data_cache(CACHE_FLUSH) and __instruction_cache(CACHE_FLUSH) respectively, both within the same function and file, that I literally commented out. Now I can download a file using GDB/Redboot (running from RAM) but I can't actually execute it. I'm downloading the file at the address 0x60000 (at RAM) since Redboot is located at 0x20000 (right?). The entry point should be reset_vector (right?), which had to be located in the address 0x64000, but is actually being mapped to 0x60040. Is this a problem? Anyways my application is loaded and GDB jumps to 0x60040 Loading section .rom_vectors, size 0x40 lma 0x60000 Loading section .text, size 0xf924 lma 0x60040 Loading section .rodata, size 0x4f0 lma 0x6f964 Loading section .data, size 0x4d4 lma 0x6fe54 Start address 0x60040 , load size 66344 Transfer rate: 40827 bits/sec, 302 bytes/write. and nothing else happens. I have the LEDs being lightned up (in vectors.S) but it's not working, what makes me assume that the application is not being executed. Am I missing something here? Thanks, Cristiano. ------------------------------------------------------------ Cristiano Ligieri Pereira - http://www.ics.uci.edu/~cpereira > First of all, you can load programs using RedBoot's "load" command as > well. > > Try turning on GDB's remote debug facility which will display something > about what's going on on the communications line. Note: it will be running > at the same speed that RedBoot was using, most likely 38400 unless you've > set it up to run otherwise. >