Search results for:

Thank you guys for the quick replies, and sorry for posting it here. Thought it would be easier to just use an existing 52840 built than create it new. Building my own is tough for me as I really don't have a single clue what I am doing. I already see myself in installing loads of depencies that I will surely never need again and "fixing" problems by googeling and hacking things apart instead of doing it right. Your hint to remove "this line" is best example: what is this and why should I remove it?! There is simply a difference between a user and a developer.
I will try to get STLink working with the bin files available.

Is there a way to convert the available files to hex to flash them using STLink? I bought a chinese nrf52840 (E73 from ebyte) and would like to try Bangle's firmware. I have already successfully flashed this one, but it is obviously a little old and missing some functions ...

I have tried this one on 52840 devices (E73 from Ebyte), it works at first. But when changing advertising later (by timer) it falls back into advertising as "UART" instead – strangely because it was never named like this. Maybe a default setting. All other options (interval, connection, ...) seem to be accurate.

Thank you!

When I use setTimeout to regularly change the BLE advertising (once a day or so), it will surely increase power consumption a bit. But will it lead to the interpreter running permanently wasting power or will it use (deep)sleep to minimise consumption? I have read here that nRF52 boards sleep automatically ...?

Thank you Gordon, looks good now. Some device scanner just don't seem to update their data correctly, even if restarted. "nRF Connect" works best.

Yes, my twice-setting of advertising didn't work, somehow it looked like it would.

Aha – I think I have found a solution, at least it looks better now. I set the name first and adv after it. They don't seem to overwrite eachother:

NRF.setAdvertising({}, {interval:1500,name:ble_name,showName:true,discoverable:true,connectable:false,scannable:true});
NRF.setAdvertising(adv, {});

Thank you for the hint ... so I have changed it to

const adv = [ 0x1e, 0xff, 0x4c, 0x00, 0x12, 0x19, 0x00, key[6], key[7], key[8], key[9], key[10], key[11], key[12], key[13], key[14], key[15], key[16], key[17], key[18], key[19], key[20], key[21], key[22], key[23], key[24], key[25], key[26], key[27], key[0] >> 6, 0x00, {}];
NRF.setAdvertising(adv, {interval:1500,name:ble_name,showName:true,discoverable:true,connectable:false,scannable:true});

Although there is no error or message the device seems to fall back so I can connect via IDE ... it does not advertise like I want it to. I am a little out of ideas now.

Thank you @fanoush!

I just want the device to advertise like here ... working as an "AirTag". From what I understand this code not really loops it just sets the device in advertising mode. How much will it consume? Is there something I can disable to even lower the consumption?

Ah, I see it sometimes takes very long for scanning apps to recognise the change of the name. The IDE is fastest mostly. Even when I restart Puck (battery out). Is that an issue of the scanning app (device) or am I missing something?

Excuse me for waking this up ... I would like to name my Puck, but this doesn't seem to work:

NRF.setAdvertising(adv, {interval:2000,name:"Bunny",showName:true});

What's wrong with it?
"adv" is an array of values similar to the one used by OpenHaystack.

Thank you very much! :-)

Me again, I have tried setting the module (flashed with old hex before) in DFU mode by submitting

E.setFlags({unsafeFlash:1});
var f=require("Flash");
f.erasePage(0x7f000);
E.reboot();

But the IDE was unable to find a device in DFU mode. So this didn't seem to work.
I then tried the VDD->D0 option and couldn't get it to work: neither IDE nor nRF-Connect see the device in DFU mode.

Another thing I have noticed: I have uploaded a script to let the device advertise like a OpenHaystack beacon – works good until I power it off and on: the device falls back into "Espruino mode" no matter if uploaded to RAM or Flash.

Can it be that the old hex does not work the way Espruinos work today?

Thank you, I am not able to build this myself. But I understand if there is no need if nobody is using it anyway. And I have already tried flashing it over bluetooth, didn't work, but I'll try again tomorrow.

This one

Perfect, thanks alot!

I see here that the .hex for the Nordic is very old. Could someone update this to a newer version? Please?

Yes, I did, beautiful!
:-)

Ha! Now it worked! Must have been a weird shortage on the back due to my soldering ... man, this thing is tiny. Thank you both for assisting!

Thank you both, I understand the shortage sounds plausible, but I am very sure there is no connection between D0 and GND. After connecting battery (LFP having 3.24v) I disconnect the lower right red clamp. A zoomed image shows that the upper clamp only touches D0.
Maybe the voltage is too high for D0?

I have tried again and again ... doesn't seem to work. I see the module in the scanner app showing up as MDBT42Q, when I connect D0 it gets offline and returns as soon as I disconnect D0. So I believe the connecting works, powering as well, otherwise it wouldn't show up at all. Very annoying.
I'll try to attach an LED.

I am having a hard time getting this thing into DFU mode. Meanwhile I have connected / disconnected power and D0 many times I don't even know in what state it is now. The device is showing up in nRF Scanner as MDBT42Q.

Just to make sure: do I have to connect all GND to minus of the battery or just one?

This is how I have it now: GND is connected to the upper left pin. D0 is connected to VDD.
I then connect power to VDD and right after that disconnect D0.
That's correct, isn't it?

of course, thank you