ARM SMP Clock driver errors

[Sebastian Huber]

On 22/06/16 09:57, Darshit Shah wrote:
> On 06/22, Sebastian Huber wrote:
>> On 21/06/16 07:29, Sebastian Huber wrote:
>>>
>>>
>>> On 20/06/16 15:40, Darshit Shah wrote:
>>>> Hi,
>>>>
>>>> Last week the clock driver for SMP ARM BSPs was fixed which allowed 
>>>> me to start executing the SMP tests for my GSoC project. However, 
>>>> today I seem to be stuck with a clock driver issue again.
>>>>
>>>> When I try to execute SMP tests, the tests exit with no output and 
>>>> a exit code of 0. On trying to run them in QEMU and breaking on 
>>>> _Terminate(), I found out that the tests exit because of an 
>>>> `RTEMS_FATAL_SOURCE_BSP` error which propagates from the 
>>>> `a9mpcore_clock_secondary_initialization` method. The complete 
>>>> backtrace is:
>>>
>>> In this case something is wrong with your BSP build. In bspopts.h 
>>> you must find this:
>>>
>>> find -name bspopts.h | xargs grep CLOCK_DRIVER_USE_ONLY_BOOT_PROCESSOR
>>> ./arm-rtems4.12/c/realview_pbx_a9_qemu_smp/lib/libbsp/arm/realview-pbx-a9/include/bspopts.h:#define 
>>> CLOCK_DRIVER_USE_ONLY_BOOT_PROCESSOR 1
>>> ./arm-rtems4.12/realview_pbx_a9_qemu_smp/lib/include/bspopts.h:#define 
>>> CLOCK_DRIVER_USE_ONLY_BOOT_PROCESSOR 1 
>>
>> I checked commit 3d9fd2ce55575e603fa9e781cc66f553e917fd3b and 
>> everything (except some timing dependent tests) works fine for the 
>> realview_pbx_a9_qemu and realview_pbx_a9_qemu_smp BSPs.
>
> I just nuked my existing build directory and everything worked again.  
> Not sure why the build went bad. I guess I'll need to constantly keep 
> deleting the build directory everytime I see any kind of failure. 

Yes, in case something is not working after an update, then please do a 
bootstrap of the RTEMS sources, delete the build tree and configure again.

-- 
Sebastian Huber, embedded brains GmbH

Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone   : +49 89 189 47 41-16
Fax     : +49 89 189 47 41-09
E-Mail  : sebastian.huber at embedded-brains.de
PGP     : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.