[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Paparazzi-devel] CAN on Lisa

From: Tilman Baumann
Subject: Re: [Paparazzi-devel] CAN on Lisa
Date: Tue, 14 Aug 2012 17:09:56 +0100
User-agent: Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20120713 Thunderbird/14.0

On 14/08/12 16:28, Tilman Baumann wrote:
Should we keep the API defined in ./sw/airborne/arch/stm32/mcu_periph/can_arch.c?

Considering that is is not actually used anywhere I would not feel too bad to scrap it.
The thing is that the libopencm3 API is quite different. And I would like to take advantage of the hardware filters in the chip more.

can_hw_init() and can_hw_transmit() would practically be the same. But I would like to change the rx_callback method so that every module could register it's own callback.
Which would make the code quite stm32 specific, I admit. More generic abstractions could be possible though.

I may have misread the specs there. I can have many filters. But not a receive FIFO each.
Well, that makes it kind of easy. Forget what I said. :)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]