[WIN 10]fwup burning to SD card not working as expected about fwup HOT 15 CLOSED

@GregMefford or @michaelkschmidt, have you seen this?

from fwup.

I have not. @gallexme can you send us the .fw file to see if I can reproduce it?

Also, when you write to the .img file, are you doing that in Docker or Windows?

from fwup.

Also, when you write to the .img file, are you doing that in Docker or Windows?

windows, im just creating the .fw file on a linux docker everything else on windows
blinky.zip

i dont think that there is anything special about the .fw

from fwup.

I didn't have a chance to look into this yet, but I'm curious if it's related to the block size of the SD card. Do you by chance have a different model of card you can experiment with?

from fwup.

@GregMefford I'm not aware of any non-512 byte block size SDCards. There are 4K hard drives, but not SDCards. If you're referring to erase block sizes, the SDCard firmware handles those variations.

This issue feels more to me like the drive didn't unmount all the way when fwup was writing to it. Then, Windows wrote some things on top of what fwup wrote and the contents were out of sync.

from fwup.

@fhunleth gonna test that later (fully unmounting it )

from fwup.

@fhunleth the block size was an issue during the transition from SD -> SDHC. There were a few cards manufactured with 1K Blocks to reach 2 GB.

Some more info here: https://en.wikipedia.org/wiki/Secure_Digital (Search for SDSC cards above 1 GB)

@gallexme what size card are you using?

from fwup.

@michaelkschmidt 1gb or 2gb not sure(not home) but im 90 % sure 2gb

from fwup.

OK, I think I have reproduced the issue

Looks like there are a couple bugs:

• We are not unmounting the FAT partition, so it does not get updated
• UBoot Stage1 doesn't appear to be writing

That said, if you have already written the card once, both items are already there and fwup can update the rest.

@gallexme can you confirm that if you write the card once with win32 disk imager, that you can update the app just using fwup on subsequent attempts?

from fwup.

If the FAT partition isn't unmounted, then all bets are off. I don't think there's any point in experimenting until that's fixed. Since the FAT partition is always updated on Raspberry Pis, even the smaller upgrade tasks aren't guaranteed to work. I think that if they do work that it's just luck since the files being upgraded are most likely not changing.

from fwup.

@michaelkschmidt actually i cant update
fwup -a -i rpi/fw.fw -t upgrade
Use 1.89 GiB memory card found at .\PhysicalDrive2? [y/N] y
21%
fwup: fat_write can't write(zImage.new): A hard error occurred in the low level disk I/O layer

from fwup.

@gallexme try the "complete" task:

fwup -a -i rpi/blinky.fw -t complete

The only reason I suggest this is that it has been accidentally working for me 😞

from fwup.

@gallexme: GitHub auto-closed this issue, but it really looks like @michaelkschmidt fixed it. Could you try out one of these and see if his fix works for you?

http://files.troodon-software.com/fwup/master/fwup.exe
http://files.troodon-software.com/fwup/master/fwup.0.9.2-dev.nupkg

from fwup.

@fhunleth seems to work 👍

from fwup.

@gallexme: Thanks! I'm generating a release with the fix now. Thank you very much for the report!

from fwup.