VFP support for lpc32xx

Fri Aug 19 00:06:29 UTC 2016

After some finagling, I was successful using the RTEMS tester, GDB, and an ARM Jlink JTAG cable to run the sptests under the testsuite.  I passed all but 8.  3 of the tests actually passed but have some issues with the test cases or output parser.  The 5 remaining failures should have nothing to do with the VFP additions so I’m pretty confident it is fine.  I’ll post the patches for review.  They are pretty minor.

Kevin Kirspel
Electrical Engineer - Sr. Staff
Opti Medical
235 Hembree Park Drive
Roswell GA 30076
Tel: (770)-510-4444 ext. 81642
Direct: (770)-688-1642
Fax: (770)-510-4445

From: Joel Sherrill [mailto:joel.sherrill at gmail.com]
Sent: Wednesday, August 17, 2016 3:06 PM
To: Kirspel, Kevin <Kevin-Kirspel at idexx.com>; Chris Johns <chrisj at rtems.org>
Cc: devel at rtems.org
Subject: Re: VFP support for lpc32xx

On Wed, Aug 17, 2016 at 2:04 PM, Kirspel, Kevin <Kevin-Kirspel at idexx.com<mailto:Kevin-Kirspel at idexx.com>> wrote:
I have a patch for the RTEMS source builder as well as RTEMS itself to support the VFP on the lpc32xx.  I don’t have hardware the matches the lpc32xx BSP but I do have some custom hardware that I can run the test suite on.  Can you point me to some documentation that tells you how to automate the running of the test suite?

If you have JTAG on your HW, the rtems-tester in rtems-tools has setup to run
tests on Zynq automated using gdb and JTAG.

Chris Johns should speak up.

Kevin Kirspel
Electrical Engineer - Sr. Staff
Opti Medical
235 Hembree Park Drive
Roswell GA 30076
Tel: (770)-510-4444 ext. 81642<tel:%28770%29-510-4444%20ext.%2081642>
Direct: (770)-688-1642<tel:%28770%29-688-1642>
Fax: (770)-510-4445<tel:%28770%29-510-4445>

_______________________________________________
devel mailing list
devel at rtems.org<mailto:devel at rtems.org>
http://lists.rtems.org/mailman/listinfo/devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20160819/350d01c9/attachment-0002.html>