electro-smith / daisywiki Goto Github PK

I received my Daisy Seed boards today and am excited to dive-in. However, I am not finding an obvious source for hardware documentation. For example what are the IO pins' current sourcing and sink capacities?

Are there plans to build-up the hardware documentation?

Are there plans to build a getting started guide from the hardware development standpoint and not just the software side?

Thank you.

I am trying to build this pod example "MultiEffect" using my mac big sur 11.2.2
https://github.com/electro-smith/DaisyExamples/tree/master/pod/MultiEffect
I cannot get the build tools in VSCODE to work so I am attempting to build with make from inside the MultiEffect directory.
ie

$make clean
$make

The entire error is this

   39 | void AudioCallback(AudioHandle::InterleavingInputBuffer  in,
      |      ^~~~~~~~~~~~~
MultiEffect.cpp:39:33: error: 'InterleavingInputBuffer' is not a member of 'daisy::AudioHandle'
   39 | void AudioCallback(AudioHandle::InterleavingInputBuffer  in,
      |                                 ^~~~~~~~~~~~~~~~~~~~~~~
MultiEffect.cpp:40:33: error: 'InterleavingOutputBuffer' is not a member of 'daisy::AudioHandle'
   40 |                    AudioHandle::InterleavingOutputBuffer out,
      |                                 ^~~~~~~~~~~~~~~~~~~~~~~~
MultiEffect.cpp:41:58: error: expected primary-expression before 'size'
   41 |                    size_t                                size)
      |                                                          ^~~~
MultiEffect.cpp: In function 'int main()':
MultiEffect.cpp:98:20: error: 'AudioCallback' was not declared in this scope
   98 |     pod.StartAudio(AudioCallback);

I spent a fair bit of time sniffing around classes looking for that class and function without much luck. Lots of inheritance and I cant find documentation of all the classes anywhere in detail. Does it exist?
I tried a git pull I can see that file was updated since my last pull. I tried to rebuild the daisy source files again with make but they seemed up to date "nothing to be built" or something. I guess I will have a go with vscode on my windows machine. Perhaps classes have been named in some conflicting way. Where is that daisy::AudioHandle class located ?
I have a bunch of C++ code it is a simple modulated delay.
https://github.com/seanwayland/waylodelayUD/blob/main/PluginProcessor.cpp
I thought of trying to build it all on this thing if I can figure out how to hook up the knobs. I built the same thing using gen~ once perhaps that is an easier way in here. Some very simple examples of knob and say a gain added to an audio buffer might really help me here ?? The MultiEffect exampled worked fine using the browser to load it. Thanks for your help.

Hi,

Given I use Windows and the latest Edge browser that is Chrome based, I was wondering if Edge will work with your system? It would be cool if it did.

Any info here would be appreciated.

libDaisy shows codec_reset_pin = {DSY_GPIOB, 11};

Could be nice to add this to the spreadsheet docs.

added PR for CSV #20

In the arduino instructions on the wiki, when you get to running the blink example, it might be a good idea to tell people if the LED pin in the blink example needs to be edited (Even if it doesn't). some people might think it needs to be edited because of the pin number instructions at the top of the blink example.

The pin is correct, and the csv file is accurate, but the pin is not capable of doing I2C3_SCL.

At present, the only instructions for installing openocd are in the MacOS section, and recommend building from source

Recently, the forum had brought up the xpack distribution of openocd which I have tested on windows so far and it works with the STM32H750.

Installation instructions are here:
https://xpack.github.io/openocd/install/

It'd be worth refining each OSes section, or adding a dedicated "Debug Tools" section to Wiki recommending to get openocd from here.

Hey everyone,

following the Getting Started tutorial 1.-Setting-Up-Your-Development-Environment and specifically for Windows 10 we ran into a weird problem with make.

Following the tutorial and just running make from a directory with an example, e.g. ADenv exits and fails with the following line:

mkdir build
process_begin: CreateProcess(NULL, mkdir build, ...) failed.

This problem is present both in the Windows Command Line (cmd, the black one) and PowerShell (the blue one).

The workaround is to create the directory called build manually in the file explorer. Make then compiles the files as intended, even though the failure prompt remains present (but gets skipped over).

I suspect the mkdir command is not available by default in windows, and there may be a way to enable it. This might be worth a note in the getting started tutorial (certainly caused some headscratching here before we figured it out.)

Links in the wiki links incorrectly
Example:
https://github.com/electro-smith/DaisyWiki/wiki/1a.-Getting-Started-(Arduino-Edition)

Links to:
https://github.com/electro-smith/DaisyWiki/wiki/

Hey everyone, regarding the instructions on this page -
https://github.com/electro-smith/DaisyWiki/wiki/1a.-Getting-Started-(Arduino-Edition)

There should be some kind of hint that if you install ArduinoDaisySP ( https://github.com/electro-smith/ArduinoDaisySP ) to the IDE via .zip file, you need to manually add the files from DaisySP ( https://github.com/electro-smith/DaisySP ) without the example folder to the arduino library's location i.e. Documents\Arduino\libraries\ArduinoDaisySP\src\utility\DaisySP

It's easy to troubleshoot but if you don't do it (using the .zip install method) you get an error during compilation that daisysp.h is missing.

The installation instructions for the Linux toolchain point to this page to download the toolchain.

I have downloaded gcc-arm-11.2-2022.02-x86_64-arm-none-eabi.tar.xz but it gives an internal compiler error when trying to build the libraries. You can find the error messages attached: ErrorMessages.txt. It mainly consists of the following error:

building libDaisy . . .
In file included from src/daisy.h:5,
                 from src/daisy_seed.h:5,
                 from src/daisy_field.h:4,
                 from src/daisy_field.cpp:1:
src/daisy_core.h:81:5: internal compiler error: Illegal instruction
   81 |     return ((float)x - 127.f) * U82F_SCALE;
      |     ^~~~~~

Steps to reproduce

1. Download gcc-arm-11.2-2022.02-x86_64-arm-none-eabi.tar.xz.
2. Decompress the archive.
3. Make sure that the bin folder of the archive is in your path.
4. Go to your working directory of the DaisyExamples repository.
5. Execute: ./ci/build_libs.sh

Workaround

The workaround is to go to the page with the older releases and to download gcc-arm-none-eabi-10.3-2021.10-x86_64-linux.tar.bz2 from there and to use that release.

Proposed solution

Please consider to update the Wiki page so that it also points to the older releases of the compilers: https://developer.arm.com/downloads/-/gnu-rm. A pointer to the last known good release would also be helpful.

Please also consider to give more specific information about what is the correct download for the most frequent case of an x86_64 Linux machine. For me it was quite confusing to make sense of all the options on the ARM page.

The Toolchain installation pages have an error. ARMGCCPATH is not the right name for the environment variable. I guess it changed at some point and should be updated.

Hey, I still wait for my board, but was happy to know that the lib is finally there. It still fails as there's no ./rebuild_libs.sh
Also when building examples I get the following:
PluckEcho.cpp:2:10: fatal error: daisysp.h: No such file or directory
2 | #include "daisysp.h"
| ^~~~~~~~~~~
compilation terminated.

For each....

Below is copy/pasted from my response on Slack

There isn't a specific official example yet. I've been trying to figure out a way to make VS Code projects for all of the Daisy Examples that can work from the root folder as a single workspace, but I don't know that it can work with how VS Code, and the extension are set up.
For now, if you have the DaisyExamples folder, you can pick any example and add the .vscode folder from this template. (I haven't used vs code for debugging in a few weeks. So I may have forgotten a step or two). I added a README to show what edits you have to make to the files (for the final binary, and the compiler path), but then you should be good to go.
I haven't tested this yet, but it came from a working project. I may have some time later today to test this, and I'll plan on making a wiki page specifically for this ASAP!

CortexDebugFiles.zip

When trying to extract to ~/Developer I get the following error during extraction:

"Could not create the hard link file:///home/user/Developer/libc.a"

Also, I'm trying to install V10.3 as suggested in the wiki, even though the page is listed as deprecated. I also noticed in other issue descriptions some folks are using a more recent version would there be a newer recommended version? I'm on Ubuntu 22.04.

Cheers :)

Hello,

When I go to this page : https://github.com/electro-smith/DaisyWiki/wiki things don't seem to be rendered properly. Thanks for your help!

Romain

I get this error messages on VS:

cannot open source file "daisy_seed.h"

I can't get to install the libraries. I did make it work on the git bash that was previously explained on https://github.com/electro-smith/DaisyWiki/wiki/1.-Setting-Up-Your-Development-Environment I don't know why you deleted that part

I am on Windows 10

https://github.com/electro-smith/DaisyWiki/blob/master/resources/Daisy_Seed_Pinout.csv
vs
https://github.com/electro-smith/DaisyWiki/wiki/2.-Daisy-Seed-Pinout

The column for daisy pin number starts with 1 but the graphic starts from 0.

Need pwm based high fidelity garnular that can be so singular(grain) into fm maddness unquantized of it seems easier

Hi! I'm on a Mac running macOS Monterey, with an Intel Core i7 processor.

When I ran $ make program-dfu I got the following error:

dfu-util -a 0 -s 0x08000000:leave -D build/harmonic_osc.bin -d ,0483:df11
dyld[3956]: Library not loaded: '/usr/local/opt/libusb/lib/libusb-1.0.0.dylib'
  Referenced from: '/Library/DaisyToolchain/0.1.2/bin/dfu-util'
  Reason: tried: '/usr/local/opt/libusb/lib/libusb-1.0.0.dylib' (no such file), '/usr/local/lib/libusb
-1.0.0.dylib' (no such file), '/usr/lib/libusb-1.0.0.dylib' (no such file)
make: *** [program-dfu] Abort trap: 6

I was able to resolve it by re-installing and linking dfu-util:

$ brew install dfu-util
$ brew link --overwrite dfu-util

Happy to open a PR to add this to the Troubleshooting section if that would be helpful.

On the Oopsy getting started page, the link used for downloading the Oopsy zip https://github.com/electro-smith/oopsy/releases/latest/download/oopsy.zip results in a "Not Found" error.

The reason is that the actual zip isn't named oopsy.zip. It also has the versioning in the name, so just using the latest URL isn't sufficient to automatically track the latest release. Probably just a link to the latest release page is the way to go.

The schematics will help to design external power source and power external components from the Seed's +3.3V analog and digital pins.

Working on this
** https://github.com/electro-smith/DaisyWiki/wiki/1.-Setting-Up-Your-Development-Environment **

I am at this step 4. Run the Blink Example and running into some errors . My dev environment is this.

  Model Name:	Mac Pro
  Model Identifier:	MacPro6,1
  Processor Name:	Quad-Core Intel Xeon E5
  Processor Speed:	3.7 GHz

VSCODE Version: 1.56.2

It looks like I need a gcc compiler that targets the processor.

I am going to try this :

https://brewinstall.org/install-gcc-arm-embedded-mac-osx/

I hope it's cool to create an issue I would like to keep track of it all here.

Executing task: make clean; make <

rm -fR build
mkdir build
arm-none-eabi-gcc -c -mcpu=cortex-m7 -mthumb -mfpu=fpv5-d16 -mfloat-abi=hard -DUSE_HAL_DRIVER -DSTM32H750xx -DHSE_VALUE=16000000 -DCORE_CM7 -DSTM32H750IB -DARM_MATH_CM7 -DUSE_FULL_LL_DRIVER -include stm32h7xx.h -I../../libdaisy -I../../libdaisy/src/ -I../../libdaisy/src/sys -I../../libdaisy/src/usbd -I../../libdaisy/Drivers/CMSIS/Include/ -I../../libdaisy/Drivers/CMSIS/DSP/Include -I../../libdaisy/Drivers/CMSIS/Device/ST/STM32H7xx/Include -I../../libdaisy/Drivers/STM32H7xx_HAL_Driver/Inc/ -I../../libdaisy/Middlewares/ST/STM32_USB_Device_Library/Core/Inc -I../../libdaisy/core/ -I../../DaisySP/Source -I../../libdaisy/Middlewares/Third_Party/FatFs/src -O2 -Wall -Wno-missing-attributes -fasm -fdata-sections -ffunction-sections -MMD -MP -MF"build/startup_stm32h750xx.d" -std=gnu11 -Wa,-a,-ad,-alms=build/startup_stm32h750xx.lst ../../libdaisy/core/startup_stm32h750xx.c -o build/startup_stm32h750xx.o
arm-none-eabi-gcc: fatal error: cannot execute 'cc1': execvp: No such file or directory
compilation terminated.
make: *** [build/startup_stm32h750xx.o] Error 1
The terminal process "/bin/bash '-c', 'make clean; make'" terminated with exit code: 2.

hi

d2dsy_gui.exe is nowhere to be found

the link in the zip file will certainly not work since I have no corvus user

C:\Users\corvus\Documents\GitHub\pd2dsy\dist\pd2dsyGUI\data\pd2dsy_gui.exe

do you even check what you upload ?

As a complete beginner I was following this tutorial and discovered that there is no json file or preset to export a simple gen patch to the daisy seed.
In my case I have a single sine wave which goes to outputs 1 and 2, after trying all the available modes like field, pedal, pod I didn't get anything to work.

Is there something that I'm missing on the wiki or anywhere else on how to get sound out of the daisy seed from an exported gen patch?

Installing toolchain on macOS Monterey 12.3.1. Ran the install.command. Homebrew upgraded and added a bunch of new casks, but it couldn't locate gcc-arm-embedded

Error: Cask 'gcc-arm-embedded' is unavailable: No Cask with this name exists.
find: /usr/local/Caskroom/gcc-arm-embedded: No such file or directory
find: /usr/local/Caskroom/gcc-arm-embedded: No such file or directory

Any ideas? Sorry if this is too general of a Homebrew question for this project.

https://github.com/electro-smith/DaisyWiki/wiki/1d.-Installing-the-Toolchain-on-Linux#arm-toolchain

The code is written for the version 9:

GCC_PATH=~/Developer/gcc-arm-none-eabi-9-2020-q2-update/bin
export PATH=$GCC_PATH:$PATH

But the folder/path from the tar file should be:

GCC_PATH=~/Developer/gcc-arm-none-eabi-10-2020-q4-major/bin
export PATH=$GCC_PATH:$PATH

As it was recommended for version 10-2020-q4-major

You can ignore the "This page is deprecated" message at the top of the website. Please scroll down and we recommend that you click on "Downloads: 10-2020-q4-major December 11 2020" and install "gcc-arm-none-eabi-10-2020-q4-major-x86_64-linux.tar.bz2".

This led to a bit of confusion when I just copied and pasted the whole thing from the wiki.

Hello,

I am trying to update my toolchain and I wanted to check as I had the older toolchain install and it is working, but will the two work together well? Moreover, will it clean up the old toolchain when this installs?

Thanks,
Brett

Hi,

I am loking at your toolchain install instructions and there are two areas that could use a little more info:

1. Where you ask people to setup the environment variables:
   a) CYWGIN - what should the env variable be? (I assume cywgin but it is not clear from the docs)
   b) GNU tools - if I missed checking the box, what should the evn variable be?
   c) dfu-util - what should the env variable be? (I assume dfu-util, but it is not clear from the docs)

2. How do I unpact the dfu-util
   When I go to the link it shows a .tar.xz?
   I have not been on a Linux system for some time, I've been coding Windows for a while, how do I unpack a tar.xz file?

first of all there's a typo in the text: "Shift+⌘+P on macOS" should loose the Shift

in terms of using a STLINK-V3MINIE, as currently sold, with M1 (and possibly all Apple Silicon) Macs, see:

https://forum.electro-smith.com/t/stlink-v3-mini-cant-program-or-debug-anymore-anymore/5039/8

Great setup guide, it's worked like a charm (on PC). Only small thing I saw:
At https://github.com/electro-smith/DaisyWiki/wiki/How-To-Create-a-New-Project
in step 4 it says to refer to step "3" of the dev env guide. That should be "4"

Also, in setting up the dev env the first time I needed to "Build all" it did not work because there were some "makefile extensions that weren't installed yet. I missed the pop-up the first time through.

going back to learning DSP now :D

The troubleshooting section for Oopsy refers to DISCREET and VERBOSE buttons, which I assume have just been replaced with the Quiet button.

When clicking on the 'Zadig wiki page' link - it passes to the same DaisyWiki home page.
Therefore I'm unable to get the information about updating the USB driver.
My Daisy is not visible as "DFU in FS Mode" in the web programmer.

I'm in the process of trying to flash the Daisy with the Blink example. I've got the Daisy in DFU mode but dfu-util cannot access the device. It also cannot open the device when trying to list the devices using just dfu-util.

If I reset the Daisy out of DFU mode, it simply states that "No DFU capable USB device available". Are there some Windows 10 drivers that I need in order for this to work?

EDIT: Under Bluetooth & other devices, the Daisy shows up as "DFU in FS Mode" when entering DFU mode.

Output:
monke@FOLDINGTREE /cygdrive/c/users/monke/desktop/daisy/DaisyExamples/seed/blink
$ make program-dfu
dfu-util -a 0 -s 0x08000000:leave -D build/Blink.bin
dfu-util 0.9

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

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

hey! thanks for all your work on this. I noticed a typo that might throw some users off - the master enable command in the mac toolchain setup was missing a dash. fixed it below but can't PR to the wiki.

sudo spctl --master-enable

thanks!

It would appear that the STM32 Arduino Core is dropping support for the V1 IDE, but the documentation doesn't talk about any of that yet - the STM32Duino getting started guide still shows V1 screenshots for example. More here: stm32duino/Arduino_Core_STM32#2416

It might be worth a note on your own wiki that Arduino V2 is required from now on.

I've just spent the afternoon attempting to debug why my V1 installation is having problems, and this appears to be the reason unfortunately. Installing V2 will have to wait for another day now, so getting my new Daisy Seed to blink will have to wait a bit longer! :)

Best wishes,
Kevin

I was looking at the pinout and noticed two UARTS1 and one USART3 but no USART2
Is there an error on this pinout ?

All the best, Brock

https://github.com/electro-smith/DaisyWiki/wiki/1d.-Installing-the-Toolchain-on-Linux

gcc-arm-none-eabi-9-2020-q2-update is the latest
update docs ?

Toolchain install for Linux should be revised and improved due to version mismatch.

I feel like the title says it all, but neither of the Mac builds of pd2dsy have an executable application in. The Apple Silicon versions dont contain the file at all, whereas the intel version does contain a file, but it's a shortcut that is not runnable.

In the pinout sheets, it states that pin 20 is AGND and that the audio in/out pins are 16-19. The PNG shows the audio in/out pins are 17-20.

From the sheets:
16 | AUDIO IN L
17 | AUDIO INR
18 | AUDIO OUT L
19 | AUDIO OUT R
20 | AGND