Thanks for letting me know! I was actually following the discussion on
whether to include the G4 in the stm32 folder, so I knew it was being
worked on.
I took a quick look at the G4 reference manual and it shows that they
share identical FDCAN core releases, so the basic stuff should all be
the same. The main difference appears to be in the number of CAN cores
(3 in the G4 vs 2 in the H7) and the amount of message RAM (1Kb per core
in the G4 vs 10Kb shared between the 2 cores in the H7). It also appears
that there is no Time Triggered CAN functionality in the G4. So it seems
like it should be pretty easy for us to collaborate.
- John
On 4/23/20 4:29 PM, Nathan Hartman wrote:
On Thu, Apr 23, 2020 at 3:54 PM John Rippetoe
<jrippe...@roboticresearch.com> wrote:
I have been working on adding support for the FDCAN peripheral in the
STM32H7 and have a basic driver working. It's a bit of a hack in some
I haven't yet read your whole email. I will revisit it soon. But in
the meantime I wanted to mention that I'm working on architectural
support in NuttX for the STM32G474xxxx family, which also has FDCAN.
In fact, yesterday, I was working on the pinmap for several
peripherals, including the FDCAN. My work is in my fork on GitHub, in
https://github.com/hartmannathan/incubator-nuttx in the branch
stm32g474. This being a recent addition to STM32's family line,
perhaps the FDCAN peripherals share some common lineage and maybe we
could split some of the work to support it. I'm not ready yet, because
first need to get minimal support up and running, to initialize the
sysclk and boot up NuttX on my board, but I thought it be helpful to
mention.
Cheers,
Nathan
CONFIDENTIALITY NOTICE: This communication may contain private, confidential
and privileged material for the sole use of the intended recipient. If you are
not the intended recipient, please delete this e-mail and any attachments
permanently.
