+ Andrzej

On 16/10/2018, 23:26, "users@... on behalf of Ormund Williams" <users@... on behalf of ormundw@...> wrote:

Hi All,

I was looking for some example code showing how to use SPI on an
nRF52840-DK board, especially selecting the pins that will be used.

Regards.

__
Ormund

It seems to be the case that this collides with some RISC-V specific term?

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 virtualization. 

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 mmu/ supervisor mode. And run in machine mode.

The riscv32 hardware, we are running doesn't support mmu or supervisor mode. We want to run zephyr on it. I am looking for some flag kind of thing, that can turn off mmu/supervisor mode.

Please suggest.

On Tue, 2018-10-16 at 23:52 -0700, filip.kubicz@... wrote:

Hello Ormund,
For example of using SPI you can take a look at
tests/drivers/spi/spi_loopback. Config for nRF52840 DK is at
tests/drivers/spi/spi_loopback/boards/nrf52840_pca10056.conf, also
please take a look at
boards/arm/nrf52840_pca10056/nrf52840_pca10056.dts for pin
configuration.

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

Zephyr supports supervisor mode. I want to nullify it at software level.

--

Hello Ormund,

For example of using SPI you can take a look at tests/drivers/spi/spi_loopback. Config for nRF52840 DK is at tests/drivers/spi/spi_loopback/boards/nrf52840_pca10056.conf, also please take a look at boards/arm/nrf52840_pca10056/nrf52840_pca10056.dts for pin configuration.

Regards, Filip

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,
sathya

Hi All,

I was looking for some example code showing how to use SPI on an
nRF52840-DK board, especially selecting the pins that will be used.

Regards.

__
Ormund

Hi Johan,

I don't have a Bluetooth adapter on my machine and "hciconfig" does not show any device available.

Thanks,
Marco

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Hi 
This is seungwoo

Hi Marco,

On Mon, Oct 15, 2018, Marco Tozzini wrote:

On terminal windows #2 "sudo /home/marco/bluez/tools/btproxy -u -i 0"
output:
Listening on /tmp/bt-server-bredr
Opening user channel for hci0
Failed to bind Bluetooth socket: No such device

Any idea why I'm getting that error?

Does your PC have a Bluetooth adapter? Does e.g. running "hciconfig"
show hci0 for you?

Johan

Hi,

I'm experimenting with Zephyr and BLE
I have few Nordic Semi boards and I've been able to successfully compile and run BLE examples for those.

I also would like to use QEMU to test BLE examples but I'm not successful

I'm following the instruction listed here
https://docs.zephyrproject.org/latest/subsystems/bluetooth/devel.html

On terminal windows #1 "ninja run" output:
[0/1] To exit from QEMU enter: 'CTRL+a, x'[QEMU] CPU: qemu32,+nx,+pae
qemu-system-i386: warning: Unknown firmware file in legacy mode: genroms/multiboot.bin
***** Booting Zephyr OS zephyr-v1.13.0-175-g62d7a7a5a *****
Starting Beacon Demo

On terminal windows #2 "sudo /home/marco/bluez/tools/btproxy -u -i 0" output:
Listening on /tmp/bt-server-bredr
Opening user channel for hci0
Failed to bind Bluetooth socket: No such device

Any idea why I'm getting that error?

Thanks,
Marco

Hi,

so,

add_custom_command(TARGET app
POST_BUILD
COMMAND
pwd
)

doesn't work because you want to run the command after the elf target is finished, not the app.

So you want to do;

add_custom_command(TARGET zephyr_prebuilt
POST_BUILD
COMMAND
pwd
)

instead. zephyr_prebuilt is the target for the first linker pass of the elf file.

But zephyr_prebuilt can not be modified from outside of zephyr/CMakeLists.txt. To get around this we could either
possibly move zephyr_prebuilt into the application's scope.

Or avoid modifying zephyr_prebuilt. To avoid modifying zephyr_prebuilt
we could define a new target and command that depends on the elf file.
Something like this;

add_custom_command(
OUTPUT log.txt
COMMAND pwd
DEPENDS zephyr_prebuilt
)
add_custom_target(
log_txt
DEPENDS
log.txt
)

but this will only have pwd run after the first link, if your platform uses multi-pass linking, and you want to run pwd after the final link, you are going to need an upstream change to have the build system give you the name of the final link target.

This new target can be invoked by doing
"ninja log_txt", or by adding log_txt to the 'ALL' target so it is run on
"ninja".

https://github.com/SebastianBoe/zephyr/commit/313f23b7197237163cf7c7d4864bfae86fecbe39

________________________________________
From: Cufi, Carles
Sent: Monday, October 15, 2018 3:52:22 PM
To: Phil Hipp; users@...; Bøe, Sebastian
Subject: RE: [Zephyr-users] How to add post build step after linking zephyr.hexhe

+ Sebastian

From: users@... <users@...> On Behalf Of Phil Hipp
Sent: 15 October 2018 15:48
To: users@...
Subject: [Zephyr-users] How to add post build step after linking zephyr.hexhe

Hi everybody,

I'm currently trying to perform a post build step after the complete zephyr image has been linked. I tried to add following lines at the bottom of my application's CMakeLists.txt (I used pwd just for testing; will be replaced with the correct command later):



add_custom_command(TARGET app

POST_BUILD

COMMAND
pwd)

With these lines the command pwd will be called after linking libapp.a which is to early for my purpose. I need to run the command after the complete zephyr image has been linked to zephyr.*. How could I do that?

Hi everybody,

I want to add a custom target in my application's CMakeLists.txt that can be used to flash my zephyr image signed for use with mcuboot (let's call it signed.hex). I'm pretty sure this can be achieved with add_custom_target, but I don't know the correct command to flash signed.hex from my build directory.