Date   

Were to send patches & Looking for a example for ADC and DFSDM for the stm32f4

Stefan Jaritz
 

Hej

I still playing a bit around with Zephyr OS.

I manged so far to setup the UART1 using PA10 & PA15. This config is not included. I can submit a patch. Who is maintaining the stm32 dts?

Now I want to go one step further. I would like to use the ADC and the DFSDM module of the stm32f4. I was checking the sample section. I only found the "grove_temperature" as an ADC sample. But for me it still remains unclear how to do ADC in Zephyr OS from the scratch.


Maybe someone can explain it to me at an example:

1) ADC

My "simple" problem is to read the PC1(ADC Channel 11), PC3(ADC Channel 13) and VRefInt. I created my own board. I would like to know all the necessary steps to finally read in my main.c a value from the ADC :D

Think to solve this I need to add some lines at

pinmux.c

myBoard.dts

myBoard_defconfig

main.c

2nd) DFSDM

The stm32f4 MCU contains a DFSDM interface. I like to use it to read microphone data. Are there people who tried to do this in zephyr? What were the steps? Is there a DFSDM driver?

Kind regards!

Stefan


Re: I am not able to read messages sent by nordic to nrf Connect app using the UART services UUID #ble #nrf52832 #bluetoothmesh

Carles Cufi
 

Hi there,

 

Zephyr doesn’t support the “Nordic UART Service”. That is a proprietary service that is only implemented in the Nordic SDK.

It should be quite simple to implement using the Zephyr Bluetooth APIs though, so feel free to give it a go!

 

Carles

 

 

From: users@... <users@...> On Behalf Of Rajat Kalyan
Sent: 19 June 2018 06:07
To: users@...
Subject: [Zephyr-users] I am not able to read messages sent by nordic to nrf Connect app using the UART services UUID #bluetoothmesh #ble #nrf52832

 

Hi Everyone,

I am able to connect my nordic microcontroller to my bluetooth by making a few changes in the UUID and some parameter in the beacon sample code given in the zephyr example codes.
But i am not able to read the messages sent on the UART service.
As soon as i open the nrf toolbox and click on the UART choice in the app.
The app connects to the nordic bluetooth but disconnects immediately and says,"Device does not have required services" .

Kindly help me out of this

Thanks 
Rajat


I am not able to read messages sent by nordic to nrf Connect app using the UART services UUID #ble #nrf52832 #bluetoothmesh

Rajat Kalyan
 

Hi Everyone,

I am able to connect my nordic microcontroller to my bluetooth by making a few changes in the UUID and some parameter in the beacon sample code given in the zephyr example codes.
But i am not able to read the messages sent on the UART service.
As soon as i open the nrf toolbox and click on the UART choice in the app.
The app connects to the nordic bluetooth but disconnects immediately and says,"Device does not have required services" .

Kindly help me out of this

Thanks 
Rajat


Re: k_sleep on mimxrt1050_evk board

Maureen Helm
 

Hi Marco,

This board has two versions, EVK and EVKB, which correspond to different revisions of silicon (A0 and A1, respectively). The EVK board works just fine, but I was able to reproduce the issue on the EVKB board. There does appear to be a problem with the timer, but I’m still investigating.

 

Please go ahead and file a bug so we can track it.

 

Maureen

 

From: users@... [mailto:users@...] On Behalf Of marco.hoefle@...
Sent: Friday, June 15, 2018 12:48 AM
To: users@...
Subject: Re: [Zephyr-users] k_sleep on mimxrt1050_evk board

 

Hello Anas,
I will, I just let Maureen have a look first just in case I need to add something to the kernel config or I am doing something wrong.
Marco


Re: Bluetooth mesh provisionning got stuck #bluetoothmesh #nrf52840

Rodrigo Peixoto <rodrigopex@...>
 

Hey, guys sorry for the delay.

Vikrant, I cannot even provision it for the first time I try.

Johan, yes I have the CONFIG_BT_TINYCRYPT_ECC=y in my conf file. 

Is there anything I can show you to give more details? 

I could not solve this yet.



Best regards,
Rodrigo Peixoto
Co-founder and Technical advisor

+55 (82) 98144-8585
http://ayna.tech | Skype: rodrigopex




Re: Bluetooth mesh provisionning got stuck #bluetoothmesh #nrf52840

Johan Hedberg
 

Hi Rodrigo,

On Fri, Jun 15, 2018, Rodrigo Peixoto wrote:
[bt] [DBG] bt_mesh_pb_gatt_open: (0x200026fc) conn 0x2000085c
[bt] [DBG] bt_mesh_pb_gatt_recv: (0x200026fc) 2 bytes: 0000
[bt] [DBG] prov_invite: (0x200026fc) Attention Duration: 0 seconds
[bt] [DBG] bt_mesh_pb_gatt_recv: (0x200026fc) 6 bytes: 020000020304
[bt] [DBG] prov_start: (0x200026fc) Algorithm: 0x00
[bt] [DBG] prov_start: (0x200026fc) Public Key: 0x00
[bt] [DBG] prov_start: (0x200026fc) Auth Method: 0x02
[bt] [DBG] prov_start: (0x200026fc) Auth Action: 0x03
[bt] [DBG] prov_start: (0x200026fc) Auth Size: 0x04
[BLUETOOTH] [DBG] output_number: OOB Number: 1224 <-- this line is
printed by my code
[bt] [DBG] bt_mesh_pb_gatt_recv: (0x200026fc) 65 bytes:
03d5287e2bd8d07a6b5346d103737dbbf8085f008e13e5586ebc453dcab8fc66d3bf5830f6e6e9935dc175d679bbe2cf2d1d356d83fe560e750a742c179803c9
[bt] [DBG] prov_pub_key: (0x200026fc) Remote Public Key:
d5287e2bd8d07a6b5346d103737dbbf8085f008e13e5586ebc453dcab8fc66d3bf5830f6e6e9935dc175d679bbe2cf2d1d356d83fe560e750a742c179803c990
[bt] [DBG] prov_clear_tx: (0x200026fc)
[bt] [WRN] prov_pub_key: Waiting for local public key

It stops right here...
Do you have CONFIG_BT_TINYCRYPT_ECC=y in your configuration?

Johan


Re: Bluetooth mesh provisionning got stuck #bluetoothmesh #nrf52840

vikrant8051 <vikrant8051@...>
 

Hi Rodrigo,

Can you access Models after following these steps ?

Provisioning & Configuration of Models -> un-provisioning (using reset node option in #nRFMesh) -> re-provisioning & re-configuration of Models -> reset / power reset the circuit
-> reconnect to same proxy node -> And try to access Models (means try to control LED associate with Gen. OnOff Server)

Thank You !!

On Sat, Jun 16, 2018 at 2:59 AM, Rodrigo Peixoto <rodrigopex@...> wrote:
Hi guys.


Board: nrf52840_pca10056
Zephyr version: 1.12.0

I am trying to add the mesh feature to my project. I am using a nrf52840_10056pca board, and I'm adding the samples/bluetooth/mesh code to project. 

In this project I have running console shell, mcumgr, PWM, SAADC, thermometer, Bluetooth mesh. Everything is compiling and is working properly. But I am getting stuck when I try to provision the device to enter to the Bluetooth mesh network.

The log for the provision when I press the button provision on the Nordic Mesh app for iOS:

    [bt] [DBG] bt_mesh_pb_gatt_open: (0x200026fc) conn 0x2000085c
    [bt] [DBG] bt_mesh_pb_gatt_recv: (0x200026fc) 2 bytes: 0000
    [bt] [DBG] prov_invite: (0x200026fc) Attention Duration: 0 seconds
    [bt] [DBG] bt_mesh_pb_gatt_recv: (0x200026fc) 6 bytes: 020000020304
    [bt] [DBG] prov_start: (0x200026fc) Algorithm:   0x00
    [bt] [DBG] prov_start: (0x200026fc) Public Key:  0x00
    [bt] [DBG] prov_start: (0x200026fc) Auth Method: 0x02
    [bt] [DBG] prov_start: (0x200026fc) Auth Action: 0x03
    [bt] [DBG] prov_start: (0x200026fc) Auth Size:   0x04
    [BLUETOOTH] [DBG] output_number: OOB Number: 1224  <-- this line is printed by my code
    [bt] [DBG] bt_mesh_pb_gatt_recv: (0x200026fc) 65 bytes: 03d5287e2bd8d07a6b5346d103737dbbf8085f008e13e5586ebc453dcab8fc66d3bf5830f6e6e9935dc175d679bbe2cf2d1d356d83fe560e750a742c179803c9
    [bt] [DBG] prov_pub_key: (0x200026fc) Remote Public Key: d5287e2bd8d07a6b5346d103737dbbf8085f008e13e5586ebc453dcab8fc66d3bf5830f6e6e9935dc175d679bbe2cf2d1d356d83fe560e750a742c179803c990
    [bt] [DBG] prov_clear_tx: (0x200026fc) 
    [bt] [WRN] prov_pub_key: Waiting for local public key

It stops right here...

Any clue on that? I have no idea what to do. When I run the sample separately it is being provisioned. I have already removed the OTA, and other features but nothing seems to fix that.

I hope you can help me.


Best regards,
Rodrigo Peixoto
Co-founder and Technical advisor

+55 (82) 98144-8585
http://ayna.tech | Skype: rodrigopex




Bluetooth mesh provisionning got stuck #bluetoothmesh #nrf52840

Rodrigo Peixoto <rodrigopex@...>
 

Hi guys.


Board: nrf52840_pca10056
Zephyr version: 1.12.0

I am trying to add the mesh feature to my project. I am using a nrf52840_10056pca board, and I'm adding the samples/bluetooth/mesh code to project. 

In this project I have running console shell, mcumgr, PWM, SAADC, thermometer, Bluetooth mesh. Everything is compiling and is working properly. But I am getting stuck when I try to provision the device to enter to the Bluetooth mesh network.

The log for the provision when I press the button provision on the Nordic Mesh app for iOS:

    [bt] [DBG] bt_mesh_pb_gatt_open: (0x200026fc) conn 0x2000085c
    [bt] [DBG] bt_mesh_pb_gatt_recv: (0x200026fc) 2 bytes: 0000
    [bt] [DBG] prov_invite: (0x200026fc) Attention Duration: 0 seconds
    [bt] [DBG] bt_mesh_pb_gatt_recv: (0x200026fc) 6 bytes: 020000020304
    [bt] [DBG] prov_start: (0x200026fc) Algorithm:   0x00
    [bt] [DBG] prov_start: (0x200026fc) Public Key:  0x00
    [bt] [DBG] prov_start: (0x200026fc) Auth Method: 0x02
    [bt] [DBG] prov_start: (0x200026fc) Auth Action: 0x03
    [bt] [DBG] prov_start: (0x200026fc) Auth Size:   0x04
    [BLUETOOTH] [DBG] output_number: OOB Number: 1224  <-- this line is printed by my code
    [bt] [DBG] bt_mesh_pb_gatt_recv: (0x200026fc) 65 bytes: 03d5287e2bd8d07a6b5346d103737dbbf8085f008e13e5586ebc453dcab8fc66d3bf5830f6e6e9935dc175d679bbe2cf2d1d356d83fe560e750a742c179803c9
    [bt] [DBG] prov_pub_key: (0x200026fc) Remote Public Key: d5287e2bd8d07a6b5346d103737dbbf8085f008e13e5586ebc453dcab8fc66d3bf5830f6e6e9935dc175d679bbe2cf2d1d356d83fe560e750a742c179803c990
    [bt] [DBG] prov_clear_tx: (0x200026fc) 
    [bt] [WRN] prov_pub_key: Waiting for local public key

It stops right here...

Any clue on that? I have no idea what to do. When I run the sample separately it is being provisioned. I have already removed the OTA, and other features but nothing seems to fix that.

I hope you can help me.


Best regards,
Rodrigo Peixoto
Co-founder and Technical advisor

+55 (82) 98144-8585
http://ayna.tech | Skype: rodrigopex



Re: k_sleep on mimxrt1050_evk board

marco.hoefle@...
 

Hello Anas,
I will, I just let Maureen have a look first just in case I need to add something to the kernel config or I am doing something wrong.
Marco


Re: k_sleep on mimxrt1050_evk board

marco.hoefle@...
 

Hello Maureen,
Sure, I tried blinky and synchronisation.
Both didn't work.

Here the detailed steps:

marco@L-xx:~/projects/misc/zephyr/samples/basic/blinky/build$ export ZEPHYR_SDK_INSTALL_DIR=/opt/zephyr-sdk/
marco@L-xx:~/projects/misc/zephyr/samples/basic/blinky/build$ export ZEPHYR_TOOLCHAIN_VARIANT=zephyr
marco@L-xx:~/projects/misc/zephyr/samples/basic/blinky/build$ source ~/projects/misc/zephyr/zephyr-env.sh
marco@L-xx:~/projects/misc/zephyr/samples/basic/blinky/build$ cmake -DBOARD=mimxrt1050_evk ..
CMake Deprecation Warning at /home/marco/projects/misc/zephyr/cmake/app/boilerplate.cmake:38 (cmake_policy):
  The OLD behavior for policy CMP0000 will be removed from a future version
  of CMake.

  The cmake-policies(7) manual explains that the OLD behaviors of all
  policies are deprecated and that a policy should be set to OLD only under
  specific short-term circumstances.  Projects should be ported to the NEW
  behavior and not rely on setting a policy to OLD.
Call Stack (most recent call first):
  CMakeLists.txt:1 (include)


-- Found PythonInterp: /usr/bin/python3 (found suitable version "3.6.5", minimum required is "3.4")
-- Selected BOARD mimxrt1050_evk
Zephyr version: 1.12.0
Parsing Kconfig tree in /home/marco/projects/misc/zephyr/Kconfig
Using /home/marco/projects/misc/zephyr/boards/arm/mimxrt1050_evk/mimxrt1050_evk_defconfig as base
Merging /home/marco/projects/misc/zephyr/samples/basic/blinky/prj.conf
/home/marco/projects/misc/zephyr/samples/basic/blinky/prj.conf:1: warning: GPIO (defined at drivers/gpio/Kconfig:9, /home/marco/projects/misc/zephyr/arch/arm/soc/nordic_nrf/Kconfig.defconfig:15, arch/arm/soc/nxp_imx/mcimx7_m4/Kconfig.defconfig.mcimx7_m4:29, /home/marco/projects/misc/zephyr/arch/arm/soc/nxp_imx/rt/Kconfig.defconfig.mimxrt1052:30, /home/marco/projects/misc/zephyr/arch/arm/soc/nxp_kinetis/k6x/Kconfig.defconfig.mk64f12:36, /home/marco/projects/misc/zephyr/arch/arm/soc/nxp_lpc/lpc54xxx/Kconfig.defconfig.lpc54114_m0:22, /home/marco/projects/misc/zephyr/arch/arm/soc/silabs_exx32/efm32wg/Kconfig.defconfig.efm32wg:15) set more than once. Old value: "y", new value: "y".
/home/marco/projects/misc/zephyr/samples/basic/blinky/prj.conf:2: warning: SERIAL (defined at drivers/serial/Kconfig:9) set more than once. Old value: "y", new value: "n".
warning: OSC_EXTERNAL (defined at /home/marco/projects/misc/zephyr/arch/arm/soc/nxp_kinetis/Kconfig:57) was assigned the value "y" but got the value "n" -- check dependencies
warning: UART_CONSOLE (defined at drivers/console/Kconfig:40) was assigned the value "y" but got the value "n" -- check dependencies
-- Generating zephyr/include/generated/generated_dts_board.h
mimxrt1050_evk.dts_compiled: Warning (unit_address_vs_reg): Node /leds/led@0 has a unit name, but no reg property
mimxrt1050_evk.dts_compiled: Warning (unit_address_vs_reg): Node /gpio_keys/button@0 has a unit name, but no reg property
-- Cache files will be written to: /home/marco/.cache/zephyr
-- The C compiler identification is GNU 6.2.0
-- The CXX compiler identification is GNU 6.2.0
-- The ASM compiler identification is GNU
-- Found assembler: /opt/zephyr-sdk/sysroots/x86_64-pokysdk-linux/usr/bin/arm-zephyr-eabi/arm-zephyr-eabi-gcc
-- Performing Test toolchain_is_ok
-- Performing Test toolchain_is_ok - Success
-- Configuring done
-- Generating done
-- Build files have been written to: /home/marco/projects/misc/zephyr/samples/basic/blinky/build
marco@L-xx:~/projects/misc/zephyr/samples/basic/blinky/build$ make
Scanning dependencies of target kobj_types_h_target
[  1%] Generating include/generated/kobj-types-enum.h, include/generated/otype-to-str.h
[  1%] Built target kobj_types_h_target
Scanning dependencies of target syscall_macros_h_target
[  2%] Generating include/generated/syscall_macros.h
[  2%] Built target syscall_macros_h_target
Scanning dependencies of target syscall_list_h_target
[  3%] Generating always_rebuild
Building for board mimxrt1050_evk
[  4%] Generating misc/generated/syscalls.json
[  5%] Generating include/generated/syscall_dispatch.c, include/generated/syscall_list.h
[  5%] Built target syscall_list_h_target
Scanning dependencies of target driver_validation_h_target
[  6%] Generating include/generated/driver-validation.h
[  6%] Built target driver_validation_h_target
Scanning dependencies of target offsets
[  7%] Building C object zephyr/CMakeFiles/offsets.dir/arch/arm/core/offsets/offsets.c.obj
[  8%] Linking C static library liboffsets.a
[  8%] Built target offsets
Scanning dependencies of target offsets_h
[  9%] Generating include/generated/offsets.h
[  9%] Built target offsets_h
Scanning dependencies of target app
[ 10%] Building C object CMakeFiles/app.dir/home/marco/projects/misc/zephyr/lib/libc/minimal/source/stdlib/atoi.c.obj
[ 11%] Building C object CMakeFiles/app.dir/home/marco/projects/misc/zephyr/lib/libc/minimal/source/stdlib/strtol.c.obj
[ 12%] Building C object CMakeFiles/app.dir/home/marco/projects/misc/zephyr/lib/libc/minimal/source/stdlib/strtoul.c.obj
[ 13%] Building C object CMakeFiles/app.dir/home/marco/projects/misc/zephyr/lib/libc/minimal/source/string/strncasecmp.c.obj
[ 14%] Building C object CMakeFiles/app.dir/home/marco/projects/misc/zephyr/lib/libc/minimal/source/string/strstr.c.obj
[ 15%] Building C object CMakeFiles/app.dir/home/marco/projects/misc/zephyr/lib/libc/minimal/source/string/string.c.obj
[ 16%] Building C object CMakeFiles/app.dir/home/marco/projects/misc/zephyr/lib/libc/minimal/source/stdout/prf.c.obj
[ 17%] Building C object CMakeFiles/app.dir/home/marco/projects/misc/zephyr/lib/libc/minimal/source/stdout/stdout_console.c.obj
[ 18%] Building C object CMakeFiles/app.dir/home/marco/projects/misc/zephyr/lib/libc/minimal/source/stdout/sprintf.c.obj
[ 19%] Building C object CMakeFiles/app.dir/home/marco/projects/misc/zephyr/lib/libc/minimal/source/stdout/fprintf.c.obj
[ 20%] Building C object CMakeFiles/app.dir/src/main.c.obj
[ 21%] Linking C static library libapp.a
[ 21%] Built target app
Scanning dependencies of target kernel
[ 22%] Building C object zephyr/kernel/CMakeFiles/kernel.dir/alert.c.obj
[ 23%] Building C object zephyr/kernel/CMakeFiles/kernel.dir/device.c.obj
[ 24%] Building C object zephyr/kernel/CMakeFiles/kernel.dir/errno.c.obj
[ 25%] Building C object zephyr/kernel/CMakeFiles/kernel.dir/idle.c.obj
[ 26%] Building C object zephyr/kernel/CMakeFiles/kernel.dir/init.c.obj
[ 27%] Building C object zephyr/kernel/CMakeFiles/kernel.dir/mailbox.c.obj
[ 28%] Building C object zephyr/kernel/CMakeFiles/kernel.dir/mem_slab.c.obj
[ 29%] Building C object zephyr/kernel/CMakeFiles/kernel.dir/mempool.c.obj
[ 30%] Building C object zephyr/kernel/CMakeFiles/kernel.dir/msg_q.c.obj
[ 31%] Building C object zephyr/kernel/CMakeFiles/kernel.dir/mutex.c.obj
[ 32%] Building C object zephyr/kernel/CMakeFiles/kernel.dir/pipes.c.obj
[ 34%] Building C object zephyr/kernel/CMakeFiles/kernel.dir/queue.c.obj
[ 35%] Building C object zephyr/kernel/CMakeFiles/kernel.dir/sched.c.obj
[ 36%] Building C object zephyr/kernel/CMakeFiles/kernel.dir/sem.c.obj
[ 37%] Building C object zephyr/kernel/CMakeFiles/kernel.dir/stack.c.obj
[ 38%] Building C object zephyr/kernel/CMakeFiles/kernel.dir/sys_clock.c.obj
[ 39%] Building C object zephyr/kernel/CMakeFiles/kernel.dir/system_work_q.c.obj
[ 40%] Building C object zephyr/kernel/CMakeFiles/kernel.dir/thread.c.obj
[ 41%] Building C object zephyr/kernel/CMakeFiles/kernel.dir/thread_abort.c.obj
[ 42%] Building C object zephyr/kernel/CMakeFiles/kernel.dir/version.c.obj
[ 43%] Building C object zephyr/kernel/CMakeFiles/kernel.dir/work_q.c.obj
[ 44%] Building C object zephyr/kernel/CMakeFiles/kernel.dir/smp.c.obj
[ 45%] Building C object zephyr/kernel/CMakeFiles/kernel.dir/timer.c.obj
[ 46%] Linking C static library libkernel.a
[ 46%] Built target kernel
Scanning dependencies of target linker_script
[ 47%] Generating linker.cmd
[ 47%] Built target linker_script
Scanning dependencies of target zephyr
[ 48%] Building C object zephyr/CMakeFiles/zephyr.dir/arch/common/isr_tables.c.obj
[ 49%] Building C object zephyr/CMakeFiles/zephyr.dir/arch/arm/soc/nxp_imx/rt/soc.c.obj
[ 50%] Building C object zephyr/CMakeFiles/zephyr.dir/arch/arm/soc/nxp_imx/rt/arm_mpu_regions.c.obj
[ 51%] Building C object zephyr/CMakeFiles/zephyr.dir/lib/thread_entry.c.obj
[ 52%] Building C object zephyr/CMakeFiles/zephyr.dir/lib/crc/crc16_sw.c.obj
[ 53%] Building C object zephyr/CMakeFiles/zephyr.dir/lib/crc/crc8_sw.c.obj
[ 54%] Building C object zephyr/CMakeFiles/zephyr.dir/lib/mempool/mempool.c.obj
[ 55%] Building C object zephyr/CMakeFiles/zephyr.dir/lib/rbtree/rb.c.obj
[ 56%] Building C object zephyr/CMakeFiles/zephyr.dir/misc/generated/configs.c.obj
[ 57%] Building C object zephyr/CMakeFiles/zephyr.dir/ext/hal/nxp/mcux/devices/MIMXRT1052/fsl_clock.c.obj
[ 58%] Building C object zephyr/CMakeFiles/zephyr.dir/ext/hal/nxp/mcux/drivers/imx/fsl_gpio.c.obj
[ 59%] Building C object zephyr/CMakeFiles/zephyr.dir/drivers/clock_control/clock_control_mcux_ccm.c.obj
[ 60%] Building C object zephyr/CMakeFiles/zephyr.dir/drivers/timer/sys_clock_init.c.obj
[ 61%] Building C object zephyr/CMakeFiles/zephyr.dir/drivers/timer/cortex_m_systick.c.obj
[ 62%] Linking C static library libzephyr.a
[ 62%] Built target zephyr
Scanning dependencies of target arch__arm__core
[ 63%] Building ASM object zephyr/arch/arm/core/CMakeFiles/arch__arm__core.dir/exc_exit.S.obj
[ 64%] Building C object zephyr/arch/arm/core/CMakeFiles/arch__arm__core.dir/irq_init.c.obj
[ 65%] Building C object zephyr/arch/arm/core/CMakeFiles/arch__arm__core.dir/swap.c.obj
[ 67%] Building ASM object zephyr/arch/arm/core/CMakeFiles/arch__arm__core.dir/swap_helper.S.obj
[ 68%] Building C object zephyr/arch/arm/core/CMakeFiles/arch__arm__core.dir/fault.c.obj
[ 69%] Building C object zephyr/arch/arm/core/CMakeFiles/arch__arm__core.dir/irq_manage.c.obj
[ 70%] Building C object zephyr/arch/arm/core/CMakeFiles/arch__arm__core.dir/thread.c.obj
[ 71%] Building ASM object zephyr/arch/arm/core/CMakeFiles/arch__arm__core.dir/cpu_idle.S.obj
[ 72%] Building ASM object zephyr/arch/arm/core/CMakeFiles/arch__arm__core.dir/fault_s.S.obj
[ 73%] Building C object zephyr/arch/arm/core/CMakeFiles/arch__arm__core.dir/fatal.c.obj
[ 74%] Building C object zephyr/arch/arm/core/CMakeFiles/arch__arm__core.dir/sys_fatal_error_handler.c.obj
[ 75%] Building C object zephyr/arch/arm/core/CMakeFiles/arch__arm__core.dir/thread_abort.c.obj
[ 76%] Building ASM object zephyr/arch/arm/core/CMakeFiles/arch__arm__core.dir/isr_wrapper.S.obj
[ 77%] Linking C static library libarch__arm__core.a
[ 77%] Built target arch__arm__core
Scanning dependencies of target arch__arm__core__cortex_m
[ 78%] Building ASM object zephyr/arch/arm/core/cortex_m/CMakeFiles/arch__arm__core__cortex_m.dir/vector_table.S.obj
[ 79%] Building ASM object zephyr/arch/arm/core/cortex_m/CMakeFiles/arch__arm__core__cortex_m.dir/reset.S.obj
[ 80%] Building ASM object zephyr/arch/arm/core/cortex_m/CMakeFiles/arch__arm__core__cortex_m.dir/nmi_on_reset.S.obj
[ 81%] Building C object zephyr/arch/arm/core/cortex_m/CMakeFiles/arch__arm__core__cortex_m.dir/prep_c.c.obj
[ 82%] Building C object zephyr/arch/arm/core/cortex_m/CMakeFiles/arch__arm__core__cortex_m.dir/scb.c.obj
[ 83%] Building C object zephyr/arch/arm/core/cortex_m/CMakeFiles/arch__arm__core__cortex_m.dir/nmi.c.obj
[ 84%] Building C object zephyr/arch/arm/core/cortex_m/CMakeFiles/arch__arm__core__cortex_m.dir/exc_manage.c.obj
[ 85%] Linking C static library libarch__arm__core__cortex_m.a
[ 85%] Built target arch__arm__core__cortex_m
Scanning dependencies of target arch__arm__core__cortex_m__mpu
[ 86%] Building C object zephyr/arch/arm/core/cortex_m/mpu/CMakeFiles/arch__arm__core__cortex_m__mpu.dir/arm_core_mpu.c.obj
[ 87%] Building C object zephyr/arch/arm/core/cortex_m/mpu/CMakeFiles/arch__arm__core__cortex_m__mpu.dir/arm_mpu.c.obj
[ 88%] Linking C static library libarch__arm__core__cortex_m__mpu.a
[ 88%] Built target arch__arm__core__cortex_m__mpu
Scanning dependencies of target boards__arm__mimxrt1050_evk
[ 89%] Building C object zephyr/boards/boards/arm/mimxrt1050_evk/CMakeFiles/boards__arm__mimxrt1050_evk.dir/pinmux.c.obj
[ 90%] Linking C static library libboards__arm__mimxrt1050_evk.a
[ 90%] Built target boards__arm__mimxrt1050_evk
Scanning dependencies of target drivers__gpio
[ 91%] Building C object zephyr/drivers/gpio/CMakeFiles/drivers__gpio.dir/gpio_mcux_igpio.c.obj
[ 92%] Linking C static library libdrivers__gpio.a
[ 92%] Built target drivers__gpio
Scanning dependencies of target zephyr_prebuilt
[ 93%] Building C object zephyr/CMakeFiles/zephyr_prebuilt.dir/misc/empty_file.c.obj
[ 94%] Linking C executable zephyr_prebuilt.elf
Memory region         Used Size  Region Size  %age Used
           FLASH:        8976 B       128 KB      6.85%
            SRAM:        3844 B       128 KB      2.93%
        IDT_LIST:          84 B         2 KB      4.10%
[ 94%] Built target zephyr_prebuilt
Scanning dependencies of target linker_pass_final_script
[ 95%] Generating linker_pass_final.cmd
[ 95%] Built target linker_pass_final_script
[ 96%] Generating isr_tables.c
Scanning dependencies of target kernel_elf
[ 97%] Building C object zephyr/CMakeFiles/kernel_elf.dir/misc/empty_file.c.obj
[ 98%] Building C object zephyr/CMakeFiles/kernel_elf.dir/isr_tables.c.obj
[100%] Linking C executable zephyr.elf
Generating files from zephyr.elf for board: mimxrt1050_evk

marco@L-xx:~/projects/misc/zephyr/samples/basic/blinky/build$ make debug
[  1%] Built target kobj_types_h_target
[  2%] Built target syscall_macros_h_target
[  3%] Generating always_rebuild
Building for board mimxrt1050_evk
[  4%] Generating misc/generated/syscalls.json
[  5%] Built target syscall_list_h_target
[  6%] Built target driver_validation_h_target
[  8%] Built target offsets
[  9%] Built target offsets_h
[ 33%] Built target kernel
[ 45%] Built target app
[ 46%] Built target linker_script
[ 62%] Built target zephyr
[ 76%] Built target arch__arm__core
[ 84%] Built target arch__arm__core__cortex_m
[ 87%] Built target arch__arm__core__cortex_m__mpu
[ 89%] Built target boards__arm__mimxrt1050_evk
[ 91%] Built target drivers__gpio
[ 93%] Built target zephyr_prebuilt
[ 94%] Built target linker_pass_final_script
[ 98%] Built target kernel_elf
[100%] Debugging mimxrt1050_evk
Using runner: jlink
J-Link GDB server running on port 2331
SEGGER J-Link GDB Server V6.32b Command Line Version

JLinkARM.dll V6.32b (DLL compiled May  8 2018 18:28:22)

-----GDB Server start settings-----
GDBInit file:                  none
GDB Server Listening port:     2331
SWO raw output listening port: 2332
Terminal I/O port:             2333
Accept remote connection:      yes
Generate logfile:              off
Verify download:               off
Init regs on start:            off
Silent mode:                   on
Single run mode:               on
Target connection timeout:     0 ms
------J-Link related settings------
J-Link Host interface:         USB
J-Link script:                 none
J-Link settings file:          none
------Target related settings------
Target device:                 Cortex-M7
Target interface:              SWD
Target interface speed:        auto
Target endian:                 little

GNU gdb (GDB) 7.11.0.20160511-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "--host=x86_64-pokysdk-linux --target=arm-zephyr-eabi".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /home/marco/projects/misc/zephyr/samples/basic/blinky/build/zephyr/zephyr.elf...done.
Remote debugging using :2331
0xa05f0000 in ?? ()
Resetting target
Loading section text, size 0x2176 lma 0x0
Loading section .ARM.exidx, size 0x8 lma 0x2178
Loading section devconfig, size 0x54 lma 0x2180
Loading section rodata, size 0xc0 lma 0x21d4
Loading section datas, size 0x28 lma 0x2294
Loading section initlevel, size 0x54 lma 0x22bc
Start address 0x14e4, load size 8974
Transfer rate: 83 KB/sec, 1121 bytes/write.
(gdb) c
Continuing.

Program received signal SIGTRAP, Trace/breakpoint trap.
0xa05f0000 in ?? ()
(gdb) c
Continuing.

Program received signal SIGTRAP, Trace/breakpoint trap.
0xa05f0000 in ?? ()
(gdb)

(gdb) mon reset 0
Resets core & peripherals via SYSRESETREQ & VECTRESET bit.
(gdb) load ~/projects/misc/zephyr/samples/basic/blinky/build/zephyr/zephyr.elf
Loading section text, size 0x2176 lma 0x0
Loading section .ARM.exidx, size 0x8 lma 0x2178
Loading section devconfig, size 0x54 lma 0x2180
Loading section rodata, size 0xc0 lma 0x21d4
Loading section datas, size 0x28 lma 0x2294
Loading section initlevel, size 0x54 lma 0x22bc
Start address 0x14e4, load size 8974
Transfer rate: 85 KB/sec, 1121 bytes/write.
(gdb) break main.c:37
Note: breakpoint 4 also set at pc 0xbbc.
Breakpoint 5 at 0xbbc: file /home/marco/projects/misc/zephyr/samples/basic/blinky/src/main.c, line 37.
(gdb) c
Continuing.

Breakpoint 3, main () at /home/marco/projects/misc/zephyr/samples/basic/blinky/src/main.c:26
26    {
(gdb) c
Continuing.

Breakpoint 4, main () at /home/marco/projects/misc/zephyr/samples/basic/blinky/src/main.c:37
37            cnt++;
(gdb) c
Continuing.

Program received signal SIGTRAP, Trace/breakpoint trap.
0xa05f0000 in ?? ()

Marco


Re: Using shell with RTT console on nRF52840 DK

Rodrigo Peixoto <rodrigopex@...>
 

Mike,
I have created the issue (#8394). I will try to start that.


Thank you,
Rodrigo Peixoto
Co-founder and Technical advisor

+55 (82) 98144-8585
http://ayna.tech | Skype: rodrigopex




Re: Using shell with RTT console on nRF52840 DK

Michael Rosen
 

Rodrigo,

 

Unfortunately, as RTT is just buffers in memory, there is no good way I can think of except to have a low priority background thread which polls the input channel using GetKey() and yields if negative (basically what WaitKey() does but with a yield). It might be a good idea to create an issue on github to track this request if you haven’t already.

 

Mike

 

From: Cufi, Carles [mailto:Carles.Cufi@...]
Sent: Thursday, June 14, 2018 7:02 AM
To: Rodrigo Peixoto <rodrigopex@...>; Rosen, Michael R <michael.r.rosen@...>; Chruściński, Krzysztof <Krzysztof.Chruscinski@...>
Cc: users@...
Subject: RE: [Zephyr-users] Using shell with RTT console on nRF52840 DK

 

Hi Rodrgo,

 

Krzysztof (on copy) is working on RTT and logging as well.

 

There’s this PR from him under review at the moment: https://github.com/zephyrproject-rtos/zephyr/pull/8110

 

Regards,

 

Carles

 

From: users@... <users@...> On Behalf Of Rodrigo Peixoto
Sent: 14 June 2018 15:58
To: Rosen, Michael R <michael.r.rosen@...>
Cc: users@...
Subject: Re: [Zephyr-users] Using shell with RTT console on nRF52840 DK

 

Mike,

 

I was taking a look at the uart_console and I couldn't any straight solution for RTT.

Uart has a device driver that enables us to use an ISR approach which is cool. There is no device driver for the SEGGER (at least, I could not find it), so the only thing I have in mind right now is to make a polling on the SEGGER_RTT_HasData function to see if there is data to be read from the host, if so write it to the input hook. For me, it seems to be a not so good solution. What do you think? Any other idea?

 

 

Best regards,

Rodrigo Peixoto

Co-founder and Technical advisor

 

+55 (82) 98144-8585

http://ayna.tech | Skype: rodrigopex

 

Image removed by sender.

 


Re: Need help on I2C burst write APIs

Carles Cufi
 

Hi there,

 

Not sure if it will solve your issue, but there is a Pull Request that rewrites the I2C implementation for nRF using Nordic’s official implementation (nrfx):

https://github.com/zephyrproject-rtos/zephyr/pull/7788

 

Carles

 

From: users@... <users@...> On Behalf Of dhguja@...
Sent: 14 June 2018 18:22
To: users@...
Subject: [Zephyr-users] Need help on I2C burst write APIs

 

Hello,
       I am using Zephyr 1.11 version and nRF52840 dev kit. I am trying to use I2C driver to communicate with a I2C device. 

My scenario is as below,

1) When i try to use i2c_burst_write API to send more than 1 byte, data is not issued to device after first byte.

2) i2c_burst_read API is working as expected. 

3) I went through the API definition code and found that burst write is split into two separate I2C transactions.

msg[0].buf = &start_addr;
msg[0].len = 1;
msg[0].flags = I2C_MSG_WRITE;

msg[1].buf = buf;
msg[1].len = num_bytes;
msg[1].flags = I2C_MSG_WRITE | I2C_MSG_STOP;

This separates the I2C interactions as 2 Tx msgs during burst write and data is not written beyond 1 byte.

I have attached the expected I2C burst write mode from my slave device data sheet. But when i analysed transactions using logic analyzer i saw transactions split into two I2C writes.

4) I also noticed that i2c_reg_read_byte uses i2c_burst_read underneath with 1 byte. But i2c_reg_write_byte uses i2c_write with combined address and data buffer. 

Not sure whether this behavior is expected or someone noticed this?

I can also use i2c_write directly to write more than 1 bytes with my device. But just curious if i am missing something while using those burst mode APIs.

Regards,
Dhananjay G J


Need help on I2C burst write APIs

dhguja@gmail.com
 

Hello,
       I am using Zephyr 1.11 version and nRF52840 dev kit. I am trying to use I2C driver to communicate with a I2C device. 

My scenario is as below,

1) When i try to use i2c_burst_write API to send more than 1 byte, data is not issued to device after first byte.

2) i2c_burst_read API is working as expected. 

3) I went through the API definition code and found that burst write is split into two separate I2C transactions.

msg[0].buf = &start_addr;
msg[0].len = 1;
msg[0].flags = I2C_MSG_WRITE;

msg[1].buf = buf;
msg[1].len = num_bytes;
msg[1].flags = I2C_MSG_WRITE | I2C_MSG_STOP;

This separates the I2C interactions as 2 Tx msgs during burst write and data is not written beyond 1 byte.

I have attached the expected I2C burst write mode from my slave device data sheet. But when i analysed transactions using logic analyzer i saw transactions split into two I2C writes.

4) I also noticed that i2c_reg_read_byte uses i2c_burst_read underneath with 1 byte. But i2c_reg_write_byte uses i2c_write with combined address and data buffer. 

Not sure whether this behavior is expected or someone noticed this?

I can also use i2c_write directly to write more than 1 bytes with my device. But just curious if i am missing something while using those burst mode APIs.

Regards,
Dhananjay G J



Re: k_sleep on mimxrt1050_evk board

Maureen Helm
 

Hi Marco,

Can you please try samples/basic/blinky or samples/synchronization? These samples should work on this board, but I’m currently traveling and don’t have hardware with me to check if they recently got broken.

 

Maureen

 

From: users@... [mailto:users@...] On Behalf Of Nashif, Anas
Sent: Thursday, June 14, 2018 4:29 AM
To: marco.hoefle@...; users@...
Subject: Re: [Zephyr-users] k_sleep on mimxrt1050_evk board

 

Marco,

Can you please open a bug with the information below?

 

https://github.com/zephyrproject-rtos/zephyr/issues/new

 

Thanks,

Anas

 

From: users@... [mailto:users@...] On Behalf Of marco.hoefle@...
Sent: Thursday, June 14, 2018 4:20 AM
To: users@...
Subject: Re: [Zephyr-users] k_sleep on mimxrt1050_evk board

 

I tried now to implement a sleep using the timer api, I think this is broken too.
Again, works on qemu port, doesn't on the mimxrt1050_evk

static void timer_expiry(struct k_timer *work)
{
    printk("timer expired!\n");
}


static void test_timer(void)
{
    k_timer_init(&timer_1, timer_expiry, NULL);
    k_timer_start(&timer_1, K_SECONDS(1), 0);
}


GDB:
(gdb) load /home/marco/projects/avnet/zephyr_demo/sw/build/mimxrt1050_evk/zephyr/zephyr.elf
Loading section text, size 0x4d2a lma 0x0
Loading section .ARM.exidx, size 0x8 lma 0x4d2c
Loading section devconfig, size 0x84 lma 0x4d34
Loading section rodata, size 0xa04 lma 0x4db8
Loading section datas, size 0x6c lma 0x57bc
Loading section initlevel, size 0x84 lma 0x5828
Loading section initshell, size 0x1c lma 0x58ac
Start address 0x32b4, load size 22726
Transfer rate: 88 KB/sec, 2066 bytes/write.
(gdb) break test_timer
Note: breakpoint 3 also set at pc 0xc3c.
Breakpoint 4 at 0xc3c: file /home/marco/projects/avnet/zephyr_demo/sw/src/main.c, line 84.
(gdb) del
Delete all breakpoints? (y or n) y
(gdb) break test_timer
Breakpoint 5 at 0xc3c: file /home/marco/projects/avnet/zephyr_demo/sw/src/main.c, line 84.
(gdb) c
Continuing.

Breakpoint 5, test_timer () at /home/marco/projects/avnet/zephyr_demo/sw/src/main.c:84
84    {
(gdb) c
Continuing.

Program received signal SIGTRAP, Trace/breakpoint trap.
0xa05f0000 in ?? ()
(gdb)


Re: Using shell with RTT console on nRF52840 DK

Carles Cufi
 

Hi Rodrgo,

 

Krzysztof (on copy) is working on RTT and logging as well.

 

There’s this PR from him under review at the moment: https://github.com/zephyrproject-rtos/zephyr/pull/8110

 

Regards,

 

Carles

 

From: users@... <users@...> On Behalf Of Rodrigo Peixoto
Sent: 14 June 2018 15:58
To: Rosen, Michael R <michael.r.rosen@...>
Cc: users@...
Subject: Re: [Zephyr-users] Using shell with RTT console on nRF52840 DK

 

Mike,

 

I was taking a look at the uart_console and I couldn't any straight solution for RTT.

Uart has a device driver that enables us to use an ISR approach which is cool. There is no device driver for the SEGGER (at least, I could not find it), so the only thing I have in mind right now is to make a polling on the SEGGER_RTT_HasData function to see if there is data to be read from the host, if so write it to the input hook. For me, it seems to be a not so good solution. What do you think? Any other idea?

 

 

Best regards,

Rodrigo Peixoto

Co-founder and Technical advisor

 

+55 (82) 98144-8585

http://ayna.tech | Skype: rodrigopex

 

 


Re: Using shell with RTT console on nRF52840 DK

Rodrigo Peixoto <rodrigopex@...>
 

Mike,

I was taking a look at the uart_console and I couldn't any straight solution for RTT.
Uart has a device driver that enables us to use an ISR approach which is cool. There is no device driver for the SEGGER (at least, I could not find it), so the only thing I have in mind right now is to make a polling on the SEGGER_RTT_HasData function to see if there is data to be read from the host, if so write it to the input hook. For me, it seems to be a not so good solution. What do you think? Any other idea?


Best regards,
Rodrigo Peixoto
Co-founder and Technical advisor

+55 (82) 98144-8585
http://ayna.tech | Skype: rodrigopex




Re: What is the process to enable bluetooth so that nrf52832 is disciverable by other device (android phone) #ble #bluetoothmesh #nrf52832

Chettimada, Vinayak Kariappa <vinayak.kariappa.chettimada@...>
 

Hi Rajat,

Please refer to Zephyr documentation: http://docs.zephyrproject.org/index.html

Bluetooth specific:

Bluetooth samples and their documentation can be found under: samples/bluetooth/*

For simple hands on, you can try the peripheral_hr and central_hr samples.

If there is something not mentioned in the documentations, please free to comment or contribute by sending a pull request.

Regards,
Vinayak


On 14 Jun 2018, at 12:44, Rajat Kalyan <rajatkalyan95@...> wrote:

Hey everyone

I have just started working on nrf52832 board. I want to enable the Bluetooth which is their on the board and set it to discoverable mode(if by default,its not)

I couldnot understand a bit of the sample bluetooth codes given.
Can anyone suggest me some procedure to enable the bluetooth and pair it with my mobile phone.

Thanks 


Re: Attempt to build an out-of-tree RTC driver

Kiril Zyapkov
 

So this is now #8379. Thanks!

On Thu, 14 Jun 2018 at 14:43, Kiril Zyapkov <kiril.zyapkov@gmail.com> wrote:

Hi all,

Newcomer here, trying to properly use the RTC hardware of an STM32Lxx chip.

I wasn't able to build my driver attempt out-of-tree. It requires
`RTC` and `USE_STM32_LL_RTC` to be selected. Selecting the `RTC`
option results in the following build failure:

CMake Error at zephyr/CMakeLists.txt:503 (message):
The Zephyr library 'drivers__rtc' was created without source files. Empty
(non-imported) libraries are not supported. Either make sure that the
library has the sources it should have, or make sure it is not created when
it has no source files.

The second symbol is a hidden one, and there are some problems with
setting it's default from an application Kconfig file. Here is a
bare-bones app which tries to set it, and succeeds:

https://github.com/kzyapkov/zephyr-set-hidden-option

However, if BOARD is set in environment instead of cmake the
USE_STM32_LL_RTC symbol is not selected.

Given those, I'll work on my driver in-tree, but I hope you can shed
some light on the issues. I saw #5554 which was rejected because
subsystems should be in the driver. However, it seems out-of-tree
drivers for existing subsystems are still not easily doable still.

Thanks,

Kiril



Attempt to build an out-of-tree RTC driver

Kiril Zyapkov
 

Hi all,

Newcomer here, trying to properly use the RTC hardware of an STM32Lxx chip.

I wasn't able to build my driver attempt out-of-tree. It requires
`RTC` and `USE_STM32_LL_RTC` to be selected. Selecting the `RTC`
option results in the following build failure:

CMake Error at zephyr/CMakeLists.txt:503 (message):
The Zephyr library 'drivers__rtc' was created without source files. Empty
(non-imported) libraries are not supported. Either make sure that the
library has the sources it should have, or make sure it is not created when
it has no source files.

The second symbol is a hidden one, and there are some problems with
setting it's default from an application Kconfig file. Here is a
bare-bones app which tries to set it, and succeeds:

https://github.com/kzyapkov/zephyr-set-hidden-option

However, if BOARD is set in environment instead of cmake the
USE_STM32_LL_RTC symbol is not selected.

Given those, I'll work on my driver in-tree, but I hope you can shed
some light on the issues. I saw #5554 which was rejected because
subsystems should be in the driver. However, it seems out-of-tree
drivers for existing subsystems are still not easily doable still.

Thanks,

Kiril

1741 - 1760 of 2659