I am now getting something similar to this. DFU3.11C on a 2MB device from Windows 7 64 host.
I was doing a bit of re-organising and find that Pawn_011.hex won't load and in my case renaming it doesn't help.
Behaviour is that DFU disk comes up and shows as a 500K drive as normal. When I copy the file, I get the copying dialog which stays up doing nothing then eventually fails saying DFU device doesn't exist. DFU device is still on Explorer tree but now has properties saying it is 0 bytes capacity. Power cycling the DSO into DFU mode restores the capacity but the process repeats.
If I use Pawn_008.hex version then copying proceeds normally and works fine.
I checked the hex file contents and they both look similar structure address-wise.
It would be nice to check out DFU source to see what could trigger this behaviour but I don't think that is available, ...unless someone knows otherwise.
Statistics : Posted by defacato • on Sun Feb 23, 2014 12:09 am • Replies 8 • Views 344
I was doing a bit of re-organising and find that Pawn_011.hex won't load and in my case renaming it doesn't help.
Behaviour is that DFU disk comes up and shows as a 500K drive as normal. When I copy the file, I get the copying dialog which stays up doing nothing then eventually fails saying DFU device doesn't exist. DFU device is still on Explorer tree but now has properties saying it is 0 bytes capacity. Power cycling the DSO into DFU mode restores the capacity but the process repeats.
If I use Pawn_008.hex version then copying proceeds normally and works fine.
I checked the hex file contents and they both look similar structure address-wise.
It would be nice to check out DFU source to see what could trigger this behaviour but I don't think that is available, ...unless someone knows otherwise.
Statistics : Posted by defacato • on Sun Feb 23, 2014 12:09 am • Replies 8 • Views 344