Hi Vinayak,

On Thu, 2017-09-14 at 19:14 +0000, Chettimada, Vinayak Kariappa wrote:

Hi Steve,

Yes, we (for myself) are listening ;-)

You say beacon hex flashed to ble nano2 works (advertises).

1. Does hello world sample work (print out on UART)?
2. Does the samples/basic/blinky  work (flash LED) ?

Lets proceed with these.

Regards,
Vinayak

On 14 Sep 2017, at 21:03, Steve Brown <sbrown@...> wrote:

Ricardo,

On Thu, 2017-09-14 at 14:49 -0300, Ricardo Salveti de Araujo wrote:

On Thu, Sep 14, 2017 at 5:53 AM, Steve Brown <sbrown@...

wrote:

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.

By works as expected you mean including the BT radio?

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.

Yeah, this looks like an issue in the firmware flashed in
LPC11U35.
Talking with Seeeds, it seems they originally flashed
https://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.

Cheers,

Thanks for the info on the CMSIS firmware. I'm not using it, but
thought that it might be connected to my radio problem. From your
comments, it's not.

pyocd-flashtool flashes the device with the expected console
output.
The radio doesn't work.

I've ordered another 2 from Digikey and will see how they behave.
When
I ordered them from Seeed, I never thought to check if they were
available locally.

I wonder if they got zapped during customs inspection. They
probably x-
ray the small boxes. I hope the customs inspector wears a film
badge.
If anybody from Nordic is listening, maybe they have an opinion.

Steve


_______________________________________________
Zephyr-users mailing list
Zephyr-users@...
https://lists.zephyrproject.org/mailman/listinfo/zephyr-users

Hello and blinky work. BT does not.

And, yes nitrogen_beacon.hex from http://builds.96boards.org/releases/n
itrogen/zephyr-1.8/ flashed to the nano2 advertises. There's no console
output as I explained previously.

I'm now more convinced that the devices somehow got damaged in transit
from Seeed.

I'll report when I get the ones I ordered from Digikey. I expect them
to work just fine.

If you are curious about what happened to the radios, I'd be glad to
send you the 2 I got from Seeed.

The shipment didn't seem to have been opened. I'm pretty ESD conscious
at my end.

Steve