Re: 96boards Nitrogen


Steve Brown
 

Richardo,

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 <sbrown@cortland.com>
wrote:
Has anyone had success with samples/bluetooth/beacon on this
device?

Even the nitrogen_beacon.hex file from 96boards.org won't transmit.
The
console messages are as expected, but nothing on the air. Same
results
on two recent boards from Seeed.

The same .hex file flashed to a redbear ble nano2 does transmit.
There
is no console output because a different uart is used, but the
beacons
are on the air.

The designation on the nRF52 is N52832/QFAAB0/1616BD. I looked at
the
errata and didn't see anything obvious.
It is supposed to just work, without any additional changes, so
wonder
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.

Cheers,
The boards are:
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
expected. However, copying a .bin file to /media/$USER/MBED gives the
following error:
"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.

By comparison, copying either a .bin or .hex to the CMSIS disk on my
blenano2 works as expected.

I agree it looks like a hardware problem, but on two different rev
boards?

Is the drag/drop CMSIS interface known to work?

Thanks,

Steve

Join users@lists.zephyrproject.org to automatically receive all group messages.