Hi Stefan, Why not join the testing working group and share your input there as

Thanks for the information and feedback. In my eyes it would be perfect if, on the long run, a formalized test system is available. I think for the users it would be perfect to have the possibility

Hi, I have tried mesh on-off sample program on nRF52 DK with and without using crystal and it works fine. I am able to provision nRF52 DK using bluez. When I try mesh program on

Really quickly, I’m not sure if we’ve done anything like this. Typically the testing support has been focused on what we’d use as a developer community for the zephyr project. So we have

Hey, I like to do some code tests for parts of my firmware. I struggling to find out how to setup testing. There is some explanation

Hi, I am trying to use the i2c on my custom board. I can read data from the devices, but (oddly) I cannot write to any of the 3 devices "attached" to the i2c line. I am using SDA on pin P0.06 and SCL

@all Thanks a lot for your support. Thanks Jean ! -- regards, Sathya

Hi Erwan, Thank you for the promising leads! The stm32_clock_control_init() is definitely what I would like. I managed to get a reference to this function using device_get_binding(): /* configure

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

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

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

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

+ Andrzej On 16/10/2018, 23:26, "users@... on behalf of Ormund Williams" <users@... on behalf of ormundw@...> wrote: Hi All, I was

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

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

Hi Devs! Compiling a Zephyr project with target nrf52_pca10040 the sys_rand32_get() works well. But when the target is FRDM-KL25Z the compiler show this error: undefined reference to

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

Thanks Filip, I'm just starting to learn Zephyr and looked thru all the examples but never thought to look in test. Thanks again. __ Ormund

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

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