Please help with GDB/PSIM and Redhat Linux

[Joel Sherrill]

Hoang Ngo wrote:
> 
> I used the same psim-gdb script for both environments.
> The on under slackware works but not the one under redhat.
> 
> Here is the content of psim_tree.hngo
> /#address-cells 2
> /openprom/options/oea-memory-size 8388608
> 
> Here is the result of running examples/ncurses/rain.exe
> core_find_mapping() - access to unmaped address, attach a default map to
> handle this - addr=0x38392d31 nr_bytes=0x1 processor=0x401a5008 cia=0xd828
> 
> The address 0xd828 is in the function <set_curterm>.
> 
> Followed your suggestion, i tried to uncommented some of the devices
> in the psim-gdb script but the simulator doesn;t know about the device
> sem or shm.

Ahah!!! I think I have it... Eric .. doesn't the BSP have to
setup the "environ" variable correctly?  The m68k BSPs all
share the same code.  I bet psim is not doing that.  What does
set_curterm do?  Does it do a setenv()?  

> Hoang
> 
> -----Original Message----
> From: Joel Sherrill [mailto:joel.sherrill at OARcorp.com]
> Sent: Sunday, July 30, 2000 7:04 AM
> To: hoanghngo at home.com
> Cc: rtems-users at OARcorp.com
> Subject: Re: Please help with GDB/PSIM and Redhat Linux
> 
> Hoang Ngo wrote:
> >
> > I ran into a perflexing problem. At home i use Slackware7
> > and rtems-4.5.0-beta3a, and rtems-packages-19991215
> > compiled for GDB/PSIM. All the applications under ncurses
> > directory ran fine (except that the terminal is not displaying
> > what it supposed to). At work i use redhat-6.2 with all the same
> > rtems packages but unable to get the ncurses applications to run.
> > The error message indicates that the applications is accessing
> > an unmapped region of memory (core_find_mapping() - access
> > to unmaped address, attach a default map to handle this -
> > addr=0x38392d31 nr_bytes=0x1 processor=0x401a5008 cia=0xf1dc).
> >
> > If you have any suggestions as what to look for please drop me a line.
> 
> I think this is a matter of either one of two things:
> 
>  + You are not starting the simulator with all the device options.
>    See the script psim/psim-gdb included with the BSP in the tools
>    subdirectory.
>  + I am not sure what instruction/inside what function the cia
>    is pointing to but it might be an issue that the shared memory
>    or semaphore is not being initialized correctly.
> 
> More than likely, it is the first since the shared mem/semapahore
> is mapped to different processor address range. See what the
> psim script does to initialize the simulator.
> 
> > TIA,
> > Hoang
> 
> --
> Joel Sherrill, Ph.D.             Director of Research & Development
> joel at OARcorp.com                 On-Line Applications Research
> Ask me about RTEMS: a free RTOS  Huntsville AL 35805
>    Support Available             (256) 722-9985

-- 
Joel Sherrill, Ph.D.             Director of Research & Development
joel at OARcorp.com                 On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
   Support Available             (256) 722-9985