Hi, You can just remove virtualcom stuff, samples/subsys/usb/console/prj.conf should assign right console with: CONFIG_UART_CONSOLE_ON_DEV_NAME="CDC_ACM_0" Best regards Andrei Emeltchenko

#dts #defconfig

Is it compulsory to add the node "virtualcom" to configure a USB virtual com port via USB-OTG-HS for STM32F407 under Zephyr 2.0.99? I got the following code in DTS from a partner but it cannot be buil

#dts #defconfig

@all Thanks a lot for your support. Thanks Jean !

#customboard #defconfig #supervisormode

Hi Sathya, Zephyr for riscv runs only in machine mode. All threads execute in machine mode. Regards, Jean-Paul

#customboard #defconfig #supervisormode

Hi Andrew, Thanks a lot. Sorry for the trouble.

#customboard #defconfig #supervisormode

What RISC-V calls "machine mode" is what the Zephyr documentation refers to as "supervisor" or "privileged" mode. You don't need to do anything. Andrew

#customboard #defconfig #supervisormode

We are talking past each other. What is your definition of "user mode"? I don't think we are using the same terminology. I don't know what you mean by "machine mode". You can't have the entire kernel

#customboard #defconfig #supervisormode

That's right! In RISC-V terms, Machine mode has access to all system resources and is the mandatory mode to implement. Supervisor mode has a different usage model, which I guess used for virtualizatio

#customboard #defconfig #supervisormode

Thanks. Actually I want to remove any supervisor mode access in the code. We don't want to have mmu. We want to run in user/machine mode. I got your point on usermode. Is there a way I can turn off mm

#customboard #defconfig #supervisormode

Hi, User mode is currently only supported on x86, ARM, and ARC CPUs. The documentation uses "supervisor mode" to refer to non-user mode, i.e. all CPU instructions may be executed and all memory may be

#customboard #defconfig #supervisormode

Where did you find this information? For RISC-V SoCs, the supervisor mode is only used when the base architecture has the 'S' extension. Since there is no Supervisor enabled SoCs supported by Zephyr s

#customboard #defconfig #supervisormode

Hi Zephyr supports supervisor mode. I want to nullify it at software level. corresponding dts , we are using is "riscv32-qemu.dtsi" regards, sathya

#customboard #defconfig #supervisormode

Hi Sathya, Which SoC are you trying with? AFAIK all supported SoC's only incorporate Machine mode access, not even User mode. Supervisor mode is meant for a full-fledged operating system. Thanks, Mani

#customboard #defconfig #supervisormode

Hi, Is there a way to run zephyr only in user/machine mode ? I am trying it for riscv32 architecture. We dont want to run in supervisor mode. Please let me know note: I am new to zephyr os. regards, s

#customboard #defconfig #supervisormode

Hi Stefan, If your board selects HAS_DTS_I2C_DEVICE, then you should define CONFIG_LSM6DS0_I2C_MASTER_DEV_NAME and CONFIG_LSM6DS0_I2C_ADDR in your board dts.fixup file rather than myboard_defconfig. S

#sensor #dts #defconfig

Hej I am failing to get my LSM6DS3(almost LSM6DS0) sensor rightfully setup. Maybe someone can give me a hint. My system: LSM6DS3 <--> I2C1 @ stm32F412 <--> Zephyr OS I created an own board for that. I

#sensor #dts #defconfig