|
Re: Enable SPI driver on nrf52840
cpmcparland@...
Vinayak,
Thanks. I thought that the creation the driver source directories was only done at cmake time.... so that's where I was looking for a problem. Clearly I was wrong about that. Did just what you suggested using the arduino_101 board as target (that seems to be the example always used) and things worked as you desicribed. However all is not well yet with the nrf pca10056, so I have taken a page from your note and am trying again from a clean dist. I just cloned rc13 and am attempting to build the i2c_fujitsu_fram sample program. Sourced the appropriate zephyr_end.sh script. Created build/arduino_101 in the sample directory and executed cmake -DBOARD=arduino_101 ../.. All went well. Also issued make command and sample compiled and linked without a problem. NO changes to anything in the repo - just cmake and make. Then created a clean build/nrf52840_pca10056 directory in the sample directory and executed cmake -DBOARD=nrf52840_pca10056. NO changes to the repo - just create directories and executed cmake. REceived the following output and error: cmake -DBOARD=nrf52840_pca10056 ../.. -- Found PythonInterp: /usr/bin/python3 (found suitable version "3.5.3", minimum required is "3.4") -- Selected BOARD nrf52840_pca10056 Zephyr version: 1.13.0 Parsing Kconfig tree in /home/mcp/ZephyrProjects/zephyr_1.1.2/zephyr_latest/Kconfig Using /home/mcp/ZephyrProjects/zephyr_1.1.2/zephyr_latest/boards/arm/nrf52840_pca10056/nrf52840_pca10056_defconfig as base Merging /home/mcp/ZephyrProjects/zephyr_1.1.2/zephyr_latest/samples/drivers/i2c_fujitsu_fram/prj.conf -- Generating zephyr/include/generated/generated_dts_board.h -- Cache files will be written to: /home/mcp/.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 CMake Error at ../../../CMakeLists.txt:527 (message): The Zephyr library 'drivers__i2c' 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. -- Configuring incomplete, errors occurred! Any comments would be welcome. Also, thanks for posting the menuconfig issue...am following that closely. Regards, Chuck
|
|
|
|
[RFC] Thinking about extended poll support in Zephyr
Paul Sokolovsky
Hello,
Soon we'll need to wave bye-bye to the bloaty [1][2] k_poll(). I'm pondering about submitting a "k_epoll" RFC some time when 1.13 heat subsides, but just came by an article that Linux was adding yet another advanced poll feature: https://lwn.net/Articles/743714/ So, reading thru it (and not anything else), they're not too shy to go for complete "zero copy" by pushing poll results straight into the userspace memory. I personally don't think that it would affect plans for going to a well-known epoll design, but pushing results asynchronously into the userspace is also an interesting, if not brave, pattern we might keep in mind trying to optimize kernel/userspace split overheads. Btw, another point is that they not too shy to do following in the very bloated OS: One potential limitation built into this API is that there can onlyWe may revisit that too, to see what are real usecases to put the same object into multiple pollers (for a new implementation, I mean). [1] https://github.com/zephyrproject-rtos/zephyr/blob/master/include/kernel.h#L4411 [2] https://github.com/zephyrproject-rtos/zephyr/blob/master/subsys/net/lib/sockets/sockets.c#L687 -- Best Regards, Paul Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog
|
|
|
|
Re: nrf52840_pca10059 startup
Henrik Brix Andersen
Hi,
toggle quoted messageShow quoted text
I am not using the NRF52832 configuration on the NRF52840 SoC; I merely noted that I have successfully used the same programmer (Atmel-ICE) for interacting with NRF52832 SoCs. Yes, my application is samples/basic/blinky (and all other samples). I have tried the samples/bluetooth/peripheral sample; same issue. When I initially flash the sample it starts up and everything works as intended. If I then disconnect USB power and reconnect it, nothing starts up (BLE scanner does not show the peripheral anymore). A simple no-op SWD connection then does the trick; the application springs to life (without flashing a new binary). I have tried a few of the USB samples as well; none of them shows up as a device on the USB bus. Do you know if the original firmware binary (the one present on the device when shipping) for the PCA10059 is available anywhere? It could be interesting to see if that behaves correctly. Are you able to share your locally built zephyr.bin file for the blinky sample with me? Best regards, Brix -- Henrik Brix Andersen
On 27 Aug 2018, at 22.06, Chettimada, Vinayak Kariappa <vinayak.kariappa.chettimada@nordicsemi.no> wrote:
|
|
|
|
Re: nrf52840_pca10059 startup
Chettimada, Vinayak Kariappa
Something you mention about using NRF52832 configuration, why would you want to use that on nRF52840 SoC?
toggle quoted messageShow quoted text
You mention blinky as the example, is that the application you have trouble with? We tried that on our dongle, and see no issues. I have tried BLE peripheral sample and hci_usb sample on nRF52840 merely powered from nRF USB interface, and see no issues. Please confirm, that your application is samples/basic/blinky… also please try the samples/bluetooth/peripheral and let me know if you don’t see BLE advertising. Regards, Vinayak
On 27 Aug 2018, at 18:42, Henrik Brix Andersen <henrik@brixandersen.dk> wrote:
|
|
|
|
回复：回复：[Zephyr-devel] hciconfig tools error with nrf52832 running zephyr
icephyr
oh，sorry that I missed the dot.it is 4.1.15 actually
toggle quoted messageShow quoted text
发自我的华为手机 -------- 原始邮件 -------- 主题：Re: 回复：[Zephyr-devel] hciconfig tools error with nrf52832 running zephyr 发件人：Johan Hedberg 收件人：sxzxchen@... 抄送：Maureen Helm ,devel@...
Earlier you said it was 4.1.15. Which one was a typo? :)
|
|
|
|
Re: nrf52840_pca10059 startup
Henrik Brix Andersen
Hi Vinayak,
toggle quoted messageShow quoted text
Thank you for getting back to me. I just tried reverting commit 26d22b0075cf5a71f13958ec1f2727ac7167eca4, but it does not fix the application behaviour. Any other ideas are most welcome. Best regards, Brix -- Henrik Brix Andersen
On 27 Aug 2018, at 12.52, Chettimada, Vinayak Kariappa <vinayak.kariappa.chettimada@nordicsemi.no> wrote:
|
|
|
|
Re: 回复：[Zephyr-devel] hciconfig tools error with nrf52832 running zephyr
Earlier you said it was 4.1.15. Which one was a typo? :)
toggle quoted messageShow quoted text
Johan
On Tue, Aug 28, 2018, sxzxchen@163.com wrote:
imx6ull，with linux kernel version 4.15
|
|
|
|
回复：[Zephyr-devel] hciconfig tools error with nrf52832 running zephyr
icephyr
imx6ull，with linux kernel version 4.15
toggle quoted messageShow quoted text
发自我的华为手机 -------- 原始邮件 -------- 主题：Re: [Zephyr-devel] hciconfig tools error with nrf52832 running zephyr 发件人：Maureen Helm 收件人：sxzxchen@...,Johan Hedberg 抄送：devel@...
|
|
|
|
Re: hciconfig tools error with nrf52832 running zephyr
Maureen Helm
Which NXP device are you running embedded Linux? I can check to see if we have plans to update the kernel version.
From: devel@... <devel@...>
On Behalf Of sxzxchen@...
Sent: Monday, August 27, 2018 7:28 AM To: Johan Hedberg <johan.hedberg@...> Cc: devel@... Subject: Re: [Zephyr-devel] hciconfig tools error with nrf52832 running zephyr
Thanks for your explanation.since the embedded linux version is bound with the chip, I cannot update it easily.So is there any ways to solve this problem without updating linux version ?
>Hi,
>
>On Thu, Aug 23, 2018, sxzxchen@... wrote:
>> I bought a official nrf52832 development kits and ported zephyr
>> project successfully. It runs fine with my ubuntu host,via btattach
>> and btmgmt tools.But it didn't work with my nxp embedded linux,the
>> linux version is 4.1.15 and supports hciattach hciconfig tools
>> only.When I tried to bring the bluetooth module up with hciconfig hci0
>> up,an error comes up:
>
>The 4.1 kernel is too old to support controllers without a public
>address. IIRC you need at least a 4.4 kernel, but ideally something much
>newer than that.
>
>Johan
|
|
|
|
Re: hciconfig tools error with nrf52832 running zephyr
icephyr
Thanks for your explanation.since the embedded linux version is bound with the chip, I cannot update it easily.So is there any ways to solve this problem without updating linux version ?
|
|
|
|
Re: nrf52840_pca10059 startup
Chettimada, Vinayak Kariappa
Hi,
toggle quoted messageShow quoted text
I may have introduced a regression (bisected to) in 26d22b0075cf5a71f13958ec1f2727ac7167eca4
I notice that hci_usb sample fails to enumerate the bluetooth class device.
Will get back when I have something. Meanwhile, revert the above mentioned commit and do let me know if your application functions as expected.
Regards,
Vinayak
|
|
|
|
NRF52 : use of NFFS file system
Laurence Pasteau
Hi everybody,
I worked on a board including a NRF52 and use the file system with NFFS but I never succeed in using it correctly.
I have a lot of errors depending on the configuration parameters that I set. I reduce my problem to a little test that only writes in a loop 12 bytes in a single file. It fails very quickly. Sometimes the operation seems good when checking the return value. However the file became a file of size null and a new file with another name appears with the previous file. Then some loops later, there is an error in a return value of the write function.
I tried to modify NFFS configuration. In the two cases when the CONFIG_NFFS_FILESYSTEM_MAX_BLOCK_SIZE is higher and when the global size of the file system is higher ; the test is good during a longer time before failing. If I write 24 instead of 12 bytes or if I write in two files instead of one, the issue comes sooner.
I think something in my configuration (or in my software) is wrong. If someone can help me it would be very helpful.
Attached is the little test and the conf file. To reduce the time before failing, I change the file system size to 0x2000.
Here is my configuration (I don't use MCU_BOOT) :
In the dts file : partitions {
compatible = "fixed-partitions"; #address-cells = <1>; #size-cells = <1>; boot_partition: partition@0 { label = "mcuboot"; reg = <0x00000000 0xc000>; }; slot0_partition: partition@c000 { label = "image-0"; reg = <0x0000C000 0x32000>; }; slot1_partition: partition@3e000 { label = "image-1"; reg = <0x0003E000 0x32000>; }; scratch_partition: partition@70000 { label = "image-scratch"; reg = <0x00070000 0xa000>; }; #if defined(CONFIG_FS_FLASH_STORAGE_PARTITION) storage_partition: partition@7a000 { label = "storage"; reg = <0x0007a000 0x00002000>; }; #endif };
In the conf file : CONFIG_SOC_FLASH_NRF=y
CONFIG_FS_NFFS_NUM_BLOCKS=1024 CONFIG_FS_NFFS_NUM_INODES=1024 CONFIG_FS_NFFS_NUM_CACHE_BLOCKS=1 CONFIG_FS_NFFS_NUM_CACHE_INODES=1 CONFIG_FS_NFFS_NUM_DIRS=4 CONFIG_FS_NFFS_NUM_FILES=4 CONFIG_FS_NFFS_NUM_INODES=64 CONFIG_HEAP_MEM_POOL_SIZE=4096 CONFIG_MAIN_STACK_SIZE=4096 CONFIG_NFFS_FILESYSTEM_MAX_AREAS=12 CONFIG_NFFS_FILESYSTEM_MAX_BLOCK_SIZE=128 CONFIG_FS_FLASH_STORAGE_PARTITION=y CONFIG_SOC_FLASH_NRF_RADIO_SYNC=y In the CMakeLists.txt : set(BOARD nrf52_pca10040) target_include_directories(app PRIVATE $ENV{ZEPHYR_BASE}/ext/fs/nffs/include)
target_link_libraries(app NFFS)
Thanks in advance for any help.
Regards, Laurence
|
|
|
|
Re: nrf52840_pca10059 startup
Henrik Brix Andersen
Hi,
toggle quoted messageShow quoted text
I am flashing the board using an Atmel-ICE debugger (using pyOCD 0.11.2) connected to a 10-pin debug connector soldered to the P1 footprint on the bottom of the board. I am using the same configuration for several NRF52832 boards without issues. Best regards, Brix -- Henrik Brix Andersen
On 26 Aug 2018, at 19.01, Cufi, Carles <Carles.Cufi@nordicsemi.no> wrote:
|
|
|
|
Re: nrf52840_pca10059 startup
Carles Cufi
Hi there,
Can you tell us how you're flashing the board? Another Nordic Devkit, or a separate debug IC? Also copying Emanuele who's doing most of the work on this board. Regards, Carles On 26/08/2018, 18:07, "devel@lists.zephyrproject.org on behalf of Henrik Brix Andersen" <devel@lists.zephyrproject.org on behalf of henrik@brixandersen.dk> wrote: Hi, I have just acquired an NRF52840 Dongle (nrf52840_pca10059) and I am facing some difficulties with board startup. When I flash a zephyr binary to the board (e.g. samples/basic/blinky) the board starts up fine and starts the application. But when I disconnect the board from USB power and reconnect it, the application no longer starts (and the internal DC-DC converter does not seem to start-up either). If I run no-op pyOCD command (e.g. pyocd-flashtool -t nrf52840) the application springs to life (e.g. for blinky, the LED starts to blink). I am not using mcuboot or any other bootloader; just the bare-bone sample application. What am I missing here? Best regards, Brix -- Henrik Brix Andersen
|
|
|
|
nrf52840_pca10059 startup
Henrik Brix Andersen
Hi,
I have just acquired an NRF52840 Dongle (nrf52840_pca10059) and I am facing some difficulties with board startup. When I flash a zephyr binary to the board (e.g. samples/basic/blinky) the board starts up fine and starts the application. But when I disconnect the board from USB power and reconnect it, the application no longer starts (and the internal DC-DC converter does not seem to start-up either). If I run no-op pyOCD command (e.g. pyocd-flashtool -t nrf52840) the application springs to life (e.g. for blinky, the LED starts to blink). I am not using mcuboot or any other bootloader; just the bare-bone sample application. What am I missing here? Best regards, Brix -- Henrik Brix Andersen
|
|
|
|
Trying to add support for FRDM-KL28Z (nxp)
Lars Knudsen
Hi, I'm trying to add support for the FRDM-KL28Z board but realize, there seem to be missing support under /ext (where I see support for e.g. MKL25Z4). Would this need to be pulled from an NXP repo? br Lars
|
|
|
|
Re: [Zephyr-users] [Zephyr-devel] nRF52: USART: sending data from Serial terminal to DK
Chettimada, Vinayak Kariappa
Why don’t you use tests/bluetooth/mesh_shell ? and add your commands?
toggle quoted messageShow quoted text
Johan may be of assistance.
|
|
|
|
Re: Applying TDD to an IP stack issue
Oleg Zhurakivskyy
Hello Paul,
On 08/23/2018 01:29 PM, Paul Sokolovsky wrote: The simplest test would be as follows: it should be an active close,Thanks for the input. Currenly the TCP suite is very simple and doesn't have a capability to initiate events on a peer's side of TCP connection. I am planning to add such capability and will try to implement such a test. Regards, Oleg
|
|
|
|
Re: [Zephyr-users] [Zephyr-devel] nRF52: USART: sending data from Serial terminal to DK
vikrant8051 <vikrant8051@...>
Hi Vinayak, My sim is to create commands & send it to PDK where PDK process
them & help onboard #BluetoothMesh clients to create data packets. Currently using thread triggered by button interrupt to send Bluetooth Mesh Client mesaages like Gen_OnOff_Set/ Gen_OnOff_Set_Unack/Gen_Level_Set/Gen_Level_Set_Unack Thank You !!
On Fri, Aug 24, 2018 at 4:32 PM Chettimada, Vinayak Kariappa <vinayak.kariappa.chettimada@...> wrote:
|
|
|
|
Re: [Zephyr-users] [Zephyr-devel] nRF52: USART: sending data from Serial terminal to DK
Chettimada, Vinayak Kariappa
if you are looking for a shell, tests/bluetooth/shell could be your inspiration.
toggle quoted messageShow quoted text
if you are looking for implementing a transport over uart, then samples/bluetooth/hci_uart could be your inspiration.
other samples and subsystems may be using UART, that could also be close to your needs. Hoping the UART API documentation in Zephyr should suffice your requirements and how to use it.
-Vinayak
|
|
|