On Thu, Sep 14, 2017 at 5:53 AM, Steve Brown <email@example.com> wrote:
On Thu, 2017-09-14 at 01:47 -0300, Ricardo Salveti de Araujo wrote:
On Wed, Sep 13, 2017 at 6:37 PM, Steve Brown <firstname.lastname@example.org>The boards are:
Has anyone had success with samples/bluetooth/beacon on thisIt is supposed to just work, without any additional changes, so
Even the nitrogen_beacon.hex file from 96boards.org won't transmit.
console messages are as expected, but nothing on the air. Same
on two recent boards from Seeed.
The same .hex file flashed to a redbear ble nano2 does transmit.
is no console output because a different uart is used, but the
are on the air.
The designation on the nRF52 is N52832/QFAAB0/1616BD. I looked at
errata and didn't see anything obvious.
if this could be hw issues.
Can you check the hw revision for your Nitrogens (should be either
v0.9, v1.0 or v1.1)?
I got several from v0.9 and v1.1 and they are all functional. Just
tested the beacon sample from Zephyr 1.9 and it is working just fine.
v1.0 build date 09/19/2016
v1.1 build date 02/16/2017
The nitrogen build uses pyOCD to flash the device. This works as
By works as expected you mean including the BT radio?
However, copying a .bin file to /media/$USER/MBED gives the
"The interface firmware FAILED to parse the hex file" in FAIL.TXT
If I copy a .hex file to the MBED disk, it isn't processed and the file
remains in the folder.
Both boards exhibit identical behavior.
Yeah, this looks like an issue in the firmware flashed in LPC11U35.
Talking with Seeeds, it seems they originally flashedhttps://github.com/xiongyihui/CMSIS-DAP/tree/arch_ble
, but I didn't
yet investigate to see why this is currently broken. Maybe it assumes
the user will flash softdevice compatible fw by default, not sure.