Re: Adding support for STM32G474RET6

> Most STM32's, certainly F4, have HRTIM. That's not true. Only F3 and H7 have HRTIM. HRTIM is a timer dedicated to power electronics applications. You've probably confused advanced timers (TIM1/TIM8) with HRTIM, but these are completely different peripherals. > The F3 is not a good point of comp

Jenkins build is back to normal : NuttX-Nightly-Build #96

See

Re: Adding support for STM32G474RET6

On Tue, Apr 14, 2020 at 9:11 PM Gregory Nutt wrote: > > > In reading about the STM32G4 family, someplace on the STmicro website, > this > > introductory page: > > > > > https://www.st.com/en/microcontrollers-microprocessors/stm32g4-series.html > > > > suggests that there's a "high degree of compa

Re: Adding support for STM32G474RET6

In reading about the STM32G4 family, someplace on the STmicro website, this introductory page: https://www.st.com/en/microcontrollers-microprocessors/stm32g4-series.html suggests that there's a "high degree of compatibility" with the stm32f3 series. I opened the datasheet for one of the stm3

Re: Adding support for STM32G474RET6

On Tue, Apr 14, 2020 at 7:57 PM Gregory Nutt wrote: > > > So this sounds like a new stm32g4 subdirectory would be beneficial. > > You would have to know how pervasive the differences between the chips > are. The STM32F0 cohabitates quite nicely with G0 and L0, for example. > > If, for example, a

Re: Adding support for STM32G474RET6

So this sounds like a new stm32g4 subdirectory would be beneficial. You would have to know how pervasive the differences between the chips are.  The STM32F0 cohabitates quite nicely with G0 and L0, for example. If, for example, all of the peripherals are the same, but there is a differenc

Re: Adding support for STM32G474RET6

On Tue, Apr 14, 2020 at 6:21 PM David Sidrane wrote: > I have not looked at the G part yet so I cannot say for certain, but I can > share this: > > We learned many lessons from the coupling in the stm32 dirs. The take away > was Avoid it! > > The F7 model is much better - the goal is to not have i

RE: Adding support for STM32G474RET6

Hi Nathan, I have not looked at the G part yet so I cannot say for certain, but I can share this: We learned many lessons from the coupling in the stm32 dirs. The take away was Avoid it! The F7 model is much better - the goal is to not have ifdef rash. Layered includes bring it the correct head

Adding support for STM32G474RET6

Regarding STM32 support, I'd like to add architectural and board support for the B-G474E-DPOW1 Discovery board and its STM32G474RET6 microcontroller: https://www.st.com/en/evaluation-tools/b-g474e-dpow1.html My first question is, which directory does this architecture belong in? Looking at the d

Re: [DISCUSS] Release Notes

On Tue, Apr 14, 2020 at 5:13 PM Abdelatif Guettouche wrote: > Are there any concerns or additions to the release notes? I just made some minor changes (most notably, describing the DNS Dual Host support where there was previously a note "what is this? No PR description"). > I don't know what we

Re: [DISCUSS] Release Notes

Are there any concerns or additions to the release notes? I did some re-organisation yesterday. Mainly I put network related changes to their own section and moved some other points that were not where they belong. I don't know what we should put in the first item "What's New In This Release". Ma

SocketCAN Status

Hi, Peter, Has there been any clarification about the state of licensing on SocketCAN code?  I have been rebasing the SocketCAN branch against master periodically, so it is ready to retest and merge when we can resolve the licensing issues.  My understanding is: 1. We would have to include t

[PATCH] arch/arm/src/stm32f7/stm32_flash.c: fix return value of stm32_flash_lock

Hi, Yet another one Best Regards, Juha From 251c978ef83589ee3ab31b367f538692ecc77bf2 Mon Sep 17 00:00:00 2001 From: Juha Niskanen Date: Tue, 14 Apr 2020 18:25:56 +0300 Subject: [PATCH] arch/arm/src/stm32f7/stm32_flash.c: fix return value of stm32_flash_lock --- arch/arm/src/stm32f7/stm

[PATCH] arch/arm/src/stm32l4/stm32l4_1wire.c: fix build error, fix typo

Hi, Yet another trivial build error. Best Regards, Juha From 7756b0d3f401e8fc16740f2f13c57a9d76a353c0 Mon Sep 17 00:00:00 2001 From: Juha Niskanen Date: Tue, 14 Apr 2020 18:20:33 +0300 Subject: [PATCH] arch/arm/src/stm32l4/stm32l4_1wire.c: fix build error, fix typo --- arch/arm/src/lc823450

[PATCH] arch/arm/src/stm32l4/stm32l4_spi.c: add missing ret

Hi Greg, Trivial build error corrected. Best Regards, Juha From 402bdadb6f51ce8879931fa0067fa82bcf3c0677 Mon Sep 17 00:00:00 2001 From: Juha Niskanen Date: Tue, 14 Apr 2020 16:42:09 +0300 Subject: [PATCH] arch/arm/src/stm32l4/stm32l4_spi.c: add missing ret --- arch/arm/src/stm32l4/stm32l4_s

RE: SDIO MMCSD card is not writing/reading files anymore it does mount CMD24 -5 error

Update: I think I have found it. it has to do with 1-bit and 4-bit: The SDIO Card Specification Version 2.0 is also supported with two different databus modes: 1-bit (default) and 4-bit. Nuttx has default 4-bit and that's why I was thrown of. I tried to change the SDIO Clock (DIV) and wan