[riot-users] atmega_common: thread_arch.c
hauke.petersen at fu-berlin.de
Thu Jun 22 14:03:12 CEST 2017
have you checked the state of your watchdog? A reproducable reset after
a certain amount of time points in that direction...
On 21.06.2017 14:08, Robert Hartung wrote:
> Hi again,
> the interrupt ist trigged and occurs two times until the reset happens.
> Best Regards,
> On 21.06.2017 14:04, Francisco Javier Acosta Padilla wrote:
>> Hi Robert,
>> The current support of context switching relies in the use of
>> “intentionally triggered” external interrupts, due to the lack of
>> software interrupts on AVR8 MCUs.
>> Please take a look on the implementation of this feature for other
>> boards, such as the arduino-mega2560 or waspmote-pro (board.h file).
>> You’ll need a free EXTI pin on your custom board.
>> I don’t know if this is the cause of your resets, but it seems to me
>> that this could be.
>> Francisco Javier Acosta Padilla
>> Research Engineer at INRIA Saclay
>> INFINE Team
>> On 21 June 2017 at 09:48:33, Robert Hartung (hartung at ibr.cs.tu-bs.de
>> <mailto:hartung at ibr.cs.tu-bs.de>) wrote:
>>> Dear RIOT users,
>>> I am trying to port our platform to RIOT. It is based on an atmega1284p
>>> and I wanted to use the atmega_common platform. However, the
>>> thread_arch.c is missing functions and my device is randomly restarting
>>> (with no reset reason), after about half a second after the first
>>> context switch happened (via an interrupt).
>>> Is anyone using any platforms that rely on the atmega_common or has an
>>> idea what might be happening?
>>> Best Regards,
>>> Robert Hartung, M.Sc.
>>> Technische Universität Braunschweig
>>> Institut für Betriebssysteme und Rechnerverbund
>>> Mühlenpfordtstr. 23, Raum 115
>>> 38106 Braunschweig
>>> Fon: +49 (531) 391 - 3264
>>> Fax: +49 (531) 391 - 5936
>>> E-Mail: hartung at ibr.cs.tu-bs.de
>>> users mailing list
>>> users at riot-os.org
More information about the users