From mboxrd@z Thu Jan 1 00:00:00 1970 From: Grant Edwards To: Ilko Iliev Cc: ecos-discuss@sources.redhat.com Subject: Re: [ECOS] ARM7 debugging Date: Tue, 16 Jan 2001 07:20:00 -0000 Message-id: <20010116092435.A18332@visi.com> References: <4.3.2.7.2.20010115181356.00b8d078@mbox> <20010115113434.B7985@visi.com> <4.3.2.7.2.20010116094325.00b61ec8@mbox> X-SW-Source: 2001-01/msg00260.html On Tue, Jan 16, 2001 at 04:02:28PM +0100, Ilko Iliev wrote: > > > > - when I use no windows interface gdb connected to target: gdb> > > > target rdi e=192.168.1.100 A user program can be downloaded and > > > executed. > > > >You should be able to type the same commands into the gdb > >window when using the windowing interface. Does that work? > > Yes, it work. But if I don't use gdb.ini file how can I init > the chip select for RAM? It must be before "load". On my board I solve that problem by loading a small (about 40 words) memory config program into the 8K internal SRAM in the processor and running it. That configures the chip select for the external RAM, which I can then use for my real application. When I was using the menu entry to load a file, I had it run that memory config program as part of the "connect script" that I defined in .gdbinit and configured in the dialog box for the target. > The example twothreads don't work with JEENI - I receive no > timer interrupt. The same elf file work fine with Wiggler. Do > you have any idea? That's odd. I don't know of any reason why the method used to load the program should change things like that. -- Grant Edwards grante@visi.com