Avatar for fanoush

fanoush

Member since Jul 2018 • Last active May 2019
  • 2 conversations
  • 86 comments

Most recent activity

  • in Projects
    Avatar for fanoush

    I went through another list of firmware files from IBand android app, all of them are SDK11 legacy DFU packages (!) for nrf52832, here is a list of device names with available firmware binary

    A8 ASA306 CB606 CWatch1 Daily DK08 EC008 F07 F07A F07Lite F10 F10A F10U F1Pro H808 H818 HB049 HB08 HB080 K2 K5 K8 KETO L8 M01 M05 M08 M10 M520 M7 M98 Matr02 MCplus2 N108S N109 N68 N69 NarutoBand ONYX SL11 Smart SVC TF1 voyage W331 X9_00 X9_OP X9Pro

    you can google them like

    -name- smart "iband"

    with iband in quotes to avoid autocorrection to band, most of them are in >$30 price range but look very good, I think you will like most of them, so far I found M7 M10 M520 W331 F1pro DK08 K2 K5 L8 F10 F07 TF1 N68 N109 X9Pro (mainly on aliexpress, ebay, gearbest), listings mention iband app and nrf52832, so far F07 is cheapest - ~$17
    In theory all of them are updatable via OTA :-)

  • in Projects
    Avatar for fanoush

    Oh, I see the 52840. Small but it is there. So the listing may be wrong. OTOH they may have invested a lot into their combined customized bootloader so they could stick to unsigned firmware after all. Just today I saw what adafruit did here https://github.com/adafruit/Adafruit_nRF­52_Bootloader/tree/master/lib/sdk11 or see https://github.com/adafruit/Adafruit_nRF­52_Bootloader/blob/master/Makefile#L114 they appear to actually link old SDK11 bootloader sources with newer SDK to support nRF52840 and legacy unsigned DFU(?). In theory Desay could do the same but the chance is of course very low.
    EDIT: they indeed use legacy unsigned DFU format with the nRF52840 becasue the readme points to https://github.com/adafruit/Adafruit_nRF­52_nrfutil which is old 0.5.3 nrfutil fork using legacy DFU, I use it with DS-D6 now. Maybe you could check that bootloader and use it with espruino too? The UF2 format support looks interesting.

  • in Projects
    Avatar for fanoush

    If you want something more watch like they have this one https://www.globalsources.com/si/AS/Desa­y-Infor/6008849906089/pdtl/smart-watch/1­167004841.htm but we don't have firmware for this one so cannot say if is it same SDK11 as others.

  • in Projects
    Avatar for fanoush

    That's really neat - so you literally just power on the watch, run this app with the firmware, and you're sorted? That's the kind of thing that could easily be automated to update off-the-shelf watches.

    Yes, but only for those made by DESAY INFOR TECHNOLOGY CO.,LTD. https://fccid.io/2AEMN https://www.globalsources.com/si/AS/Desa­y-Infor/6008849906089/Homepage.htm

    So if you e.g. could source this one https://www.globalsources.com/si/AS/Desa­y-Infor/6008849906089/pdtl/smart-bracele­t/1167004880.htm or this one https://www.globalsources.com/si/AS/Desa­y-Infor/6008849906089/pdtl/Heart-rate-Sm­art-Bracelet/1167004822.htm it would most probably work (we do have links for DFU zips for most models including this D15F or Z10F one)

    EDIT:
    And BTW same thing can be done for devices manufactured by "Shenzhen DO Intelligent Technology Co. Ltd" as they also use SDK11 for their ID1xx models (except that ID205 nRF52840 model) so you don't need for them to do custom firmware, you just need to meet minimum order which may be an issue too.

    However if you aim for nRF52840 then SDK11 is out of question, looks like they stick with old proven SDK11 they initially started with when going for nrf52, but they cannot do this with nRF52840 .

    And others possibly started with nrf52 a bit later so they stick to SDK12 (and signed firmware :-( )

  • in Projects
    Avatar for fanoush

    This is bluetooth DFU for original Desay bootloader - it does not use standard Nordic BLE DFU guids so cannot be updated via nrf connect Android app. Until now the procedure of updating new device was using nordic tools over TTL serial. So this is targeted to SDK11 based development with original bootloader for people who don't have usb to TTL serial adapter. Not just for Espruino built with SDK11 but also for Arduino code.

    Once updated to espruino SDK12 bootloader (which now works still only via TTL serial, this tool does not handle uploading bootloader or soft device yet) this D6 flasher is no longer useful as you can use nordic nrf connect since the DFU over BLE is standard nordic one (and signed, not old legacy format).

  • in Projects
    Avatar for fanoush

    Wow, the atc1441 guy did it again. He published playstore app https://play.google.com/store/apps/detai­ls?id=com.atcnetz.ble.readwrite to update DS-D6 over bluetooth easily. So if you were hesitating to get TTL serial working now you have one less excuse to get this $7.99 watch to run Espruino ;-)

    It can even detect Espruino and reboot it to bootloader automatically so you can easily update to newer Espruino version.

    This should also work with other devices manufactured by Desay. I will verify it with DS-D9 I have and also with HX03W once it finally arrives.

  • in Projects
    Avatar for fanoush

    There is another nRF52840 watch. I was going through 60 FW links from H Band android app (credit goes again to the same guy) and most is nrf51, some is nrf52 - all nrf52 are SDK12, signed and one has stack pointer 0x20037404 so looks like 256KB SRAM. nrfutil says it is hw version 52 however the soft device is recent with app start at 0x26000 (same as ID205 above, sdk12 SoftDevice 3.0 has 0x1f000). The string found in firmware that may be device name is V12 which may be this
    https://wosmart.en.alibaba.com/product/6­0829664160-807772971/FITUP_smart_watch_b­racelet_V12_sport_fitness_tracker_nRF528­40_smart_bracelet.html and possibly also https://www.cavosmart.com/products/fitne­ss-tracker-v12/
    Again the firmware is signed so this is just if one wants to take it apart.

    EDIT: this one is a bit risky to get for the 52840 chip, there are two same/similar devices V12 and V12C. The V12C one has older nrf52 chip. If you check this page in chinese and translate to english http://www.wo-smart.com/p-333.html then it is very confusing what is the difference and which one is better/newer but they do mention different chips. I also found V12C FW binary and this one is indeed SDK12 based with <64K SRAM stack pointer.

  • in Projects
    Avatar for fanoush

    Yes at most one needs to open just one but all other can be updated wirelessly. With a bit of luck even the first one will work as I tried with DS-D9 and generic espruino build. It comes up and can be connected over bluetooth and the rest of HW could be figured out by trial and error from espruino and/or reverse engineering the firmware.

    I have another batch of SDK11 nrf52 based trackers, these are too from VeryFit Pro app but there was no sensible metadata so the strings are from firmware binary

    • Polyfit HR Pro
    • ID 107 Plus Color HR
    • ID131 Color HR
    • ID133 Color HR
    • ID130 Plus Color HR
    • S4000
    • ACT304
    • ID115 HR (this one is nrf51, 32K)
    • ACT101 (nrf51, 16K, look like ID115)

    The S4000 is interesting as it has GPS however I cannot find any info about it. These are bluetooth names so the product may have different name. Some interesting strings from S4000 binary : sony\gps_cxd56xx_agps.c, oled, spi_flash,PPG_sensor\si117x\si117x_ic.c

  • in Projects
    Avatar for fanoush

    The ID205 is also listed here https://idoosmart.manufacturer.globalsou­rces.com/si/6008849563328/pdtl/Smart-wat­ch/1165759500/smart-watch.htm which I suppose is the page of the "Shenzhen DO Intelligent Technology Co. Ltd" manufacturer. The page mentions "Very Fit Pro" app and "Main CPU: Nordic nRF52842". If you are interested in direct veryfit app hosted firmware download link let me know. It is signed firmware, the .bin file inside is ~700K and initial stack pointer points to 0x2003F3F8 so SRAM is 256KB, interrupt vectors point to 0x26xxx so 0x26000 is app start which implies soft device version. Also "nrfutil pkg display" shows info like:

      |- Type: application
       |- Image file: ID205.bin
       |- Init packet file: ID205.dat
          |- signature_type: ECDSA_P256_SHA256
          |- hw_version 0x000000E2 (226)
          |- sd_req: 0xA9
          |- hash_type: SHA256
    

    However I did not find this model here https://fccid.io/2AHFT which otherwise has most of their devices.

    This was one of the first firmware files so I hoped there could be more nRF52840 ones but this was the only one after all. However good news is that their older nrf52 models are based on SDK11 so the firmware is not signed, here are model names (from FW metadata)

    I also went throught WearFit app links but all nrf52 ones are signed (M2S,M6,eTimerFit,AISIRER-8C_HannStar) however there are lot of nrf51 based, all of them using the 32K SRAM variants so they are moderately usable too (K1,B15S,C1,CK11,E26,M8,OSSINE X7, P2 HR,SWB200,T-FLY,YKY_SH,Tempo,Z18).

  • in Projects
    Avatar for fanoush

    He is also the guy who can figure out lot of links to firmware downloads from the android apps so we are currently in the process of going through DFU zips for devices supported by VeryFit apps and WearFit apps. Some are interesting, most new ones has signed firmware. All of them Nordic chips. BTW some already have 52840 chip e.g. the ID205 (possibly this one?). Of course it uses latest SDKs to support that CPU so the DFU is signed. Some of older ones are based on 51442 which seems like odd choice as they are used with BLE SoftDevices, not ANT.

    I'll send update if something useful comes out of this. Veryfit are those various IDxxx devices, WearFit app devices are often sold as Wearpai (e.g. the GT-101 FCC ID manual has Wearpai there) but there are many other sellers rebranding this on aliexpress like e.g. Letike.

Actions