Hi Felipe, Thanks for you support. I also used this style to take advantage of SoC built-in PWM module. But was not able to generate PWM with different pulse_width using same instance. Now it is possi

I'm not able to understand what you are saying. Is that means Zephyr PWM (fade_led example) is using software to generate PWM instead of separate dedicated SoC's internal PWM module ?

>> Again, I will like to iterate that for nRF52840, h/w PWM driver has to be used, feel free to contribute (isn’t it fun to develop than test ;) ) Means ?? I am using h/w PWM only !! Have you looked m

Hi Marti, >>Are you using the latest master? Yes

I took reference of $zephy/samples/samples/fade_led project & add following parameters in my prj.conf CONFIG_STDOUT_CONSOLE=y CONFIG_PRINTK=y CONFIG_PWM=y CONFIG_SYS_LOG=y CONFIG_SYS_LOG_PWM_LEVEL=4 C

Hello World !! I've added following lines in my project main () pwm_dev = device_get_binding(PWM_DRIVER); if (!pwm_dev) { printk("Cannot find %s! ", PWM_DRIVER); return; } while(1) { if(pwm_pin_set_us

Using #meshctl I gave following commands to BOARD_1 appkey-add 1 bind 0 1 1000 bind 0 1 1001 bind 0 1 1002 bind 0 1 1003 sub-add 0100 c000 1000 sub-add 0100 c001 1000 pub-set 0100 c000 1 0 5 1001 sub-

Using #meshctl I gave following commands to BOARD_1 appkey-add 1 bind 0 1 1000 bind 0 1 1001 bind 0 1 1002 bind 0 1 1003 sub-add 0100 c000 1000 sub-add 0100 c001 1000 pub-set 0100 c000 1 0 5 1001 sub-

Hello World !! What to do so that every fs_write( ) will save data on next new line ? Similarly what to do so that every fs_read() will read data from next new line ? Thank You !!

https://github.com/vikrant8051/zephyr-samples-boards-nrf52-nffs Are you want this ? Thank You !!

As per this document .... nrf5_SDK_for_Mesh_v1.0.1_src/doc/introduction/mesh_hw_resources.md (I've attached this file for reference......very informative) The mesh stack uses flash to store the follow

#bluetoothmesh

After testing I found that it is necessary to add __attribute__((packed)) after structure definationWhy ?? This will be helpful --> http://www.avabodh.com/cin/structure.html So I edit above mentioned

#bluetoothmesh

Hello World !! By including NFFS support into #BluetoothMesh project, now I can access flash of nRF52. { Some useful links: http://docs.zephyrproject.org/api/file_system.html https://lists.zephyrproje

#bluetoothmesh

I forgot to inform that, we have to add ext/fs/nffs/include into list of include directories. For that edit $zephyr_base/CMakeLists.txt as follow .... so it will looks like.. zephyr_include_directorie

Thanks Michael !! Now I can access flash of nRF52840 using NFFS file system APIs. I request Zephyr OS maintainer to create & add following attached main.c under $zephyr_base/samples/boards/nrf52/nffs/

Hello World !! https://devzone.nordicsemi.com/blogs/1235/nrf-blinky-compatible-firmware-using-zephyr-blueto/ I modified $zephyr_base/sample/bluetooth/peripheral/src/main.c as mentioned above. Using nR

fs_open( ) returns -19 instead of 0.

Hi Vinayak, it works !! I make following changes ..... fs_file_t my_zfp; unsigned char ptr[32]; for(cntr=0;cntr<=31;cntr++) { ptr[cntr]='@'; } fs_open(&my_zfp,"mesh.prv"); fs_write(&my_zfp,"0123456789

I copied & pasted $zephyr/ext/fs/nffs directory into $zephyr_base/include ---------------------------------------------------------------------------------------------------------------------- & edit

>> How provisioner will understand from where to received/read DEVICE >> public key out of *Bluetooth-Link* or *OOB* channel ? >I believe this is out of scope for the specification, since any OOB >cha

#bluetoothmesh