Recent content by bobreece20

My expectations (for now) is to be able to use the watch to monitor the bike and control it. Currently I'm not thinking about HR or anything like that. A simple small device to control is all I wish for now. Obviously I've no objections to working towards a Garmin Edge like device but I want to...

Yeah I'll get around to writing to documentation soon. Not much to see atm really. Lvgl provides a lot of nice widgets but a single button was enough to prove the concept and graphics renderering Helpfully Lvgl also comes with simulator for the PC so I can mock up the UI without having to...

Spent the entire day just trying to get my watch code running on top of a softdevice on the X9, who would of thought it'd be so difficult :shock:. Anyway I've got the lvgl graphics library hooked in now, got the button controls working so just need to hook in the ANT code and it'll be mostly...

Although I have been updating the schema I cannot take claim for the original creation and that one in particular is not one I've touched, I believe it's from @Headless. It would be good if we can get it in github though so it can be updated if needed :)

casainho, have you figured out a way to use NRF_LOG_INFO and receive the data via the SWD interface? It's not strictly needed as debug will do but it'd be nice to be able to log things out for more complicated applications

Yeah I agree, I'm hoping to try build on something like lvgl graphics library so if the watches disappear another nrf52832 based smartwatch can be used and all that would be required is a new lcd driver. I think I can prove the concept if it works on both the pinetime and x9 pro Update: Got the...

I wasn't noticing any issues with this example was nice and stable when I tried it but I was using softdevice s340 rather then the defaul that example comes with. And I'm also using pca10059 not the MDK dongle but I wouldn't of thought that would make a difference, although the button can be...

I've also been looking into BLE services, I found the ble_app_blinky example difficult as I couldn't convert it easily to use softdevice s340 (and at that point didn't have STLink to debug why the dongle was crashing). The ble_app_hrs example was simple to convert to use s340 though, just...

The pins used by these two different dongles are quite different. The only common exposed pins they share are the debugging pins and: 0.20, 0.09, 0.10, 0.02, 0.04(on the bottom of board, would be pita to use). Worse is that this dongle has LEDs on 0.06 which is being used for motor comms so will...

I was correct the issue was the bootloader checking application CRC and it not matching with the CRC it had stored. For now I've got around it by merging in the hex generated from `nrfutil settings generate --family NRF52840 --bootloader-version 0 --bl-settings-version 1 --application...

Very nice! I'm still hunting down the issues with trying to program my dongle. I've found that the application flash content is correct after a flash and flashing using openocd works if I flash the same hex as what I programmed via nRF Connect as a result it has to be the bootloader which is...

Turns out I was actually wrong about this, can only debug if I've flashed it via nRF Connect (even hooking up RST via the button doesn't work). The debug information appears to show it flashing correctly (and verifying it also shows its correct). I also verified after using nRFConnect and both...

Guess it's worth doing some experimentation with labels to see if we can have alternative boards much like we have alternative motor cables and then seeing how messy the schematic is

I'm fairly familiar with KiCad so when I get a spare moment I'll check out the pins and generate a new schematic for the blue dongle. Will probably also commit a footprint file for it too ready for pcb design

Finally got around to soldering pins onto my dongle for the STLink, my dongle is one of the blue ones (i.e. https://uk.farnell.com/nordic-semiconductor/nrf52840-dongle/bluetooth-module-v5-2mbps/dp/2902521) which appears to have a completely different pinout to the ones used in the schematics...