-
Notifications
You must be signed in to change notification settings - Fork 103
Troubleshooting FAQ
Keir Fraser edited this page May 12, 2021
·
11 revisions
-
Greaseweazle is not detected by my host PC
- Test your USB cable with another device. Charging-only micro USB cables which omit the data wires are very common and will not work to connect Greaseweazle (or any other device) to your PC.
- If the activity LED blinks a repeated pattern, see the next question in the FAQ.
- F1 only: Check the resistance between Blue Pill pins A12 and 3.3. If this is not 1.5k ohms then you should remove Blue Pill surface-mounted resistor R10 and manually connect a 1.5k resistor between A12 and A0.
- F1 only: Be aware of STM32 fake chips which do not work properly.
-
Greaseweazle blinks the activity LED and is not detected via USB
- Greaseweazle performs a power-on self test and blinks a diagnostic
code on failure:
- 1 blink: Board version straps are unstable. Check for bad soldering around those pins (PC13-15).
- 2 blinks: Board version straps not recognised. Check you're loading the latest firmware.
- 3 blinks: Oscillator failed to start up. Check the external oscillator.
- 4 blinks: Unrecognised or incorrect microcontroller chip.
- Greaseweazle performs a power-on self test and blinks a diagnostic
code on failure:
-
Commands fail with 'Track 0 not found' or 'No Index'
- If using an F7-based Greaseweazle, the default drive is A. This requires a PC drive (strapped for DS1, pin 12) and a ribbon cable with a twist across pins 10-16. If you have a different drive setup, please see the documentation for Drive Select.