Mateusz Szafoni

I'm reopening it because nrf53 has not been done yet

I'll take care of STM32MP on day if there is no support in NuttX by then. I'm more interested in STM32MP2, which is probably not available yet. But I don't...

@nicolas71640 Infineon dev boards come with built-in J-Link if I remember correctly, so I recommend using SystemView to debug time related problems. This way you can get much more information...

`stm32` will definitely not be good for stm32h5 because it's Cortex-M33, `stm32` holds Cortex-M3/M4 chips. We have `stm32l5` and `stm32u5` which are Cortex-M33, so most likely stm32h5 could share a...

I'm not too familiar with C-M33 from ST, but I predict that they use the same versions of peripherals (or almost identical), so combining l5,u5 and h5 into one probably...

Configurations with `CONFIG_ALLSYMS` needs to call `tools/mkallsyms.py` (or `tools/mkallsyms.sh`) which is not currently supported by cmake build system. Here's how it's done with make: https://github.com/apache/nuttx/blob/4f9d0149947cc3625726127e491cc5b8f978c690/arch/risc-v/src/Makefile#L164-L171 and something similar must be...

It looks like `CONFIG_NSH_SYMTAB` is also not supported for cmake. We have function to generate symbol table in `cmake/nuttx_add_symtab.cmake` but it's not called anywhere and it's quite possible that this...

@acassis this is another problem for which I created a separate issue https://github.com/apache/nuttx/issues/11080 In this issue, I'm talking more about this page https://nuttx.apache.org/docs/latest/platforms/index.html It's just a wall of links. Something...

> this patch should fix https://github.com/apache/nuttx/issues/10401 issue This issue is about broken `make` build. If we modify cmake to be the same as make - should I assume that cmake...