users@lists.zephyrproject.org

mcuboot for nrf52840_pca10059

Hi, I am trying to compile mcuboot (latest version from git) with zephyr v1.14.0-rc3. I am getting this error: mcuboot/boot/boot_serial/src/boot_serial.c:36:10: fatal error:

By Venkat Rao Vallapaneni <vallapaneni@...> · #1394 ·

Re: BT Mesh Health Server FaultPeriodicPublication#bluetoothmesh #zephyrbluetoothmesh

Hi Billy, Actually, I think I missed the fact in the earlier emails that this was specifically about the health server and not just any model publishing. The health server is a special case and does

By Johan Hedberg · #1393 ·

Re: NXP RT1064 board and JLink Debugging

Continuing: I Installed the LPCScript utilities on both Ubuntu, and Windows from

By Lawrence King · #1392 ·

Re: BT Mesh Health Server FaultPeriodicPublication#bluetoothmesh #zephyrbluetoothmesh

I have looked into the health_svr.h and found that the “helper” does not have an update callback. Maybe in might be worth adding to allow periodic updates. I will change my app to use the generic

By William Fish · #1391 ·

Re: BT Mesh Health Server Fault PeriodicPublication#bluetoothmesh #zephyrbluetoothmesh

Johan, Fantastic, thanks. I am using the BT_SETTINGS and calling settings_load(). I use this as a short cut for development purposes. The Update callback well spotted many thanks. The lack of

By William Fish · #1390 ·

Re: BT Mesh Health Server Fault Periodic Publication#bluetoothmesh #zephyrbluetoothmesh

Hi Billy, (added zephyr-users back to CC - please don’t drop it since others may benefit from this information as well) There are a many problems with the above: 1. The model publication is

By Johan Hedberg · #1389 ·

Re: BT Mesh Health Server Fault Periodic Publication #zephyrbluetoothmesh #bluetoothmesh

Hi Billy, It should be working even with a single fault, and this has e.g. been tested with the PTS which does configure periodic publishing during some of its test cases. Is your source code

By Johan Hedberg · #1388 ·

BT Mesh Health Server Fault Periodic Publication #zephyrbluetoothmesh #bluetoothmesh

Hi All, Have a unusual issue i cant get to the bottom of, I am attempting to implement a Mesh Health Server yet I seem to have come across some odd behaviour. If i set a publication period for the

By William Fish · #1387 ·

Re: BlueZ PHY CODED scan via HCI UART on nRF52840_pca10056 #ble #nrf52840 #uart #hci

Is there anything else I could check to make it work?

By Piotr Barszczewski <piotr@...> · #1386 ·

Re: NXP RT1064 board and JLink Debugging

Well I have made progress resolving this problem. (but not resolved) It turns out the that LPC4322 chip on the RT1064 board has two sets of firmware in it. 1) the DAPLINK firmware, and 2)

By Lawrence King · #1385 ·

Re: onoff-app board sample not working #bluetoothmesh #nrf52832

Hi Alexander, I don’t know if this is the cause of your issue, but it implies that you have something in flash (the storage partition) that the application doesn’t expect. Before investigating

By Johan Hedberg · #1384 ·

onoff-app board sample not working #bluetoothmesh #nrf52832

Trying to get the Bluetooth mesh onoff-app sample working on a nrf52_pca10040 it compiles and runs on the board but when it try to provision it using the meshctl tool it freezes and I cant type after

By alexander.2003@... · #1383 ·

Re: NXP RT1064 board and JLink Debugging

Hi Maureen: Actually I don’t think mcuxpresso is using JLink, however during the install, mcuxpresso did remove JLink 6.44 and install JLink 6.42. I suspect this is due to the fact that the ide

By Lawrence King · #1382 ·

Re: NXP RT1064 board and JLink Debugging

Hi Lawrence, You’re right, I forgot that RT1064-EVK has a different onboard debug circuit than RT1050-EVK. Do you have an external JLink probe you can use? Are you sure you’re using the JLink

By Maureen Helm · #1381 ·

Re: BlueZ PHY CODED scan via HCI UART on nRF52840_pca10056 #ble #nrf52840 #uart #hci

There's a "Group Reply" button in the bottom right-corner. It took me while to find because you can see it only *after* clicking "Reply", that's an unusual interface.

By Marc Herbert · #1380 ·

Re: BlueZ PHY CODED scan via HCI UART on nRF52840_pca10056 #ble #nrf52840 #uart #hci

Hello Johan, Thank you for your response. Following your suggestion I've updated my kernel to 4.20 and there is a change in behavior though I don't see LE CODED scanning to be working + btmgmt

By piotr@... · #1379 · Edited

Re: BlueZ PHY CODED scan via HCI UART on nRF52840_pca10056 #ble #nrf52840 #uart #hci

Hi, HCI_Read_Local_Extended_Features is a BR/EDR-only command, which is why you are getting this response from the LE-only controller. You’ll also see that it’s not listed in the supported

By Johan Hedberg · #1378 ·

Re: BlueZ PHY CODED scan via HCI UART on nRF52840_pca10056 #ble #nrf52840 #uart #hci

Hi, Notice that these are MGMT commands and events, i.e. just communication between BlueZ user space and the Linux kernel and not directly related to the controller. The Set PHY Configuration MGMT

By Johan Hedberg · #1377 ·

Re: NXP RT1064 board and JLink Debugging

Hi Maureen: Yes, I added the two configs, and I am only trying “ninja debug”. I did try using OpenSDA fromhttps://www.segger.com/downloads/jlink/OpenSDA_V2_1 unfortunately it will not load

By Lawrence King · #1376 ·

Re: NXP RT1064 board and JLink Debugging

Hi Lawrence, You have to use JLink firmware to use the JLink GDB server. “lpc4322__mimxrt1064_evk_if_crc_20180810.bin” is DAPLink firmware, not JLink firmware.

By Maureen Helm · #1375 ·

Messages