MVME162 BSP Issues
Hoover, Victor P CTR NAVAIR, AIR 4.1.3.3
victor.hoover.ctr at navy.mil
Wed Nov 2 14:21:31 UTC 2011
On the web page for this BSP the "Test Reports" section has the following comment:
CVS head -- March 24, 2011: User:Richard Campbell:
Ticker ran successfully; File I/O printed to console but did not accept input.
This still seems to be the case with RTEMS version 4.10.1 (in addition the loopback program in the testsuites/samples directory locks up with a yellow STAT light - the processor halts).
1) Has anyone gotten the console to work properly for this board?
2) Is anyone actively using this BSP?
Note that the ticker and base_sp programs from testsuites/samples both run. Originally they also triggered the yellow SCON light upon completion and do not return to the 162Bug program. This is the result of bugs in the bsp_return_to_monitor_trap() function in the bspclean.c module.
There's an #ifdef for mvme162lx that conditionally sets the 162Bug vector address. By default, 162Bug uses DRAM to run in and the address should always be 0x0 (not 0xFFE00000, this is the SRAM address). The rest of the function is commented out with an #if 0 block that says it does not work on the 162 board. If the vector address is correctly restored the code does work (at least it does on an MVME162-413 board).
Vic Hoover
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5218 bytes
Desc: not available
URL: <http://lists.rtems.org/pipermail/users/attachments/20111102/0081c9c9/attachment.bin>
More information about the users
mailing list