lasaska.blogg.se

1. #SANDISK SANSA FUZE UPDATE FIRMWARE UPGRADE#
2. #SANDISK SANSA FUZE UPDATE FIRMWARE SOFTWARE#
3. #SANDISK SANSA FUZE UPDATE FIRMWARE WINDOWS#

I was able to connect/disconnect/reset/restart a lot of time and the device was up for all those tries before the last. It kept telling me the cable was disconnected though I haven't touched a thing there, and checking that "pop API errors" checkbox, I was able to see that this error was triggered when attempting to contact the device. And guess what, I saw the sansa logo again since a long time However, god-knows-why, the device booted in MTP mode and I was not able to update the firmware so I tried to fix that up and that's probably when I messed something up because I wasn't able to see the device again with OCD Commander (and H-JTAG for those that wonder). With this setup, I was able to connect to the JTAG module on the Sansa m200 SoC, halt it, reset it, update the clock generation unit register to re-enable the external memory module, inject a valid ORR instruction to fix my faulty AND instruction and make the program run again. Note to use the buffered version with the 74HC244 (or 74AC244 if that's what you have.). This software, however, requires to add a jumper between pin 8 and 15 of the parallel port to be recognized, so here is a valid schematic to be used with the OCD Commander software. It's very nice because you can directly control the cpu, halt it, reset it, inject instructions, replace instructions, etc.

#SANDISK SANSA FUZE UPDATE FIRMWARE SOFTWARE#

I came across the OCD Commander software by Macraigor, which is the original producer of the Wiggler JTAG adapter/cable. Anyway, no big deal, I was already prepared not to revive my sansa.īut I can give more detail on my method. I could be many things because I was working on a pretty risky setup with a breadboard and stuff so maybe I inadvertently shorted wires or something. I'm really interested in giving a hand, if I can.Īnother news but not good this time, it seems that JTAG stopped responding on my device. My sansa did not even want to flash itself with this modified version ('Upgrade in progress.

Weird, since the checksum program (available into Daniel's wiki) told me that the checksum did not changed.

#SANDISK SANSA FUZE UPDATE FIRMWARE UPGRADE#

But since I did not find any mention of them on the firmware wiki page, I thought it would be interesting to mention.Īnother thing : I tried to upgrade to a "by-hand" modified firmware (I just changed "HOLD" into "HALD" in a string), but it did not work as expected. Total time: 6 sec 223 ms - global rate: 2.4 MB/secīy the way these pictures aren't really interesting to extract (sandisk logos, and pictures of the device. but maybe there are some pullups or some powermanagment stuff to enable.Ĭode: % hachoir-subfile e200pe.bin Will test again with oscilloscope some time) (But i have measured with a slow DMS - maybe the keys are tested only for a short periode of time, and the DMS integrates over it. * In normal mode, but screen (and blue leds) switching off: 0.5Vīut even with from that mode (with 0.5V) the sansa can detect keypresses. * If the Sansa-Bootscreen appears and in normal mode: 3V * After power on, but in the wait-loop: 1.9V Maybe one problem: Measured the voltage on the switches again - one side is always ground the other one: Tried all 8 bitmasks for GPIO1 (which is hopefully GPIOA): no reaction to keypresses - every time it waits the ~5 seconds. Noloop: ldr pc, originalentry(Test now in the loop - maybe to circumvent timing problems) * Now branch back to the original firmware's entry point */ Mov r1, #0x500000 /* Approximately 5 seconds */ * A delay loop - just to prove we're running */ Please let us know if you have any other queries on Windows.Code: /* This value is filled in by mkamsboot */

If the issue still persists, refer to the link to post the same query on Sandisk forum: Refer the section “ Run the Hardware and Devices troubleshooter” You can run hardware and device troubleshooter and check if it works:

#SANDISK SANSA FUZE UPDATE FIRMWARE WINDOWS#

Refer to the link to get the details on Windows Compatibility center: Is the issue specific to this device? Are other USB devices getting detected on the computer?Īs far as compatibility is concerned, the device is compatible with Windows 8.1. This issue might occur if the device configuration settings for the SanDisk Sansa Clip+ 4GB Media Player.