Troubleshooting¶
General¶
Powering Dev Boards: All of the Daisy boards, (except for the seed and pod) must be powered externally to work.
If you are using the field, petal, or patch remember to plug in power and/or turn on your Eurorack case.
Dev Boards w/ OLED: 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 the patch turn on your case.
DaisyExamples Board Compatibility: Remember when flashing examples from DaisyExamples or the 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 OLED or leds.
DFU Mode: If you still are unable to flash you 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 Clean: 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, the daisy should be powered with DC from 4V to 12V.
Make sure to plug power into VIN and no other pins.
Both AGDN 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.
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¶
The Problem: Make not installed
The Error: -bash: make: command not found.
The Solution: 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 $PATH. The instructions for this are on your OS's getting started page.
The Problem: arm toolchain not installed
The Error: make: arm-none-eabi-gcc: No such file or directory
The Solution: 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.
The Problem: Dfu util not installed:
The Error: make: dfu-util: No such file or directory
The Solution: 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.
The Problem: Submodules not initialized.
The 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
The Solution From your DaisyExamples directory run
git submodule update --init --recursive then
./rebuild_all.sh
The Problem: Flash Failure
The Errors:
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
The Solution: 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, then press the RESET button. Once you release the RESET button, you can also let go of 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.
If you see this, or a similar message after any of the above, then that tool was not installed properly.
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 wiki 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.
Here are some common issues and how to resolve them:
I'm not sure I'm in bootloader mode or not.
You should be able to see "DFU in FS Mode" visible within your computers 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.
I'm on windows, and I see "No DFU capable device available"
Open Zadig, and reset the driver for the Daisy ("DFU in FS Mode") to WinUSB (instead of STTub, or usbser)
This must be done while the Daisy is in bootloader mode.
I clicked the bang, and saw: oopsy-verbose: "stderr . . . . . cannot find -ldaisy" in the max console.
Generally this will 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
VS Code and Cortex Debug¶
Note: VS Code has a bash terminal built in, so many VS Code errors are covered under Command Line Tools.
The Problem: Git bash not default (Windows only)
The Error: make : The term 'make' is not recognized as the name of a commandlet...
The Solutions:
Switch your default terminal to git bash. These instructions are 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.