Hi John,

>Is there a working document or set of notes detailing ongoing/needed
work for STM32H7 support?

Not really - a diff to the F7 file usually will show the holes but there is
also the datasheet diff view.

We used SDMMC2 in all H7 designs and that choice gave us the ability to
bring out the full ARM trace pins, so the MDMA was not high on our list.

I will be upstreaming DMA support for the SPI driver once we complete
testing (Friday). I found a nasty along the way and will document it in the
PR.

My next stop was going to be the stm32H7 CANFD driver, so if you want to
start on that it would be a great contribution and we can work on it
together.


Regards,

David

-----Original Message-----
From: John Rippetoe [mailto:jrippe...@roboticresearch.com]
Sent: Thursday, April 02, 2020 12:56 PM
To: dev@nuttx.apache.org
Subject: STM32H7 support

Hi all,

Is there a working document or set of notes detailing ongoing/needed
work for STM32H7 support? I've looked through the code in
arc/arm/*/stm32h7, release notes, board README, and commits/issues/PRs
on github to piece together some of what has been worked on.  It appears
that a lot of the difficult groundwork has already been laid. So that I
don't duplicate any work, is anyone working on the following?


- MDMA support.  This is especially important for SDMMC1, which doesn't
have access to SRAM1234 needed by the IDMA (see PR684
<https://github.com/apache/incubator-nuttx/pull/684>). This seems like a
big job for a newbie like me, but there is no better way to learn than
to just dive in right?

- Support for silicon revision-specific differences. There is some code
for this in the chip ADC driver (ADC_DEVICE_VERSION_V). I have a few
ideas for this.


What other things need attention?

Thanks as always. I am looking forward to working with you all!

- John Rippetoe


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.

Reply via email to