2017-07-30 20:40 GMT+02:00 Joel Sherrill <j...@rtems.org>: > > > On Jul 30, 2017 12:19 PM, "Denis Obrezkov" <denisobrez...@gmail.com> > wrote: > > 2017-07-30 3:10 GMT+02:00 Joel Sherrill <j...@rtems.org>: > >> >> >> On Jul 29, 2017 8:02 PM, "Denis Obrezkov" <denisobrez...@gmail.com> >> wrote: >> >> >> >> 2017-07-30 2:34 GMT+02:00 Joel Sherrill <j...@rtems.org>: >> >>> >>> Sorry to top post but this thread is very deep to answer on a phone. >>> >>> Try looking at the same code on the erc32 bsp and see how it is done. >>> >>> Also you could disable the atexit() call and see how.much further you >>> get. >>> >>> >>> Ok, I will look at erc32 bsp. >> I have removed atexit call, now I can proceed further, till the while(1) >> loop in the low ticker test. >> But the Dummy Clock doesn't tick. >> So, I again get the output: >> *** LOW MEMORY CLOCK TICK TEST *** >> TA1 - rtems_clock_get_tod - 09:00:00 12/31/1988 >> TA2 - rtems_clock_get_tod - 09:00:00 12/31/1988 >> TA3 - rtems_clock_get_tod - 09:00:00 12/31/1988 >> >> >> Low ticker has its Init task become the idle task. Your clock driver >> simulator thread is likely never running. >> >> Try turning that option off in the test >> >> >> >> -- >> Regards, Denis Obrezkov >> >> >> > I tried it, but I had an error > ../../../../../hifive1/lib/include/rtems/confdefs.h:3586:2: error: #error > "CONFIGURATION ERROR: No initialization tasks or threads configured!!" > #error "CONFIGURATION ERROR: No initialization tasks or threads > configured!!" > > > You have to configure an Init task. > > > > > -- > Regards, Denis Obrezkov > > > Yes, I understand that, but I can't find proper configuration options.
-- Regards, Denis Obrezkov
_______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
