search

vgkits / vanguard-cli

VGkits' tools to connect to Micropython Vanguard Shell, reset, save and restore Vanguard firmware and other utility tasks.
GNU General Public License v3.0
1 stars 1 forks source link

Wemos D1s from different manufacturer will not flash successfully. #10

Open lesp opened 5 years ago

lesp commented 5 years ago

Hi Cefn,

Just received another couple of Wemos D1 Mini and Arduino layout boards from Aliexpress and noted that both will not flash. I've run the following to ID them for you.

esptool.py --port /dev/ttyUSB0 flash_id

==WEMOS D1 Mini Output== Detecting chip type... ESP8266 Chip is ESP8266EX Features: WiFi Manufacturer: c8 Device: 4016 Detected flash size: 4MB

==Wemos D1 Arduino Layout Output== Detecting chip type... ESP8266 Chip is ESP8266EX Features: WiFi Manufacturer: ef Device: 4016 Detected flash size: 4MB

Is there any chance that these can be added? Cheers Les

cefn commented 5 years ago

Thanks, @lesp

Hoping to get to refactoring the whole of vanguard-cli to extract flashing logic.

For now, have a focus on preparing classroom materials as per https://github.com/cefn/group9/blob/master/vector/presentation.pdf and then creating worked examples for Web-hosted text-adventures and interactive text games as per https://github.com/vgkits/vanguard-firmware/tree/prerelease/modules/vgkits/console/examples

Finally I need to build a new release for vanguard as 0.1.0 is getting old compared to the latest images I'm using. Need to stabilise the work-in-progress to achieve this.

Want to be sure you know about the --device flag for our vanguard-cli which overrides the auto-detection? Sorry not to have mentioned this to you earlier.

You can see the aliases you can 'force' at... https://github.com/vgkits/vanguard-cli/blob/master/vgkits/vanguard/__init__.py

For example in my case...

vanguard brainwash --device nodemcu_m --release 0.1.0 vanguard+rainbow

...succeeds at flashing the kits we're shipping from https://vgkits.org/blog/vanguard-rainbow-kit/ using the vanguard-rainbow image shipped in our pip package onto a nodemcu_m without doing any auto-detection, so the the manufacturer and device don't need to be in the table for it to work. That's assuming the entry with that device name has the correct memory size and flash mode.

Let me know how you're getting on with the tools and any more changes needed to make routine tasks easy.