Troubleshooting¶

General¶

Powering Externally¶

All of the Daisy boards (except for Seed and Pod) must be powered externally to work. If you are using Field, Petal, or Patch, remember to plug in power and/or turn on your Eurorack case.

OLED Only Showing Lines¶

If your OLED only shows lines, you haven't powered your Daisy correctly. Please remember to plug in all adapters, and, in the case of Patch, turn on your case.

Flashing Board-Specific Firmware¶

Remember, when flashing examples from DaisyExamples or Daisy Web Programmer, only the examples for your board will work correctly. Seed examples will work on any board, but they are audio-only and will not respond to controls or interface with the OLED or LEDs.

Unable to Flash to Daisy¶

If you are unable to flash your daisy, make sure you've correctly connected the USB cable and put the device in DFU mode. Do this by holding the BOOT button down, and then pressing the RESET button. Once you release the RESET button, you can also let go of the BOOT button.

`make: Nothing to be done for 'all'.`¶

If you get the "error" make: Nothing to be done for 'all'., don't worry! Whatever you're trying to build has already been built! If you want to force a rebuild, run make clean; make.

Breadboarding¶

When powered externally, Daisy should be powered with DC from 4V to 12V. Make sure to plug power into VIN and no other pins. Both AGND and DGND should be connected to the power supply's ground. In the diagram, power supply + should be connected to the red rail, and - to the blue rail.

Breadboarding for Seed and Power Supply When powered strictly from the USB cable, VIN doesn't need to be connected. However, DGND and AGND still must be connected to each other.

Command Line Tools¶

Missing Tools¶

bash: command not found: make

This indicates that make is not installed. Follow the steps for your OS to install make. The instructions for this are on pages 1b, 1c, and 1d. On Windows and Linux, please ensure you've added make to your system's $PATH. The instructions for this are on your OS's Getting Started page.

make: arm-none-eabi-gcc: No such file or directory

This indicates that arm toolchain is not installed. Follow the steps for your OS to install the arm toolchain. The instructions for this are on pages 1b, 1c, and 1d. On Windows and Linux, please ensure you've added the arm toolchain to your system $PATH. The instructions for this are on your OS's getting started page.

make: dfu-util: No such file or directory

This indicates that dfu-util is not installed. Follow the steps for your OS to install dfu-util. The instructions for this are on pages 1b, 1c, and 1d. On Windows and Linux, please ensure you've added dfu-util to your system $PATH. The instructions for this are on your OS's getting started page.

Errors Resulting from Submodules Not Being Initialized¶

If submodules is not initialized, you'll see the following errors:

collect2.exe: error: ld returned 1 exit status
make: *** [../../libdaisy/core/Makefile:203: build/whitenoise.elf] Error 1

or

Makefile:15: ../../libdaisy/core/Makefile: No such file or directory
make: *** No rule to make target '../../libdaisy/core/Makefile'.  Stop.
done

If you see these errors, run the following from your DaisyExamples directory: - git submodule update --init --recursive - ./rebuild_all.sh

Flash Failure¶

If you see the following:

Warning: Invalid DFU suffix signature
A valid DFU suffix will be required in a future dfu-util release!!!
No DFU capable USB device available
make: *** [../../libdaisy/core/Makefile:252: program-dfu] Error 74

ensure your USB cable is connected properly and your Daisy is in DFU mode. To put your Daisy in DFU mode, hold the BOOT button down and then press the RESET button. Once you release the RESET button, also release the BOOT button.

Windows downloading files with DOS line endings( ex. "'\r': command not found" in console)

Windows USB devices and hubs can be debugged using the USBView tool in the Windows SDK.

Validating the Toolchain¶

Running the following commands will confirm if the associated tool is installed on your machine:

make --version

arm-none-eabi-gcc --version

dfu-util --version

openocd --version

If you see the following (or a similar message) after running any of the above, then that tool was not installed properly:

bash: make: command not found

Arduino¶

Problem Uploading¶

Make sure that you installed STM32CubeProg on your system. You can test this by trying to run the program on its own.

If it is not installed, download and install STM32CubeProg.

Problem Uploading on Windows¶

You might need to use Zadig to reset your USB driver. You can follow our Zadig page here.

DaisyDuino Library Shows up as INCOMPATIBLE¶

If your selected board is not a Daisy compatible processor, the DaisyDuino library will show up as INCOMPATIBLE in the IDE. Once you have selected a board that can accept Daisy firmware, the library will no longer show up this way.

U8g2 not installed¶

You may get the error error: 'U8G2_SSD1309_128X64_NONAME2_F_4W_SW_SPI' does not name a type. To solve this, follow step 2.5 to install the OLED library from the Getting Started with Arduino page.

Oopsy¶

First things first, if you think you're having a problem, press the 'QUIET' button so that it turns gray instead of yellow. This will enable printing to the Max console.

Checking If Daisy is in Bootloader Mode¶

You should be able to see "DFU in FS Mode" listed in your computer's Device Manager.

However, if you have already successfully flashed gen~ code once, the onboard LED will blink once per second to indicate that the firmware is running. This blinking stops upon entering bootloader mode.

"No DFU capable device available" (Windows)¶

Open Zadig and reset the driver for Daisy ("DFU in FS Mode") to "WinUSB" (instead of "STTub" or "usbser"). This must be done while Daisy is in bootloader mode.

`oopsy-verbose: "stderr . . . . . cannot find -ldaisy"`¶

If you see that error in the Max console after pressing Oopsy’s button, this will generally mean that you cloned the repo from Github and did not run the ./install.sh script. Or, you downloaded the source of the repo and not the fully built oopsy package.

To run ./install.sh: - Open up terminal - Type cd Documents/"Max 8"/Packages/Oopsy and hit enter - Type ./install.sh and hit enter

VS Code and Cortex Debug¶

Note: VS Code has a bash terminal built in, so many VS Code errors are covered in Command Line Tools.

`make : The term 'make' is not recognized as the name of a commandlet...`¶

This indicates that Git bash is not default. To switch your default terminal to Git bash, follow step 1.5 of Getting Started with VS Code and Cortex Debug. If Git bash isn't an option, make sure you have git installed. It can be installed from here.

Please note that this problem only applies to Windows. All other OS's will use the native bash terminals.

Contact Us¶

Still stuck? Don't hesitate to get in touch via Discord, the Forum, or directly with Electrosmith.