You are reading a single comment by @fanoush and its replies.
Click here to read the full conversation.
-
This watch seems like a far more likely candidate for the dickens parent. It has the i2c on pins 9 and 10 and 8MB of external flash like on the dickens the only difference being it uses a higher resolution display.
Oh, I am afraid this sounds more like wishful thinking . The design may be similar in some parts but it may not mean that much, there are not that many ways how you could do it.
And BTW G5 also has additional 16MB SPI flash so there are two SPI flash chips.
fanoush
Im lookin through the GW32.py and it seems that if pins are shown under the def get_pins(): area are they unused? or simply available to be used by apps?
i2c is pins 9 and 10 on dickens (available on the supposed HRM header) but on the GW32 the i2c is on pins 3 and 47. I cant imagine the difference matters much. At some point these NRF52840 watches are starting to meld together in a bunch of ways. If we can confirm that the GW32 watch has the 3 and 47 pins on the HRM header then itll be more obvious that it was derived from the GW32.
In the Dickens.py the package is shown as QFN48 but its actually the aQFN73
I took a look at the G5 Smart Watch .js and .py file here
https://github.com/jeffmer/WatchApps/blob/master/apps/main-g5/main-g5.js
https://github.com/jeffmer/Espruino/blob/master/boards/G5.py
This watch seems like a far more likely candidate for the dickens parent. It has the i2c on pins 9 and 10 and 8MB of external flash like on the dickens the only difference being it uses a higher resolution display. The G5 also has some pre-exisitng multiface code which could have been used for the multifaces on the starfield watch but that may be a stretch.
So along with the GW32 do you have any photos for the G5 watch PCB @jeffmer?