-
• #2
@Robin, I'm surprised seeing you using Espruion Web IDE for updating MDBT42Q based Espruino! How could I have missed that this is now released / available... Documentation at http://www.espruino.com/Puck.js#firmware-updates still requires you to use the same process as from the very beginning...
The only common thing across all boards is the reset: power on with button pressed.
That it fails is - I assume - that a different boot loader is used than the other Espruino boards (chips) do.
-
Thanks for responsding @allObjects
'How could I have missed that this is now released / available...'
Are you being factitious here?
There is more confusion added as others were trying also, as the firmware is accessible in the download list with the native app. Also confusing is the native app is title Espruino WEB IDE
Did I misunderstand this comment then? *(posts 7 thru 10)
ref#9 http://forum.espruino.com/conversations/338136/#14936620
-
• #4
The context makes it clear. Still same process as documented at http://www.espruino.com/Puck.js#firmware-updates.
There may be other native apps or chrome things available that do the DFUing - other than the above mentioned links mentions... but for sure not the Espruino Web IDE (for programming).
That
the firmware is accessible in the download list
means only: this are the different builds of the firmware.
If it talks and walks like a duck...
That is too fuzzy... like a duck chicks actually are.
Every A is a B, but not every B is an A. A corollary in Object-Oriented programming when it is about classes and inheritance.
-
'but for sure not the Espruino Web IDE (for programming)'
Then the option for performing the install for nRF devices needs to be removed . . . .
re: 'the firmware is accessible in the download list'
(as the WebIDE flash option self detects and enables the ability to start the flash process)I wont be the only one that falls into this trap!
Just installed nRF-Connect, we'll try that first. . . .
1 Attachment
-
-
• #6
the install for nRF devices needs to be removed
Not really...
As the NOTE 'right there' -
* IN BOLD AND ALL CAPS *- says:
1 Attachment
-
-
Ahhh, but I followed the instruction:
"Normal Firmware Update"
"Just click the button below and follow the on-screen instructions."re: 'Not really...'
Why provide the trap at all? Any beginner will follow the same instruction for 'Normal' as did I.
nRF-Connect doesn't recognize the device either.So, . . .
Tried online Web Bluetooth Secure DFU from post #9 from link in post #1 above
but don't even make it as far (32768 bytes) as @AkosLukacs did (270336) in post #10 same link
Might be relevant 32768 == 0x8000
From Chrome console when stalled: DOMExceptionfound DFU service web.html:140 found 2 characteristic(s) web.html:140 found packet characteristic web.html:140 found control characteristic web.html:140 enabled control notifications web.html:140 transferring init web.html:140 init packet already available, skipping transfer web.html:140 transferring firmware web.html:140 written 32768 bytes web.html:1 Uncaught (in promise) DOMException
1 Attachment
-
-
Hi Robin,
as @allObjects say, only „nRF-Connect“ will to the job.
Used it many times with ios and android phones without any problems.
-
Or try this desktop version
https://www.nordicsemi.com/Software-and-Tools/Development-Tools/nRF-Connect-for-desktop
-
Thanks @MaBe
Upgraded from v2.4.0 to V3.2.0 using your link. But still doesn't recognize the MDBT42Q. Tried both just powering up, the one second button release and the five second hard reset.
I suppose a reboot of Windows10 might be the next step. Don't have iOS or a smart phone to try the android version.
EDIT:
Just tried on the old laptop with a BLE dongle, that hadn't lost pairing, but get the same stalled progress as in #7 image.And, same error 'Windows Web Bluetooth is broken in <68' when using the native WebIDE to just connect:
Loaded code from storage. GET chrome.storage.local.OFFLINE_DATA = 0 bytes Web Bluetooth available, but Windows Web Bluetooth is broken in <68 - not using it >>> Connecting... Set Slow Write = true ERROR: Unable to open device (connectionInfo=undefined) ERROR: [notify_error] Connection Failed. >>> Connection Failed.
1 Attachment
-
-
The following was attempted using a TTL converter with Tx->Rx and Rx->Tx per:
and connect using a Com port rather than Bluetooth.
Used the old standby laptop with the BLE dongle with pairing still in tact.
Tried the web launch from page link from:Initialising Tour Initialising SettingsProfile Initialising HelpLinks Initialising Offline Initialising CoreModules No code in storage. GET chrome.storage.local.OFFLINE_DATA = 0 bytes Handling URL "http://www.espruino.com/webide" >>> Connecting... Set Slow Write = true Unable to open device (connectionInfo=undefined) ERROR: Unable to open device (connectionInfo=undefined) ERROR: [notify_error] Connection Failed. >>> Connection Failed.Back to the native WebIDE app using the TTL converter and Com port
Initialising Tour Initialising SettingsProfile Initialising HelpLinks Initialising Offline Loaded code from storage. GET chrome.storage.local.OFFLINE_DATA = 0 bytes Web Bluetooth available, but Windows Web Bluetooth is broken in <68 - not using it >>> Connecting... Set Slow Write = true Unable to open device (connectionInfo=undefined) ERROR: Unable to open device (connectionInfo=undefined) ERROR: [notify_error] Connection Failed. >>> Connection Failed.
So it appears the inability to complete the flash process (using DFU) prevents the existing corrupted (previous) flashed version from being accessible. Again tried a hard reset also. Device still unusable. -
What you may have ended up by using STM / Espruino boot loader based firmware updater on the nrf5x / Raytec based boot loader device is a bricked BLE connectivity.
Btw, for the com port connection to work correctly as by Espruino doc, you still need to have a working Espruino REPL on your device... And even if it (would still) work/s, you still cannot update Espruino BLE Espruino device via Espruino IDE...
To get your device back in working BLE boot loader mode / sw update OTA, you may need to walk the path of Recover from a bricked nrf52 device . Check these links as a 'boot strap links' to all the details you need to consider:
- How to recover bricked nRF52832 with ST Link? - https://devzone.nordicsemi.com/f/nordic-q-a/22886/how-to-recover-bricked-nrf52832-with-st-link
- Custom board bricked - https://devzone.nordicsemi.com/f/nordic-q-a/1700/custom-board-bricked
Take also a look at http://www.espruino.com/datasheets/nRF52832_PS_v1.0.pdf - p. 70+. 16 Debug and trace / 16.2 16.2 CTRL-AP - Control Access Port
- How to recover bricked nRF52832 with ST Link? - https://devzone.nordicsemi.com/f/nordic-q-a/22886/how-to-recover-bricked-nrf52832-with-st-link
-
This was all explained in this thread which you were involved in, but I'll point it all out here to be totally clear:
- It seems Web Bluetooth updates don't work for Windows, either via the browser or Native IDE - I believe they did at some point in the past, but not now.
- Web Bluetooth updates do work on Linux, Mac, Android and Chromebook
- Pairing in Windows has no effect. The bootloader's BLE name is 'DfuTarg' so you won't expect to see it in the normal IDE's connection options.
- Yes, the option should be disabled in Windows - however none of the instructions for firmware updates instruct you to use the Web IDE. Everything is open source so you are willing to contribute a change for this if it bothers you. edit: I have now disabled Web Bluetooth updates for windows
- The bootloader is fine, your board is not bricked. You just need to re-flash the firmware successfully.
- There is no UART bootloader. You have to update via Bluetooth LE
- By far the easiest option is to follow the instructions on http://www.espruino.com/Puck.js#firmware-updates with an Android or iOS phone or tablet
I understand that you don't have a smartphone. Do you have a tablet? Do you know anyone with a smartphone that you can borrow?
I'm pretty sure this has come up previously and you did manage to update firmware on Puck or a Pixl. What did you do then?
- It seems Web Bluetooth updates don't work for Windows, either via the browser or Native IDE - I believe they did at some point in the past, but not now.
-
@Gordon, does Web Bluetooth work running in a Linux - such as Ubuntu - as guest in virtual box vm on a windows host, such as @Robin may have?
If so, this is really an easy setup... and the few megs/gigs such an environment requires are usually (still) available. Setting up c:/ root as shared folder gives access to all files to from within Ubuntu. Virtual box and Ubuntu are free and easy to use.
-
does Web Bluetooth work running in a Linux - such as Ubuntu - as guest in virtual box vm
Oof. Maybe, but I wouldn't hold out high hopes. If you're going to do that I'd either:
- Use a Raspberry Pi
- Install Ubuntu on a USB stick (super easy), reboot into it, and use Chromium/Chrome web browser on there to do the update
Or in the UK you can buy Android mobile phones good enough for flashing brand new for around £30, so I doubt they'd be more than $40 in the US - even less if you go second hand.
- Use a Raspberry Pi
-
Thr 2019.11.28
' work for Windows, either via the browser or Native IDE - I believe they did at some point in the past, but not now.'
Yep. I used the Windows version ~nine months ago to upgrade the same MDBT42Q. Totally surprised when it failed this time.
'Do you have a tablet?'
Yes, but even with side-loading still doesn't recognize the device. It is three years old, so maybe BLE wasn't totally supported then.
'good enough for flashing brand new for around £30, so I doubt they'd be more than $40 in the US - even less if you go second hand.'
Had considered that option, but . . . , it isn't the cost of the hardware that is the issue, it's the connection plan. Even with a basic one month no commitment accessible discount card, still puts that ~$40 and the hardware ~$40 at a cost to flash one existing board that exceeds purchasing two new MDBT42Q breakout boards direct!
'Do you know anyone with a smartphone that you can borrow?'
'What did you do then?'It was with a Puck and had to wait until a Holiday when an individual willing to d/l to their device was in town. Amazing how protective individuals are when (even offering a stipend) asking to download an unknown app to program my device on to their phone. In any event, friend in town and got it done with an Apple iPhone. Incidentally, moving the zip file into the workspace of the nRF_toolbox app for the 'choose Distribution Packet' step was an absolute nightmare. Convinced, I'll never need/use (for the monthly fee required) a smart phone for daily use, . . . Espruino testing/ connectivity, maybe.
Gotta go, there's an eighteen pound turkey waiting to be devoured . . . .
-
...no plan needed for a smart phone... if Wifi enabled and connected to a Wfi LAN, there you go.
-
Sat 2019.11.30
'if Wifi enabled and connected to a Wfi LAN, there you go.'
A bit puzzled @allObjects, as the MDBT42Q breakout board is not a WiFi device. Also the detailed instructions under 'Firmware Update' specifically state "On your Bluetooth LE capable phone."
Was the intent to use the WebIDE? No, as that #1 is what caused this headache in the first place a month ago. Not grasping the 'WiFi' solution through all the 'BLE' fog. ;-)
-
...nothing to be puzzled about: the phone gets you BLE AND Wifi: BLE to talk to the Espruino BLE boards and Wifi to go to the internet or your local Wifi LAN. With Wifi you get www and your locally connected computers. With that you get what you need from there and them, such as the flashing software and the flash images / binaries / etc... You don't even need to create a (S)FTP or Web server on your computer. Push comes to shove, email does it (most of the time if email provider is not shooting you in the foot because of data / intrusion security).
The phone was born as airtime voice phone only - but that's a while ago. Today, many apps now also use voice over IP, even the phones Phone app itself, and apps suich as What's up. Being connected to a Wifi (hotspot) LAN (that allows that), no need to have a phone (air and data) plan.
Not grasping the 'WiFi' solution through all the 'BLE' fog.
...neither did most of the classic computers and operating systems... until recently. The phones got it first, that's why they supported upload / flash tools first...
But: Well... I may be fogged as well... or not-so-well... weather has changed out here in the West since the holiday season began. Clear and blue is gone...
-
I have had luck side-loading .apk files from Windows to an Android tablet, so I gather the concept for both the install of nRF-Toolkit.exe and espruinoxxxxx.zip would be similar? e.g. use the desktop to acquire both those files over the Internet, and through magic I've yet to discover, beam those files to the smart phone, (won't be eMail as WiFi would be needed, e.g. a plan - micro USB perhaps?) and then perform the install, move the .zip into that apps file space and re-flash at that point? It would be much nicer to have the WebIDE Windows option active again.
Correct me if my understanding is flawed, but doesn't the WiFi use of a smart phone require a SIM card, and now I recall there are low cost SIM options there also. I've heard other's purchasing second hand smart phones off eBay, but then get stung with the SIM card issue. The generic SIM cards at Target are ~$20, last time (months ago) I checked, piggy-backed on a plan, month-to-month being the shortest. If a SIM card is required, then might as well fetch directly and bypass the PC. Still not convinced what is outlined in pp.1 post #20 will work (micro USB maybe) without activating the smart phone.
-
Hey, if you have a tablet, that most likely has BLE too.
AFAIK, you don't need a SIM card to use wifi at all. You can use your wifi connection to perform all the smartphone-y things like installing apps from app-store and download emails. -
Sun 2019.12.01
'if you have a tablet, that most likely has BLE too'
Answered that in second sentence in post #17 Three year old device recognizes PC but doesn't recognize BLE devices.
'AFAIK, you don't need a SIM card to use wifi'
Isn't the SIM card integral in allowing/exposing the MAC address in order to comm with other devices via any means? I was under the impression that mfg's protected their products this way.
-
Ah, ok, forgot about #17...
My phone has different bluetooth and Wifi MAC addresses, different IP address when on mobile and on wifi. Those are independent.
On power up it asks for SIM PIN, to prevent unauthorized access. But with a wifi only tablet, you don't have a SIM card at all, and can still use wifi.
allObjects
MaBe
Gordon
AkosLukacs-
Post a reply
About
Unable to flash MDBT42Q with either Native WebIDE or Chrome - board now locked and unusable [SOLVED #13 post]
Posted by
@Robin
Sat 2019.10.26
Was in the process of attempting to resolve an issue for another forum post and needed to
flash to current version.
Didn't want to hijack the following as I'm not flashing a Puck, but this may be related as it appears still unresolved. (three weeks now without update)
Puck.js failed to update firmware; can't hard reset now
Still get the stuck uploading green bar, but an additional error using the native app.
Entering bootloader mode releasing button after one second and view red LED is illuminated
First attempt using WebIDE native app v0.70.06
Note that the device was found blue and then connected green
TypeError: failed to execute 'requestDevice' on 'Bluetooth' required member filters is undefined.
Needed to close IDE, unpair device, then 'Add a Device' then pair then relaunch IDE. That worked great
until I tried the Chrome version. Then device becomes locked and unusable.
Second attempt using Chrome Version 77.0.3865.120 (Official Build) (64-bit)
Stalls with green progress bar at 20%
Second attempt
Device is not able to be paired at this point. It doesn't even appear as recognizable in the 'Add a Device' BT settings section.
No Compatible devices found
Closed browser and reattempted
Windows10
Went to provide console output for native WebIDE app, but as device is now not recognized, get the 'No ports found' error when attempting to connect.
Tried the five second hard reset, but still not seen
Found this for STM32
Are there instructions on how to flash NRF52 using the UART?
EDIT:
1 Attachment