From mboxrd@z Thu Jan 1 00:00:00 1970 From: Grant Edwards To: Fernando Nasser Cc: gdb@sourceware.cygnus.com Subject: Re: RDI target broken in 000215 snapshot Date: Thu, 24 Feb 2000 10:47:00 -0000 Message-id: <20000224124726.A663@visi.com> References: <20000221104541.A28578@visi.com> <38B2AD14.7B0B4A4E@redhat.com> X-SW-Source: 2000-02/msg00006.html On Tue, Feb 22, 2000 at 03:36:52PM +0000, Fernando Nasser wrote: > > The RDI target support seems to be broken in the 000215 > > snapshot. > > Can you be more specific? It is working right with the AEB board and > with another one I have here. Both use serial ports. (I'm now using 000222) When I download code with the "load" command, the byte order of the data gets flipped -- it ends up in little-endian order (it's big-endian in the file, and I need it to stay that way when it is downloaded). Downloading with a patched 4.18 doesn't have this problem. -- Grant Edwards grante@visi.com >From fnasser@cygnus.com Thu Feb 24 11:16:00 2000 From: Fernando Nasser To: Grant Edwards Cc: Fernando Nasser , gdb@sourceware.cygnus.com Subject: Re: RDI target broken in 000215 snapshot Date: Thu, 24 Feb 2000 11:16:00 -0000 Message-id: <38B58292.3B11D622@cygnus.com> References: <20000221104541.A28578@visi.com> <38B2AD14.7B0B4A4E@redhat.com> <20000224124726.A663@visi.com> X-SW-Source: 2000-02/msg00007.html Content-length: 1221 Grant Edwards wrote: > > On Tue, Feb 22, 2000 at 03:36:52PM +0000, Fernando Nasser wrote: > > > > The RDI target support seems to be broken in the 000215 > > > snapshot. > > > > Can you be more specific? It is working right with the AEB board and > > with another one I have here. Both use serial ports. > > (I'm now using 000222) > > When I download code with the "load" command, the byte order of > the data gets flipped -- it ends up in little-endian order > (it's big-endian in the file, and I need it to stay that way > when it is downloaded). Downloading with a patched 4.18 doesn't > have this problem. > Grant, A few questions (while I rebuild from the 22 sources): What compiler, in what host and with which parameters did you generate your executable file? Is it the same one you can successifuly load with the patched 4.18? In both cases you are loading the program into the AEB board, right? I forgot, which host are you running gdb in? Linux, Solaris, Cygwin? Thanks, Fernando -- Fernando Nasser Red Hat - Toronto E-Mail: fnasser@cygnus.com 2323 Yonge Street, Suite #300 Tel: 416-482-2661 ext. 311 Toronto, Ontario M4P 2C9 Fax: 416-482-6299 >From grante@visi.com Thu Feb 24 11:33:00 2000 From: Grant Edwards To: Fernando Nasser Cc: Fernando Nasser , gdb@sourceware.cygnus.com Subject: Re: RDI target broken in 000215 snapshot Date: Thu, 24 Feb 2000 11:33:00 -0000 Message-id: <20000224133238.A723@visi.com> References: <20000221104541.A28578@visi.com> <38B2AD14.7B0B4A4E@redhat.com> <20000224124726.A663@visi.com> <38B58292.3B11D622@cygnus.com> X-SW-Source: 2000-02/msg00008.html Content-length: 1495 On Thu, Feb 24, 2000 at 02:12:18PM -0500, Fernando Nasser wrote: > > When I download code with the "load" command, the byte order of > > the data gets flipped -- it ends up in little-endian order > > (it's big-endian in the file, and I need it to stay that way > > when it is downloaded). Downloading with a patched 4.18 doesn't > > have this problem. > > > Grant, > > What compiler, in what host and with which parameters did you > generate your executable file? $ uname -a Linux grante.comtrol.com 2.2.12-20 #1 Mon Sep 27 10:25:54 EDT 1999 i586 unknown $ arm-elf-gcc --version 2.95.2 $ arm-elf-as --version GNU assembler 991018 $ make arm-elf-as --gstabs -EB -m arm7tdmi -amhlsnd=memconfigR10_S0_D100.lst -o memconfigR10_S0_D100.o memconfigR10_S0_D100.s arm-elf-gcc -g -mcpu=arm7tdmi -fverbose-asm -mbig-endian -Wl,-Map,memconfigR10_S0_D100.map -nostartfiles -o memconfigR10_S0_D100 memconfigR10_S0_D100.o -T./memconfig.ld -nostdlib libgcc.a > Is it the same one you can successifuly load with the patched 4.18? Yes. > In both cases you are loading the program into the AEB board, right? No. I'm loading to custom hardware (big-endian), but I verified that the same thing happens with the Samsung SNDS eval board (also big-endian hardware). I've used the EPI Jeeni (via ethernet) and the ARM Embedded ICE (via serial port) and had the same results. > I forgot, which host are you running gdb in? Linux, Solaris, Cygwin? Linux (same as above). -- Grant Edwards grante@visi.com >From grante@visi.com Thu Feb 24 11:46:00 2000 From: Grant Edwards To: Fernando Nasser Cc: Fernando Nasser , gdb@sourceware.cygnus.com Subject: Re: RDI target broken in 000215 snapshot Date: Thu, 24 Feb 2000 11:46:00 -0000 Message-id: <20000224134607.A6354@visi.com> References: <20000221104541.A28578@visi.com> <38B2AD14.7B0B4A4E@redhat.com> <20000224124726.A663@visi.com> <38B58292.3B11D622@cygnus.com> X-SW-Source: 2000-02/msg00009.html Content-length: 984 Another interesting bit of info. The new snapshot is apparently not detecting the endianness of the target (both the sessions below were with a Samsung SNDS evel board (big-endian): $ arm-elf-gdb GNU gdb 4.18 [...] This GDB was configured as "--host=i586-pc-linux-gnu --target=arm-elf". (gdb) target rdi /dev/ttyS1 EmbeddedICE Manager (ADP, ARM7TDI) 2.07 (Advanced RISC Machines SDT 2.11a) Rebuilt on Apr 1 1998 at 00:43:57 Serial Rate: 9600 Connected to ARM RDI target. (gdb) show endian The target endianness is set automatically (currently big endian) $ ~/gdb-000222/gdb/gdb GNU gdb 000222 [...] This GDB was configured as "--host=i586-pc-linux-gnu --target=arm-elf". (gdb) target rdi /dev/ttyS1 EmbeddedICE Manager (ADP, ARM7TDI) 2.07 (Advanced RISC Machines SDT 2.11a) Rebuilt on Apr 1 1998 at 00:43:57 Serial Rate: 9600 Connected to ARM RDI target. (gdb) show endian The target endianness is set automatically (currently little endian) -- Grant