Search results for:

I've not tried/done it from espruino... but in my nrf code the steps to get to DFU are:

1. disable softdevice
   
2. disable interrupts (NVIC->ICER & NVIC->ICPR [0&1] = 0xffffffff)
   
3. write 0x57 into GPREGRET
   
4. call NVIC_SystemReset()
   

Superb! and welcome!

and it's quite weird to not have to reverse engineer a device for a change

bah, but that's half the fun. 😉

Runs a build of Android. Apparently uses a chinese "Ingenic M200" cpu - http://www.ingenic.com.cn/en/?newton/id/13.html so no, unlikely to be an option for Espruino.

So.... this will be "half a guide" reasons at the end. ☹
Disassembly was relatively straightforward if a little tricky, if I was more organised and had the setup I should have made a video, so I will try to describe. Can't see how to re-order pictures so attached show (pic 3) the black tape peeled away, (pic 4) the screen with the tape removed, (pic 5). all the backlight parts.
I used a soldering hot-air gun to soften the glue, but I expect a hair-dryer could be used instead just as effectively, firstly on the screen itself and then used a suction cup to pull the screen away.
The back of the screen is covered in a black plastic tape, this is very sticky and needs patience to remove, again - used the hot-air to soften the glue and peeled away from the top holding the screen back as it peeled, this tore where it joined the LCD cables at the base, I was assuming I'd just cut a strip of tape to replace it with, but it you're careful you could probably re-use this.
Next I used tweezers to pull the black plastic cover away, this seemed to be clipped around the edges.
Next (more warming) and the thin white plastic sheet is glued around the edges and needs pulling away again from the top, this should come away with the solid clear diffuser.
Now all the parts ready to fit to the new screen in reverse, place the white sheet into the black frame with the black edging upwards, LED's down (pic 2), then clip the frame onto the back of the LCD (pic 1), finally clip the diffuser into the back of the frame and connect the ribbon cable into the screen socket.
And now the failure. Connecting up the new screen discover that the watch was indeed destroyed in the accident and is completely dead, so I can't add a guide to finishing the reassembly and confirming that the backlight works.

Indeed, will take some pics and describe how it goes (assuming it's not an abject failure) 😁 also hoping the watch is still ok, it took quite a drop. 😬

Lifesaver Gordon! I just dropped my Q3 and smashed the screen. Hunted everywhere for matching/compatible/spare screens but finally found this. Fingers crossed.

Thanks! lots of jsiConsolePrintf's and using Bluetooth logging was just the ticket! (couldn't get RTT working, might try that again sometime).

All up and running now, going to be really handy having a permanently SWD connected unit to tinker with.

It only needs minor changes to work with this model (disabling GPS and IO expander, oh and speaker! and redirecting the IO lines).
Is there any interest/value in making a pull request for this? since I can't imagine there's going to be many people with one of these! or what it would be called either, it was just branded as F18, and was very cheap. It has a squarer edged case and metal strap.)

Perfect thanks, lots of ideas cheers! will give it a spin tonight. Having a huge amount of fun with these.

Hacker and Ultrarunner...
Blog
Mastodon

For more info/detail/spec take a look at https://treadmillsensor.blogspot.com/
The Bluetooth footpod spec is the "running speed and cadence" doc: Bluetooth profile doc
The ANT+ profile is - ANT+ profile doc

While I wait for a Bangle2... I was tinkering with getting the ANT+ 332 softdevice working to use with secondary HRM's (only reason for going ANT rather the BLE is all my HR straps here are ANT+)

So I picked up another F18 type board to play with, interestingly this one doesn't have GPS or use an IO expander so everything's a direct link to the NRF52.
So far I've got everything working but the flash isn't behaving (I've definitely traced the pins correctly to their new IO lines)

So the question I wanted to know/ask was what options there are for getting some/any debug logging out from the firmware? Is there any way to generate a debug message that can be passed back out to openocd or similar? or since the web bluetooth connection seems to be working is there any way from from the firmware to log to that? (I couldn't see either but I may have missed it)
(up to now I've been relying on adding "vibrate buzz" statements at points in the code and counting them!) :)

Looks like it's using something like this: [https://www.aliexpress.com/item/1005001380147177.html] so SPI serial interface. So you might be able to drive it from an SPI port, but it's certainly not a plugin replacement or just a matter of adjusting the connection.

and great success! Thanks, the problem was the bootloader was too large... doh.
Right, onwards to some more hacking, think I'll leave the SWD leads on for a bit, that's rather handy.
Keeping eyes peeled for the bangle2.

Thanks, pretty sure I'd had that on an earlier flash, just retried with that and does the same.

Is that warning in the flash output anything significant?

Warn : no flash bank found for address 0x60000000

Firstly apologies for going 'off-piste'...
but since I was intended to do some heavy hacking I didn't want to accidentally brick/destroy an official bangle.js but had no qualms blatting a generic watch I could easilly replace. So picked up an (I think identical?) unbranded version. (and I was rather taken with the red case! :) (pic1)

I'm connected via SWD, an STLink2 and OpenOCD (as I said I intended to do some hacking, bootloader changes, different NRF softdevice etc)

I thought everything was going well, but now I seem to be at an impasse, I assume I've missed something obvious or done something stupid, so any suggestions welcome. However obvious!
I've got a local build of Espruino using current git code.
After flashing then hex through OpenOCD:

> program /home/ivor/devel/espruino/Espruino/espruino_2v09.134_banglejs.hex reset
target halted due to debug-request, current mode: Thread 
xPSR: 0x01000000 pc: 0x000008e4 msp: 0x20000400
** Programming Started **
nRF52832-QFAA(build code: E0) 512kB Flash, 64kB RAM
Padding image section 0 at 0x00000964 with 1692 bytes
Padding image section 1 at 0x0001ebf0 with 1040 bytes
Flash write discontinued at 0x00072950, next section at 0x0007a000
Adding extra erase range, 0x00072950 .. 0x00072fff
Padding image section 3 at 0x0007dfc0 with 64 bytes
Padding image section 4 at 0x0007e324 with 3292 bytes
Adding extra erase range, 0x0007f324 .. 0x0007ffff
Adding extra erase range, 0x10001000 .. 0x10001013
Adding extra erase range, 0x1000101c .. 0x10001fff
no flash bank found for address 0x60000000
** Programming Finished **
** Resetting Target *

On reboot, says "storage is corrupt, erasing" then shows a ">" cursor. (pic2)

I thought/wondered if this was just because no apps had been uploaded/bundled and I can connect to the watch via "bangle.js/apps" from there if I run "Install Default Apps" the "Erasing..." happens but then it proceeds to uploading bootloader, displays "Uploading boot..." and hangs. (pic3)

Not sure if it's a related problem, but if I connect to the watch via nRFConnect it shows up as 'Nordic UART Service' with no DFU service.

Any suggestions what I've missed or what I should/could try?