Hi there, I'm currently working on porting Zephyr to i.MX7 SoC and I'm facing an error with cmake when it is generating the generated_dts_board.h. I want to use only the sram and in my dts I removed t

Hello Michael, You mean setting the same entry for the flash and sram? Something like that? chosen { zephyr,flash = &ocram; zephyr,sram = &ocram; zephyr,console = &uart2; }; What is the usage and purp

Hello Maureen, Thanks for the suggestion. This is an interesting approach as well. I still want to understand how to use the "dummy-flash" and if I can assign the same memory node for the flash and sr

Just to give you an update on this. It works when using 2 different RAMs regions for flash and. But I still want to understand the usage of the "dummy-flash" and if I'm setting it correctly because I'

Kumar, From the source code itself, there is no difference. For now, I'm only testing the shell subsys sample application. I'm not storing anything. The linker does all the necessary job to generate a

Hello, I'd like to know what is the usage of the *_GPIO_FLAGS macro. For example in "dts/bindings/gpio/nxp,kinetis-gpio.yaml" file: And "boards/arm/frdm_k64f/frdm_k64f.dts" file we have This will gene

Hi Erwan, I agree with you about using a more generic name (FLAGS). So basically we will need to update the "samples/basic/button/src/main.c" (SW0_GPIO_INT_CONF ->SW0_GPIO_FLAGS) application and move

Erwan, I submitted a PR to apply these modifications: https://github.com/zephyrproject-rtos/zephyr/pull/7493 -- *dS Diego Sueiro sent from mobile

Hello, I'm having problems when trying to use the SystemView for both frdm_k64f and colibri_imx7d_m4 boards. I followed these instructions and sometimes the SystemView crashes, or reports it was faile

Folks, I was thinking about doing a code cleanup in the dts.fixup and uart and gpio driver for the i.MX7 SoC, where we create redundant defines already covered by devicetree aliases. Here is a breif e

#defines

Andy, Actually, the dts extraction already deals with the driver properties listed in the yaml file. For example, the nxp,imx-uart.yaml, has the following #defines automatically generated for the uart

#defines

Take a look at the documentation to understand how this process works: https://docs.zephyrproject.org/latest/devices/dts/device_tree.html

Hello Zephyrs, I'm developing a shell module for the sensor drivers and I want to validate if the device name passed from the user is a sensor device. I have the CONFIG_USERSAPCE=y. After calling "dev

I managed to solve this by calling "k_thread_access_grant(k_current_get(), dev, NULL)" before calling the "Z_SYSCALL_DRIVER_SENSOR" macro. This question remains open.

In the "soc/arm/nxp_imx/mcimx7_m4/Kconfig.defconfig.mcimx7_m4" we default the GPIO config to "y" which will make the GPIO_IMX config default to "y" as well. I think you can have "CONFIG_GPIO=n" in the