On Feb 14, 2014, at 07:06 , Peter Dufault <dufa...@hda.com> wrote: >> which issues do you have? > > I wanted to get more details before posting. The first thing I noticed is > that either rtems_clock_set() or rtems_clock_get() isn't working properly > (and isn't returning an error), so e.g. Task_1_through_3() in sp01 exits > immediately because it sees that more than 35 seconds has gone by and exits. > The fact that exit() now calls bsp_reset() had me confused for a while, I > thought things were really in bad shape until I realized that (and I checked, > that detail is in the release notes). I recompiled without optimization last > night so that this AM I can figure out more. > >
Oh-oh, this isn't what I wanted to see after rebuilding without optimization. With optimization on by the time the program printed out "**" TA1 would run, see 35 seconds had gone by, exit and call bsp_reset(). *** TEST 1 *** TA1 - rtems_clock_get_tod - 09:00:00 12/31/1988 TA2 - rtems_clock_get_tod - T0A93: 0 - rtems_clock_get_tod - 00:90:00 012:/0310/ 198812 /31/1988 TA1 - rtems_clock_get_tod - 09:00:05 12/31/1988 TA1 - rtems_clock_get_tod - 09:00:10 12/31/1988 TA2 - rtems_clock_get_tod - 09:00:10 12/31/1988 TA1 - rtems_clock_get_tod - 09:00:15 12/31/1988 TA3 - rtems_clock_get_tod - 09:00:15 12/31/1988 TA1 - rtems_clock_get_tod - 09:00:20 12/31/1988 TA2 - rtems_clock_get_tod - 09:00:20 12/31/1988 TA1 - rtems_clock_get_tod - 09:00:25 12/31/1988 TA1 - rtems_clock_get_tod - 09:00:30 12/31/1988 TA3 - rtems_clock_get_tod - 09:00:30 12/31/1988 TA2 - rtems_clock_get_tod - 09:00:30 12/31/1988 *** END OF TEST 1 *** Peter ----------------- Peter Dufault HD Associates, Inc. Software and System Engineering _______________________________________________ rtems-devel mailing list rtems-devel@rtems.org http://www.rtems.org/mailman/listinfo/rtems-devel