Nah not internal cache. The SRAM sizes for H723/5 are different from any of
those defined in arch/arm/include/stm32h7/chip.h
Suspect we need to get these correct as other files use these defs also,
such as stm32_allocateheap.c
Is Jorge's PR the one merged on Jul 12 (8ceff0d)?
Thanks,
Robert
On Thu
Hi Robert,
Thank you for the explanation! Is it about internal cache?
Looking at
https://www.st.com/en/microcontrollers-microprocessors/stm32h7-series.html
I can see that H723/5 shares mostly everything with H333/5.
I only tested NuttX on STM32H743ZI and STM32H753BI (I and Jorge added
support to t
Apologies, I should have been more specific, I was referring to parts in
the family which are not currently covered, such as the STM32H723xx which
we use. The RAM sizes definitions in chip.h for
CONFIG_STM32H7_STM32H7X3XX/CONFIG_STM32H7_STM32H7X5XX are incorrect for
the STM32H723xx and STM32H725x
Robert,
STM32H7 family is already supported.
Look at arch/arm/src/stm32h7 and equivalent at boards/
BR,
Alan
On Tuesday, January 16, 2024, Robert Turner wrote:
> Did anyone finish supporting the broader STM32H7xx family? If so, is it
> close to being mergeable or sendable as a patch?
>
> Than
Hi Stewart,
Take this with a grain of salt. I have never used the ioexpander ... took a
quick look after seeing your email.
You need to populate ioexpander_ops_s within your board specific files.
IOEXP_WRITEPIN is the "virtual function" that calls your board specific
write_pin function (which call
Hello Bowen,
Thank you for you help. I am not sure if this question is for you or is
more architecture specific?
I am looking at implementing the the relay ops (set()/get()) functions
within the drivers/power/relay/relay.c file. I can see how to implement
this based on the drivers/power/rela
Hi Zhe
I am working on tag nuttx-12.2.1.
Your referenced commit did indeed fix the issue.
My apologies for not trying on master. I mistakenly though the error was in the
TUN device driver, which I noticed had not changed since nuttx-12.2.1.
Thanks a lot!
Kian
F
