rtems samples crash

[Joel Sherrill]

Tim Cussins wrote:
> Hi Lukasz,
>
> Instead of invoking gdb directly, Joel has written some wrapper scripts
> that setup the psim simulator correctly. Look for 'psim', 'psim-gdb',
> and 'runtests' - I think they get installed to the tests directory.
>   
But he is running the virtex BSP which won't run on the
ppc simulator in gdb.  You have to be running psim executables
and invoking gdb requires a lot of arguments for psim.  You
need to use the scripts Tim mentioned PLUS the right BSP.

--joel
> HTH
>
> Tim
>
> On Thu, 30 Apr 2009 11:27 +0200, "lukasz mosdorf"
> <lukasz.mosdorf at gmail.com> wrote:
>   
>> Hi all,
>>
>> I have compiled RTEMS 4.9 for powerpc bsp virtex. Unfortunatelly Im not 
>> able to run example programs. I do the following thing:
>>
>> [root at mort RTEMS_CVS]# powerpc-rtems4.9-gdb `find . -name ticker.exe`
>> GNU gdb 6.8
>> Copyright (C) 2008 Free Software Foundation, Inc.
>> License GPLv3+: GNU GPL version 3 or later 
>> <http://gnu.org/licenses/gpl.html>
>> This is free software: you are free to change and redistribute it.
>> There is NO WARRANTY, to the extent permitted by law.  Type "show
>> copying"
>> and "show warranty" for details.
>> This GDB was configured as "--host=i686-pc-linux-gnu 
>> --target=powerpc-rtems4.9"...
>> (gdb) tar sim
>> Connected to the simulator.
>> (gdb) load
>> (gdb) r
>> Starting program: 
>> /home/mort/RTEMS_CVS/b-mpc55xxevb/powerpc-rtems4.9/c/virtex/testsuites/samples/ticker/ticker.exe 
>>
>> core_find_mapping() - access to unmaped address, attach a default map to 
>> handle this - addr=0x40600008 nr_bytes=0x4 processor=0xb7c92008
>> cia=0x13414
>>
>>
>> i did a stack trace and it looks like printing to a console crashes:
>>
>>
>> (gdb) bt
>> #0  outputChar (ch=85 'U')
>>     at 
>> ../../../../../../../../rtems/c/src/lib/libbsp/powerpc/virtex/console/consolelite.c:67
>> #1  0x0001561c in vprintk (
>>     fmt=0x2f380 "Unknown PVR value of 0x%x. Please add it to 
>> <libcpu/powerpc/shared/include/cpuIdent.c>\n", ap=0x3ff74)
>>     at 
>> ../../../../../../rtems/c/src/../../cpukit/libcsupport/src/printk.c:159
>> #2  0x0001593c in printk (fmt=<value optimized out>)
>>     at 
>> ../../../../../../rtems/c/src/../../cpukit/libcsupport/src/printk.c:174
>> #3  0x00013cf0 in get_ppc_cpu_type ()
>>     at 
>> ../../../../../../../rtems/c/src/lib/libcpu/powerpc/shared/include/cpuIdent.c:111
>> #4  0x00013108 in bsp_start ()
>>     at 
>> ../../../../../../../../rtems/c/src/lib/libbsp/powerpc/virtex/startup/bspstart.c:163
>> #5  0x00013000 in boot_card (argc=<value optimized out>,
>>     argv=<value optimized out>, envp=<value optimized out>)
>>     at 
>> ../../../../../../../../rtems/c/src/lib/libbsp/powerpc/virtex/../../shared/bootcard.c:197
>> #6  0x00010024 in .startup ()
>>     at 
>> ../../../../../../../../rtems/c/src/lib/libbsp/powerpc/virtex/dlentry/dlentry.S:106
>> Backtrace stopped: previous frame inner to this frame (corrupt stack?)
>>
>>
>> Same thing happens with all examples, not only this one.
>> Any ideas ?
>>
>> regards
>> Lukasz Mosdorf
>> _______________________________________________
>> rtems-users mailing list
>> rtems-users at rtems.org
>> http://www.rtems.org/mailman/listinfo/rtems-users
>>     
> _______________________________________________
> rtems-users mailing list
> rtems-users at rtems.org
> http://www.rtems.org/mailman/listinfo/rtems-users
>