v0.19.877

[amandel]

Version v0.19.877 based on refs/heads/main f5bca8c

🎉 Major features and improvements

• b7e83f2 - Allow multiple WiFi configurations for different networks (Allow multiple WiFi configurations for different networks #343)

🚀 New features and improvements

• 8a9fb45 - OpenBikeSensorFirmware-334 Flush CSV/SD buffer when privacy zone is entered (Flush CSV and SD buffer when privacy zone is entered #341)

📦 Dependency updates

• e80c0ad - Chore: update SQ scanner version
• 3f938c3 - Bump metcalfc/changelog-generator from 4.1.0 to 4.2.0 (Bump metcalfc/changelog-generator from 4.1.0 to 4.2.0 #346)
• d53fea6 - platform update to 5.4.0
• c218640 - Update SonarQube dependencies (Refresh build tool dependencies #342)
• 43a7299 - Update library dependencies
• d2b1bb6 - Bump metcalfc/changelog-generator from 4.0.1 to 4.1.0 (Bump metcalfc/changelog-generator from 4.0.1 to 4.1.0 #337)

👷 Changes for developers / internal

• f5bca8c - Preparing 0.19 release

---

This discussion was created from the release v0.19.877.

[gluap]

@amandel On one device that I had pre-flashed with "pio run -t upload" running 0.18-dev I wasn't able to automatically update

• Firmware correctly found the latest version number, but wasn't able to flash 0.19.xx from the weg
• The same device also wasn't able to flash 0.18.xx from the web.
• pio run -t erase; pio run -t upload didn't help
• uploading the latest firmware.bin didn't help (showed "updating" but came back up with v0.18-dev)
• Using a new SD fixed the issue.
  • Strangely though the original sd works just fine for recording, only gives trouble when flashing.

So everything is alrigtht :)

Log during failing flash attempt (note to self: the light blue OBS on the cargobike):

␛[0;32mI (233) flash-sd: OpenBikeSensorFlash version v0.2.38.␛[0m
␛[0;32mI (243) flash-sd: Reset reason 0x3.␛[0m
␛[0;32mI (243) flash-sd: Running partition: flashApp␛[0m
␛[0;32mI (253) flash-sd: App 'OpenBikeSensorFlash', Version: 'v0.2.38'␛[0m
␛[0;32mI (253) flash-sd: IDF-Version: '4.3.1'␛[0m
␛[0;32mI (263) flash-sd: sha-256: 5fd778b4903689a73b328fe0a161cf4a7b080714b4512308f0c053c9a690fbb7␛[0m
␛[0;32mI (273) flash-sd: date: 'Nov 27 2021', time: '15:01:34'␛[0m
␛[0;32mI (273) flash-sd: Initializing SD card␛[0m
␛[0;32mI (283) gpio: GPIO[5]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0 ␛[0m
␛[0;32mI (293) sdspi_transaction: cmd=52, R1 response: command CRC error␛[0m
␛[0;31mE (293) sdmmc_io: sdmmc_io_reset: unexpected return: 0x109␛[0m
␛[0;31mE (303) vfs_fat_sdmmc: sdmmc_card_init failed (0x109).␛[0m
␛[0;32mI (303) gpio: GPIO[5]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0 ␛[0m

abort() was called at PC 0x400d1351 on core 0

Backtrace:0x40085422:0x3ffb55e0 0x40085b4d:0x3ffb5600 0x4008a0a6:0x3ffb5620 0x400d1351:0x3ffb5690 0x400f023e:0x3ffb5760

[amandel]

Hmm, I'm not sure. A broken SD card could definitely be a possible cause. But you write that the SD worked fine otherwise.
Still the flasher app uses a bit different technology and likely a different library to talk to the SD card.
I'm guessing here, glad that it works now and we hopefully do not see this often.