Pure Data

Ah thanks.

But 8 month since it was supposed to be available, the script.

Yeah Bela is nice. I already have one, but this Daisy thing was ment for a Eurorack project that I was going to help some friends with. And it’s a bit frustrating that the script that we were told would be available, is still not available.

But yeah Bela, it’s nice. I have no idea what NEON SIMD is, sorry. I am just using it with Pure Data and it’s really simple to use. Make your patch on computer, drop it into the IDE, push “Run” and you have an up and running instrument.

I don’t mind doing a bit more work than that for Daisy, but the script was supposed to be for less code savy people, to make it easier to use. And I think also having a system which is very easy to use, will also sell more units as more people can use it.

The Max Msp thing. First I thought it was a great idea. But then start to think about it’s a paid software. So either you have to buy a pretty expensive piece of software or you have to rent it. Not too happy about adding extra expenses by having to buy/rent Max.

I just think open source like PD, goes better hand in hand with Daisy than Max does, cause Daisy is also open source. But yeah, I don’t see any reason why we can’t have both of course, but I am a bit bummed that the Daisy script is stil not here, so long time after it was supposed to be available.

1 Like

What’s the actual problem with current pd2dsy? They have a definition for seed board too, are you sure that it doesn’t work?

Besides that, sounds like you’ll have to understand how to define a custom board for libDaisy and integrate it to py2dsy or that fork of HVCC if you want to use it for a custom module.

There was supposed to be support for Daisy seed. Last time I checked it wasn’t there. And I just checked the thread here today, and there was no mention of any updates, so I kind of assumes it has not changed?

But those things you mention. They should be part of the PD>Daisy script, no?

The first post of this topic says:

I am just trying to follow up on it, cause this is what we were told. That was 14 month ago.

My develop branch of heavy now supports Daisy generator, this makes it much easier to compile the patch (and you can import hvcc as a lib in your own python3 code if you want).

Example patches are reported to work, but definitely needs some more testing. I hope to have some daisy hw soon-ish

Need to clean up some DPF bits and settle on the metafile.json structure (that is, among other things, used for specifying which Daisy board you want to compile to) and then try to release a v0.2.0 to pypi.org

Very open to contributions/help with pushing heavy/hvcc forward :slight_smile:

1 Like

Example how to build for seed: hvcc/examples/daisy at develop · Wasted-Audio/hvcc · GitHub

However next-gen the idea is to add custom board definitions. Daisy team is still working out the details, but for now this hopefully can get you going.

1 Like

Thanks, I will give it a go next weekend :slight_smile:

Last day of holiday today. Sooo much to do before starting again.

Have a nice Sunday :wink:

Hi @Jaffasplaffa

Apologies on the lack of updates here on the Pure Data thread over the past few months.

Some of the pieces of the integration have ended up taking a bit more time than we originally anticipated, but we have made some good progress, and are still working hard to make it all happen!

Here are just a few notes about the state of the Pure Data integration, and where we’re at in supporting it.

We’ve been working on a new flash loader that allows using larger programs (as the binaries generated from pure data can end up being pretty large), and allowing the use of the external SDRAM for extra memory. This ended up taking a bit longer than we originally anticipated, but it is now in the review stages, and seems to be working to use large amounts of data, and to run programs with more objects.

In order to support custom hardware (i.e. Daisy Seed with custom interface elements attached), we needed to come up with some sort of metadata format that would allow for mapping parameters in pure data to various controls connected to the Daisy. This has seem some good progress, and we’re working to make that a universal format that can work for the other integrations as well. It was just added into the latest commits on the oopsy support for Max/MSP gen~, and will be making it’s way into our current pd2dsy implementation as soon as possible.

For the user, this will be a simple .json file that will define the hardware mapping. For example, here is what it might look like if you were going to mirror the Daisy Pod:

{
	"name":"pod",
	"components": {
		"sw1": {
			"component": "Switch",
			"pin": 27
		},
		"sw2": {
			"component": "Switch",
			"pin": 28
		},
		"knob1": {
			"component": "AnalogControl",
			"pin": 21
		},
		"knob2": {
			"component": "AnalogControl",
			"pin": 15
		},
		"encoder": {
			"component": "Encoder",
			"pin": {"a":26, "b":25, "click":13 }
		},
		"led1": {
			"component": "RgbLed",
			"pin": {"r":20, "g":19, "b":18 }
		},
		"led2": {
			"component": "RgbLed",
			"pin": {"r":17, "g":24, "b":23 }
		}
	}
}

This json file will likely be able to get passed into the pd2dsy script the same way you would select one of the other boards (i.e. python pd2dsy.py --board MyCustomBoard.json project.pd)

Pending any unexpected hang ups we’re hoping to be wrapping up both of these changes into pd2dsy very shortly.

As @dreamer mentioned, he’s been leading the charge on integrating the Daisy directly into the revived version of hvcc that runs with python3. This does seem to be working great right now, and we’ll be working with him to integrate the changes mentioned above into that platform as we progress.

We’ll post more regular updates here as we continue to progress.

2 Likes

re. large binary size of pd patches:

There are some ideas to get [expr] objects working, then we can hopefully optimize some of the internal hvcc objects which could save some of the size of these builds (won’t be coming any time soon, but I’m sure this is something that would benefit everyone).

1 Like

@ shensley

Thank you so much for the update. I am so happy to hear something is still happening, regarding the PD>Daisy script, cause it’s been a while now.

I did not want to create any fuzz, I just wanted to know that the PD approach was still in the works.

And I think spending time on being able to load patches to the SDram, is super important, so any time spend on that is well spend time :slight_smile:

I will keep an eye out for any progress.

Thanks for the feedback!

Hi. I’m new to Daisy and new on the forum here, I have a few Seeds on their way to me, very excited! PD is my tool so I’m hoping I can get my patches working on the Seed.

I wondered if there was any update on the forthcoming script as outlined in this thread and also wanted to know should I be using the original hvcc with Python 2.7 or dreamer’s updated version for the latest Python? (python is new to me as is most of the process for compiling a PD patch for Daisy). Any assistance for a newbie most appreciated.

Thank-you,
crewdson

Hi. I’ve been following the steps to get set up with pd2dsy and have successfully (I think?!) managed to compile a PD patch and can see that a new folder has been created with the ‘.h .cpp and makefile’ files as well as ‘c hv build and ir’ folders.

I then try and flash to my seed using ‘make program-dfu’ in terminal and get the below.

Can anyone tell me what my issue is?
I’m using the ‘saw_test’ example here to avoid any pure data object issues whilst i sort this problem out
Many thanks

Hughs-MacBook-Pro-2:~ Crewdson$ cd pd2dsy/saw_test
Hughs-MacBook-Pro-2:saw_test Crewdson$ make
make: Nothing to be done for `all'.
Hughs-MacBook-Pro-2:saw_test Crewdson$ make program-dfu
dfu-util -a 0 -s 0x08000000:leave -D build/saw_test.bin -d 0483:df11
dfu-util 0.11

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2021 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/

dfu-util: Warning: Invalid DFU suffix signature
dfu-util: A valid DFU suffix will be required in a future dfu-util release
Deducing device DFU version from functional descriptor length
Opening DFU capable USB device...
Device ID 0483:df11
Device DFU version 011a
Claiming USB DFU Interface...
Setting Alternate Interface #0 ...
Determining device status...
DFU state(2) = dfuIDLE, status(0) = No error condition is present
DFU mode device DFU version 011a
Device returned transfer size 1024
DfuSe interface name: "Internal Flash   "
Downloading element to address = 0x08000000, size = 62052
Erase   	[=========================] 100%        62052 bytes
Erase    done.
Download	[=========================] 100%        62052 bytes
Download done.
File downloaded successfully
Submitting leave request...
dfu-util: Error during download get_status
make: *** [program-dfu] Error 74

I believe that error number 74 is a red herring explained here: Make program-dfu error - #4 by shensley (look at or near the end of the thread for the explanation) I think everything should be working, despite the error.

Regards,
John

@jcgriggs is absolutely right. This error is a part of the tool used to flash the daisy, and is unfortunately unavoidable, but it is nothing to worry about.

Re. the newer version of the script (that handles compilation, etc. as well as fully supported custom JSON) should be wrapped up in the next few weeks. It’s mostly undergoing testing at this point.

@jcgriggs @shensley many thanks to both of you, that is great news on both counts. in which case i’ll get breadboarding and see what input control and output of sound i can muster.

will be great to get the new script when it’s ready, thanks for your continuing work on that

thank-you!

Hi. I have an issue where I’m seemingly able to get my PD patch successfully compiled and then flashed to my seed but the audio that is coming out is corrupted.

There is a loud high pitched tone (that isn’t supposed to be there) along with the output of my patch playing quietly underneath it. This plays out of the speaker when the speaker is connected to both of the Audio out pins (18, 19) but also weirdly the Audio In pins (16,17). This made me think I had connected things wrongly on the breadboard but when I flash one of the Seed_DSP example patches from the Web Programmer the sound comes out perfectly.

I’m stumped! Any ideas??
Thanks in advance

Here is what I get in Terminal when I run ‘make’ and then ‘make program-dfu’:

Hughs-MacBook-Pro-2:tone_generator_seq Crewdson$ make
mkdir build
arm-none-eabi-gcc -c -mcpu=cortex-m7 -mthumb -mfpu=fpv5-d16 -mfloat-abi=hard  -DUSE_HAL_DRIVER -DSTM32H750xx -DUSE_HAL_DRIVER -DHSE_VALUE=16000000 -DSTM32H750xx -Ic/ -I../libdaisy -I../libdaisy/src/ -I../libdaisy/Drivers/CMSIS/Include/ -I../libdaisy/Drivers/CMSIS/Device/ST/STM32H7xx/Include -I../libdaisy/Drivers/STM32H7xx_HAL_Driver/Inc/ -I../libdaisy/core/ -I  -O2 -Wall -Wno-missing-attributes -fasm -fdata-sections -ffunction-sections -MMD -MP -MF"build/HvControlBinop.d" -std=gnu11 -Wa,-a,-ad,-alms=build/HvControlBinop.lst c/HvControlBinop.c -o build/HvControlBinop.o
In file included from c/HvHeavy.h:20,
                 from c/HvHeavyInternal.h:20,
                 from c/HvControlBinop.h:20,
                 from c/HvControlBinop.c:17:
c/HvUtils.h:33:4: warning: #warning Could not detect platform. Assuming Unix-like. [-Wcpp]
   33 |   #warning Could not detect platform. Assuming Unix-like.
      |    ^~~~~~~
arm-none-eabi-gcc -c -mcpu=cortex-m7 -mthumb -mfpu=fpv5-d16 -mfloat-abi=hard  -DUSE_HAL_DRIVER -DSTM32H750xx -DUSE_HAL_DRIVER -DHSE_VALUE=16000000 -DSTM32H750xx -Ic/ -I../libdaisy -I../libdaisy/src/ -I../libdaisy/Drivers/CMSIS/Include/ -I../libdaisy/Drivers/CMSIS/Device/ST/STM32H7xx/Include -I../libdaisy/Drivers/STM32H7xx_HAL_Driver/Inc/ -I../libdaisy/core/ -I  -O2 -Wall -Wno-missing-attributes -fasm -fdata-sections -ffunction-sections -MMD -MP -MF"build/HvControlCast.d" -std=gnu11 -Wa,-a,-ad,-alms=build/HvControlCast.lst c/HvControlCast.c -o build/HvControlCast.o
In file included from c/HvHeavy.h:20,
                 from c/HvHeavyInternal.h:20,
                 from c/HvControlCast.h:20,
                 from c/HvControlCast.c:17:
c/HvUtils.h:33:4: warning: #warning Could not detect platform. Assuming Unix-like. [-Wcpp]
   33 |   #warning Could not detect platform. Assuming Unix-like.
      |    ^~~~~~~
arm-none-eabi-gcc -c -mcpu=cortex-m7 -mthumb -mfpu=fpv5-d16 -mfloat-abi=hard  -DUSE_HAL_DRIVER -DSTM32H750xx -DUSE_HAL_DRIVER -DHSE_VALUE=16000000 -DSTM32H750xx -Ic/ -I../libdaisy -I../libdaisy/src/ -I../libdaisy/Drivers/CMSIS/Include/ -I../libdaisy/Drivers/CMSIS/Device/ST/STM32H7xx/Include -I../libdaisy/Drivers/STM32H7xx_HAL_Driver/Inc/ -I../libdaisy/core/ -I  -O2 -Wall -Wno-missing-attributes -fasm -fdata-sections -ffunction-sections -MMD -MP -MF"build/HvControlDelay.d" -std=gnu11 -Wa,-a,-ad,-alms=build/HvControlDelay.lst c/HvControlDelay.c -o build/HvControlDelay.o
In file included from c/HvHeavy.h:20,
                 from c/HvHeavyInternal.h:20,
                 from c/HvControlDelay.h:22,
                 from c/HvControlDelay.c:17:
c/HvUtils.h:33:4: warning: #warning Could not detect platform. Assuming Unix-like. [-Wcpp]
   33 |   #warning Could not detect platform. Assuming Unix-like.
      |    ^~~~~~~
arm-none-eabi-gcc -c -mcpu=cortex-m7 -mthumb -mfpu=fpv5-d16 -mfloat-abi=hard  -DUSE_HAL_DRIVER -DSTM32H750xx -DUSE_HAL_DRIVER -DHSE_VALUE=16000000 -DSTM32H750xx -Ic/ -I../libdaisy -I../libdaisy/src/ -I../libdaisy/Drivers/CMSIS/Include/ -I../libdaisy/Drivers/CMSIS/Device/ST/STM32H7xx/Include -I../libdaisy/Drivers/STM32H7xx_HAL_Driver/Inc/ -I../libdaisy/core/ -I  -O2 -Wall -Wno-missing-attributes -fasm -fdata-sections -ffunction-sections -MMD -MP -MF"build/HvControlSystem.d" -std=gnu11 -Wa,-a,-ad,-alms=build/HvControlSystem.lst c/HvControlSystem.c -o build/HvControlSystem.o
In file included from c/HvHeavy.h:20,
                 from c/HvHeavyInternal.h:20,
                 from c/HvControlSystem.h:20,
                 from c/HvControlSystem.c:17:
c/HvUtils.h:33:4: warning: #warning Could not detect platform. Assuming Unix-like. [-Wcpp]
   33 |   #warning Could not detect platform. Assuming Unix-like.
      |    ^~~~~~~
arm-none-eabi-gcc -c -mcpu=cortex-m7 -mthumb -mfpu=fpv5-d16 -mfloat-abi=hard  -DUSE_HAL_DRIVER -DSTM32H750xx -DUSE_HAL_DRIVER -DHSE_VALUE=16000000 -DSTM32H750xx -Ic/ -I../libdaisy -I../libdaisy/src/ -I../libdaisy/Drivers/CMSIS/Include/ -I../libdaisy/Drivers/CMSIS/Device/ST/STM32H7xx/Include -I../libdaisy/Drivers/STM32H7xx_HAL_Driver/Inc/ -I../libdaisy/core/ -I  -O2 -Wall -Wno-missing-attributes -fasm -fdata-sections -ffunction-sections -MMD -MP -MF"build/HvControlVar.d" -std=gnu11 -Wa,-a,-ad,-alms=build/HvControlVar.lst c/HvControlVar.c -o build/HvControlVar.o
In file included from c/HvHeavy.h:20,
                 from c/HvHeavyInternal.h:20,
                 from c/HvControlVar.h:20,
                 from c/HvControlVar.c:17:
c/HvUtils.h:33:4: warning: #warning Could not detect platform. Assuming Unix-like. [-Wcpp]
   33 |   #warning Could not detect platform. Assuming Unix-like.
      |    ^~~~~~~
arm-none-eabi-gcc -c -mcpu=cortex-m7 -mthumb -mfpu=fpv5-d16 -mfloat-abi=hard  -DUSE_HAL_DRIVER -DSTM32H750xx -DUSE_HAL_DRIVER -DHSE_VALUE=16000000 -DSTM32H750xx -Ic/ -I../libdaisy -I../libdaisy/src/ -I../libdaisy/Drivers/CMSIS/Include/ -I../libdaisy/Drivers/CMSIS/Device/ST/STM32H7xx/Include -I../libdaisy/Drivers/STM32H7xx_HAL_Driver/Inc/ -I../libdaisy/core/ -I  -O2 -Wall -Wno-missing-attributes -fasm -fdata-sections -ffunction-sections -MMD -MP -MF"build/HvLightPipe.d" -std=gnu11 -Wa,-a,-ad,-alms=build/HvLightPipe.lst c/HvLightPipe.c -o build/HvLightPipe.o
In file included from c/HvLightPipe.h:20,
                 from c/HvLightPipe.c:17:
c/HvUtils.h:33:4: warning: #warning Could not detect platform. Assuming Unix-like. [-Wcpp]
   33 |   #warning Could not detect platform. Assuming Unix-like.
      |    ^~~~~~~
arm-none-eabi-gcc -c -mcpu=cortex-m7 -mthumb -mfpu=fpv5-d16 -mfloat-abi=hard  -DUSE_HAL_DRIVER -DSTM32H750xx -DUSE_HAL_DRIVER -DHSE_VALUE=16000000 -DSTM32H750xx -Ic/ -I../libdaisy -I../libdaisy/src/ -I../libdaisy/Drivers/CMSIS/Include/ -I../libdaisy/Drivers/CMSIS/Device/ST/STM32H7xx/Include -I../libdaisy/Drivers/STM32H7xx_HAL_Driver/Inc/ -I../libdaisy/core/ -I  -O2 -Wall -Wno-missing-attributes -fasm -fdata-sections -ffunction-sections -MMD -MP -MF"build/HvMessage.d" -std=gnu11 -Wa,-a,-ad,-alms=build/HvMessage.lst c/HvMessage.c -o build/HvMessage.o
In file included from c/HvMessage.h:20,
                 from c/HvMessage.c:17:
c/HvUtils.h:33:4: warning: #warning Could not detect platform. Assuming Unix-like. [-Wcpp]
   33 |   #warning Could not detect platform. Assuming Unix-like.
      |    ^~~~~~~
In file included from c/HvMessage.h:20,
                 from c/HvMessage.c:17:
c/HvMessage.c: In function 'msg_toString':
c/HvMessage.c:172:55: warning: format '%X' expects argument of type 'unsigned int', but argument 4 has type 'uint32_t' {aka 'long unsigned int'} [-Wformat=]
  172 |       case HV_MSG_HASH: len[i] = hv_snprintf(NULL, 0, "0x%X", msg_getHash(m, i)) + 1; break;
      |                                                       ^~~~~~  ~~~~~~~~~~~~~~~~~
      |                                                               |
      |                                                               uint32_t {aka long unsigned int}
c/HvUtils.h:131:50: note: in definition of macro 'hv_snprintf'
  131 | #define hv_snprintf(a, b, c, ...) snprintf(a, b, c, __VA_ARGS__)
      |                                                  ^
c/HvMessage.c:172:59: note: format string is defined here
  172 |       case HV_MSG_HASH: len[i] = hv_snprintf(NULL, 0, "0x%X", msg_getHash(m, i)) + 1; break;
      |                                                          ~^
      |                                                           |
      |                                                           unsigned int
      |                                                          %lX
In file included from c/HvMessage.h:20,
                 from c/HvMessage.c:17:
c/HvMessage.c:191:62: warning: format '%X' expects argument of type 'unsigned int', but argument 4 has type 'uint32_t' {aka 'long unsigned int'} [-Wformat=]
  191 |       case HV_MSG_HASH: hv_snprintf(finalString+pos, len[i], "0x%X", msg_getHash(m, i)); break;
      |                                                              ^~~~~~  ~~~~~~~~~~~~~~~~~
      |                                                                      |
      |                                                                      uint32_t {aka long unsigned int}
c/HvUtils.h:131:50: note: in definition of macro 'hv_snprintf'
  131 | #define hv_snprintf(a, b, c, ...) snprintf(a, b, c, __VA_ARGS__)
      |                                                  ^
c/HvMessage.c:191:66: note: format string is defined here
  191 |       case HV_MSG_HASH: hv_snprintf(finalString+pos, len[i], "0x%X", msg_getHash(m, i)); break;
      |                                                                 ~^
      |                                                                  |
      |                                                                  unsigned int
      |                                                                 %lX
arm-none-eabi-gcc -c -mcpu=cortex-m7 -mthumb -mfpu=fpv5-d16 -mfloat-abi=hard  -DUSE_HAL_DRIVER -DSTM32H750xx -DUSE_HAL_DRIVER -DHSE_VALUE=16000000 -DSTM32H750xx -Ic/ -I../libdaisy -I../libdaisy/src/ -I../libdaisy/Drivers/CMSIS/Include/ -I../libdaisy/Drivers/CMSIS/Device/ST/STM32H7xx/Include -I../libdaisy/Drivers/STM32H7xx_HAL_Driver/Inc/ -I../libdaisy/core/ -I  -O2 -Wall -Wno-missing-attributes -fasm -fdata-sections -ffunction-sections -MMD -MP -MF"build/HvMessagePool.d" -std=gnu11 -Wa,-a,-ad,-alms=build/HvMessagePool.lst c/HvMessagePool.c -o build/HvMessagePool.o
In file included from c/HvMessagePool.h:20,
                 from c/HvMessagePool.c:17:
c/HvUtils.h:33:4: warning: #warning Could not detect platform. Assuming Unix-like. [-Wcpp]
   33 |   #warning Could not detect platform. Assuming Unix-like.
      |    ^~~~~~~
arm-none-eabi-gcc -c -mcpu=cortex-m7 -mthumb -mfpu=fpv5-d16 -mfloat-abi=hard  -DUSE_HAL_DRIVER -DSTM32H750xx -DUSE_HAL_DRIVER -DHSE_VALUE=16000000 -DSTM32H750xx -Ic/ -I../libdaisy -I../libdaisy/src/ -I../libdaisy/Drivers/CMSIS/Include/ -I../libdaisy/Drivers/CMSIS/Device/ST/STM32H7xx/Include -I../libdaisy/Drivers/STM32H7xx_HAL_Driver/Inc/ -I../libdaisy/core/ -I  -O2 -Wall -Wno-missing-attributes -fasm -fdata-sections -ffunction-sections -MMD -MP -MF"build/HvMessageQueue.d" -std=gnu11 -Wa,-a,-ad,-alms=build/HvMessageQueue.lst c/HvMessageQueue.c -o build/HvMessageQueue.o
In file included from c/HvMessage.h:20,
                 from c/HvMessageQueue.h:20,
                 from c/HvMessageQueue.c:17:
c/HvUtils.h:33:4: warning: #warning Could not detect platform. Assuming Unix-like. [-Wcpp]
   33 |   #warning Could not detect platform. Assuming Unix-like.
      |    ^~~~~~~
arm-none-eabi-gcc -c -mcpu=cortex-m7 -mthumb -mfpu=fpv5-d16 -mfloat-abi=hard  -DUSE_HAL_DRIVER -DSTM32H750xx -DUSE_HAL_DRIVER -DHSE_VALUE=16000000 -DSTM32H750xx -Ic/ -I../libdaisy -I../libdaisy/src/ -I../libdaisy/Drivers/CMSIS/Include/ -I../libdaisy/Drivers/CMSIS/Device/ST/STM32H7xx/Include -I../libdaisy/Drivers/STM32H7xx_HAL_Driver/Inc/ -I../libdaisy/core/ -I  -O2 -Wall -Wno-missing-attributes -fasm -fdata-sections -ffunction-sections -MMD -MP -MF"build/HvSignalPhasor.d" -std=gnu11 -Wa,-a,-ad,-alms=build/HvSignalPhasor.lst c/HvSignalPhasor.c -o build/HvSignalPhasor.o
In file included from c/HvHeavy.h:20,
                 from c/HvHeavyInternal.h:20,
                 from c/HvSignalPhasor.h:20,
                 from c/HvSignalPhasor.c:17:
c/HvUtils.h:33:4: warning: #warning Could not detect platform. Assuming Unix-like. [-Wcpp]
   33 |   #warning Could not detect platform. Assuming Unix-like.
      |    ^~~~~~~
arm-none-eabi-gcc -c -mcpu=cortex-m7 -mthumb -mfpu=fpv5-d16 -mfloat-abi=hard  -DUSE_HAL_DRIVER -DSTM32H750xx -DUSE_HAL_DRIVER -DHSE_VALUE=16000000 -DSTM32H750xx -Ic/ -I../libdaisy -I../libdaisy/src/ -I../libdaisy/Drivers/CMSIS/Include/ -I../libdaisy/Drivers/CMSIS/Device/ST/STM32H7xx/Include -I../libdaisy/Drivers/STM32H7xx_HAL_Driver/Inc/ -I../libdaisy/core/ -I  -O2 -Wall -Wno-missing-attributes -fasm -fdata-sections -ffunction-sections -MMD -MP -MF"build/HvSignalVar.d" -std=gnu11 -Wa,-a,-ad,-alms=build/HvSignalVar.lst c/HvSignalVar.c -o build/HvSignalVar.o
In file included from c/HvHeavy.h:20,
                 from c/HvHeavyInternal.h:20,
                 from c/HvSignalVar.h:20,
                 from c/HvSignalVar.c:17:
c/HvUtils.h:33:4: warning: #warning Could not detect platform. Assuming Unix-like. [-Wcpp]
   33 |   #warning Could not detect platform. Assuming Unix-like.
      |    ^~~~~~~
arm-none-eabi-gcc -c -mcpu=cortex-m7 -mthumb -mfpu=fpv5-d16 -mfloat-abi=hard  -DUSE_HAL_DRIVER -DSTM32H750xx -DUSE_HAL_DRIVER -DHSE_VALUE=16000000 -DSTM32H750xx -Ic/ -I../libdaisy -I../libdaisy/src/ -I../libdaisy/Drivers/CMSIS/Include/ -I../libdaisy/Drivers/CMSIS/Device/ST/STM32H7xx/Include -I../libdaisy/Drivers/STM32H7xx_HAL_Driver/Inc/ -I../libdaisy/core/ -I  -O2 -Wall -Wno-missing-attributes -fasm -fdata-sections -ffunction-sections -MMD -MP -MF"build/HvTable.d" -std=gnu11 -Wa,-a,-ad,-alms=build/HvTable.lst c/HvTable.c -o build/HvTable.o
In file included from c/HvHeavy.h:20,
                 from c/HvTable.h:20,
                 from c/HvTable.c:17:
c/HvUtils.h:33:4: warning: #warning Could not detect platform. Assuming Unix-like. [-Wcpp]
   33 |   #warning Could not detect platform. Assuming Unix-like.
      |    ^~~~~~~
arm-none-eabi-gcc -c -mcpu=cortex-m7 -mthumb -mfpu=fpv5-d16 -mfloat-abi=hard  -DUSE_HAL_DRIVER -DSTM32H750xx -DUSE_HAL_DRIVER -DHSE_VALUE=16000000 -DSTM32H750xx -Ic/ -I../libdaisy -I../libdaisy/src/ -I../libdaisy/Drivers/CMSIS/Include/ -I../libdaisy/Drivers/CMSIS/Device/ST/STM32H7xx/Include -I../libdaisy/Drivers/STM32H7xx_HAL_Driver/Inc/ -I../libdaisy/core/ -I  -O2 -Wall -Wno-missing-attributes -fasm -fdata-sections -ffunction-sections -MMD -MP -MF"build/HvUtils.d" -std=gnu11 -Wa,-a,-ad,-alms=build/HvUtils.lst c/HvUtils.c -o build/HvUtils.o
In file included from c/HvUtils.c:17:
c/HvUtils.h:33:4: warning: #warning Could not detect platform. Assuming Unix-like. [-Wcpp]
   33 |   #warning Could not detect platform. Assuming Unix-like.
      |    ^~~~~~~
arm-none-eabi-gcc -c -mcpu=cortex-m7 -mthumb -mfpu=fpv5-d16 -mfloat-abi=hard  -DUSE_HAL_DRIVER -DSTM32H750xx -DUSE_HAL_DRIVER -DHSE_VALUE=16000000 -DSTM32H750xx -Ic/ -I../libdaisy -I../libdaisy/src/ -I../libdaisy/Drivers/CMSIS/Include/ -I../libdaisy/Drivers/CMSIS/Device/ST/STM32H7xx/Include -I../libdaisy/Drivers/STM32H7xx_HAL_Driver/Inc/ -I../libdaisy/core/ -I  -O2 -Wall -Wno-missing-attributes -fasm -fdata-sections -ffunction-sections -MMD -MP -MF"build/system_stm32h7xx.d" -std=gnu11 -Wa,-a,-ad,-alms=build/system_stm32h7xx.lst ../libdaisy/core/system_stm32h7xx.c -o build/system_stm32h7xx.o
arm-none-eabi-gcc -c -mcpu=cortex-m7 -mthumb -mfpu=fpv5-d16 -mfloat-abi=hard  -DUSE_HAL_DRIVER -DSTM32H750xx -DUSE_HAL_DRIVER -DHSE_VALUE=16000000 -DSTM32H750xx -Ic/ -I../libdaisy -I../libdaisy/src/ -I../libdaisy/Drivers/CMSIS/Include/ -I../libdaisy/Drivers/CMSIS/Device/ST/STM32H7xx/Include -I../libdaisy/Drivers/STM32H7xx_HAL_Driver/Inc/ -I../libdaisy/core/ -I  -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-g++  -c -mcpu=cortex-m7 -mthumb -mfpu=fpv5-d16 -mfloat-abi=hard  -DUSE_HAL_DRIVER -DSTM32H750xx -DUSE_HAL_DRIVER -DHSE_VALUE=16000000 -DSTM32H750xx -Ic/ -I../libdaisy -I../libdaisy/src/ -I../libdaisy/Drivers/CMSIS/Include/ -I../libdaisy/Drivers/CMSIS/Device/ST/STM32H7xx/Include -I../libdaisy/Drivers/STM32H7xx_HAL_Driver/Inc/ -I../libdaisy/core/ -I  -O2 -Wall -Wno-missing-attributes -fasm -fdata-sections -ffunction-sections -MMD -MP -MF"build/HeavyContext.d" -fno-exceptions -fasm -finline -finline-functions-called-once -fshort-enums -fno-move-loop-invariants -fno-unwind-tables  -std=gnu++14 -Wa,-a,-ad,-alms=build/HeavyContext.lst c/HeavyContext.cpp -o build/HeavyContext.o
In file included from c/HeavyContextInterface.hpp:20,
                 from c/HeavyContext.hpp:20,
                 from c/HeavyContext.cpp:17:
c/HvUtils.h:33:4: warning: #warning Could not detect platform. Assuming Unix-like. [-Wcpp]
   33 |   #warning Could not detect platform. Assuming Unix-like.
      |    ^~~~~~~
arm-none-eabi-g++  -c -mcpu=cortex-m7 -mthumb -mfpu=fpv5-d16 -mfloat-abi=hard  -DUSE_HAL_DRIVER -DSTM32H750xx -DUSE_HAL_DRIVER -DHSE_VALUE=16000000 -DSTM32H750xx -Ic/ -I../libdaisy -I../libdaisy/src/ -I../libdaisy/Drivers/CMSIS/Include/ -I../libdaisy/Drivers/CMSIS/Device/ST/STM32H7xx/Include -I../libdaisy/Drivers/STM32H7xx_HAL_Driver/Inc/ -I../libdaisy/core/ -I  -O2 -Wall -Wno-missing-attributes -fasm -fdata-sections -ffunction-sections -MMD -MP -MF"build/Heavy_tone_generator_seq.d" -fno-exceptions -fasm -finline -finline-functions-called-once -fshort-enums -fno-move-loop-invariants -fno-unwind-tables  -std=gnu++14 -Wa,-a,-ad,-alms=build/Heavy_tone_generator_seq.lst c/Heavy_tone_generator_seq.cpp -o build/Heavy_tone_generator_seq.o
In file included from c/HeavyContextInterface.hpp:20,
                 from c/HeavyContext.hpp:20,
                 from c/Heavy_tone_generator_seq.hpp:37,
                 from c/Heavy_tone_generator_seq.cpp:33:
c/HvUtils.h:33:4: warning: #warning Could not detect platform. Assuming Unix-like. [-Wcpp]
   33 |   #warning Could not detect platform. Assuming Unix-like.
      |    ^~~~~~~
arm-none-eabi-g++  -c -mcpu=cortex-m7 -mthumb -mfpu=fpv5-d16 -mfloat-abi=hard  -DUSE_HAL_DRIVER -DSTM32H750xx -DUSE_HAL_DRIVER -DHSE_VALUE=16000000 -DSTM32H750xx -Ic/ -I../libdaisy -I../libdaisy/src/ -I../libdaisy/Drivers/CMSIS/Include/ -I../libdaisy/Drivers/CMSIS/Device/ST/STM32H7xx/Include -I../libdaisy/Drivers/STM32H7xx_HAL_Driver/Inc/ -I../libdaisy/core/ -I  -O2 -Wall -Wno-missing-attributes -fasm -fdata-sections -ffunction-sections -MMD -MP -MF"build/HvHeavy.d" -fno-exceptions -fasm -finline -finline-functions-called-once -fshort-enums -fno-move-loop-invariants -fno-unwind-tables  -std=gnu++14 -Wa,-a,-ad,-alms=build/HvHeavy.lst c/HvHeavy.cpp -o build/HvHeavy.o
In file included from c/HeavyContextInterface.hpp:20,
                 from c/HeavyContext.hpp:20,
                 from c/HvHeavy.cpp:17:
c/HvUtils.h:33:4: warning: #warning Could not detect platform. Assuming Unix-like. [-Wcpp]
   33 |   #warning Could not detect platform. Assuming Unix-like.
      |    ^~~~~~~
c/HvHeavy.cpp:24: warning: ignoring '#pragma mark ' [-Wunknown-pragmas]
   24 | #pragma mark - Heavy Table
      | 
c/HvHeavy.cpp:45: warning: ignoring '#pragma mark ' [-Wunknown-pragmas]
   45 | #pragma mark - Heavy Message
      | 
c/HvHeavy.cpp:127: warning: ignoring '#pragma mark ' [-Wunknown-pragmas]
  127 | #pragma mark - Heavy Common
      | 
c/HvHeavy.cpp:294: warning: ignoring '#pragma mark ' [-Wunknown-pragmas]
  294 | #pragma mark - Heavy Common
      | 
arm-none-eabi-g++  -c -mcpu=cortex-m7 -mthumb -mfpu=fpv5-d16 -mfloat-abi=hard  -DUSE_HAL_DRIVER -DSTM32H750xx -DUSE_HAL_DRIVER -DHSE_VALUE=16000000 -DSTM32H750xx -Ic/ -I../libdaisy -I../libdaisy/src/ -I../libdaisy/Drivers/CMSIS/Include/ -I../libdaisy/Drivers/CMSIS/Device/ST/STM32H7xx/Include -I../libdaisy/Drivers/STM32H7xx_HAL_Driver/Inc/ -I../libdaisy/core/ -I  -O2 -Wall -Wno-missing-attributes -fasm -fdata-sections -ffunction-sections -MMD -MP -MF"build/tone_generator_seq.d" -fno-exceptions -fasm -finline -finline-functions-called-once -fshort-enums -fno-move-loop-invariants -fno-unwind-tables  -std=gnu++14 -Wa,-a,-ad,-alms=build/tone_generator_seq.lst tone_generator_seq.cpp -o build/tone_generator_seq.o
In file included from c/HeavyContextInterface.hpp:20,
                 from c/HeavyContext.hpp:20,
                 from c/Heavy_tone_generator_seq.hpp:37,
                 from tone_generator_seq.cpp:5:
c/HvUtils.h:33:4: warning: #warning Could not detect platform. Assuming Unix-like. [-Wcpp]
   33 |   #warning Could not detect platform. Assuming Unix-like.
      |    ^~~~~~~
In file included from tone_generator_seq.cpp:3:
daisy_boards.h: In function 'void __static_initialization_and_destruction_0(int, int)':
daisy_boards.h:73:14: warning: statement has no effect [-Wunused-value]
   73 | DaisyHvParam DaisyParameters[0];
      |              ^~~~~~~~~~~~~~~
arm-none-eabi-g++  build/HvControlBinop.o build/HvControlCast.o build/HvControlDelay.o build/HvControlSystem.o build/HvControlVar.o build/HvLightPipe.o build/HvMessage.o build/HvMessagePool.o build/HvMessageQueue.o build/HvSignalPhasor.o build/HvSignalVar.o build/HvTable.o build/HvUtils.o build/system_stm32h7xx.o build/startup_stm32h750xx.o build/HeavyContext.o build/Heavy_tone_generator_seq.o build/HvHeavy.o build/tone_generator_seq.o  -mcpu=cortex-m7 -mthumb -mfpu=fpv5-d16 -mfloat-abi=hard --specs=nano.specs --specs=nosys.specs -T../libdaisy/core/STM32H750IB_flash.lds -L../libdaisy/build  -ldaisy -lc -lm -lnosys -Wl,-Map=build/tone_generator_seq.map,--cref -Wl,--gc-sections -o build/tone_generator_seq.elf
arm-none-eabi-size build/tone_generator_seq.elf
   text	   data	    bss	    dec	    hex	filename
  63620	    800	  15024	  79444	  13654	build/tone_generator_seq.elf
arm-none-eabi-objcopy -O ihex build/tone_generator_seq.elf build/tone_generator_seq.hex
arm-none-eabi-objcopy -O binary -S build/tone_generator_seq.elf build/tone_generator_seq.bin
Hughs-MacBook-Pro-2:tone_generator_seq Crewdson$ make program-dfu
dfu-util -a 0 -s 0x08000000:leave -D build/tone_generator_seq.bin -d 0483:df11
dfu-util 0.11

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2021 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/

dfu-util: Warning: Invalid DFU suffix signature
dfu-util: A valid DFU suffix will be required in a future dfu-util release
Deducing device DFU version from functional descriptor length
Opening DFU capable USB device...
Device ID 0483:df11
Device DFU version 011a
Claiming USB DFU Interface...
Setting Alternate Interface #0 ...
Determining device status...
DFU state(2) = dfuIDLE, status(0) = No error condition is present
DFU mode device DFU version 011a
Device returned transfer size 1024
DfuSe interface name: "Internal Flash   "
Downloading element to address = 0x08000000, size = 64428
Erase   	[=========================] 100%        64428 bytes
Erase    done.
Download	[=========================] 100%        64428 bytes
Download done.
File downloaded successfully
Submitting leave request...
dfu-util: Error during download get_status
make: *** [program-dfu] Error 74
Hughs-MacBook-Pro-2:tone_generator_seq Crewdson$ make program-dfu
dfu-util -a 0 -s 0x08000000:leave -D build/tone_generator_seq.bin -d 0483:df11
dfu-util 0.11

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2021 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/

dfu-util: Warning: Invalid DFU suffix signature
dfu-util: A valid DFU suffix will be required in a future dfu-util release
Deducing device DFU version from functional descriptor length
Opening DFU capable USB device...
Device ID 0483:df11
Device DFU version 011a
Claiming USB DFU Interface...
Setting Alternate Interface #0 ...
Determining device status...
DFU state(2) = dfuIDLE, status(0) = No error condition is present
DFU mode device DFU version 011a
Device returned transfer size 1024
DfuSe interface name: "Internal Flash   "
Downloading element to address = 0x08000000, size = 64428
Erase   	[=========================] 100%        64428 bytes
Erase    done.
Download	[=========================] 100%        64428 bytes
Download done.
File downloaded successfully
Submitting leave request...
dfu-util: Error during download get_status
make: *** [program-dfu] Error 74
Hughs-MacBook-Pro-2:tone_generator_seq Crewdson$ 

Hey everyone!
I just got my Daisy patch and trying to upload some PD patches…

I successfully converted them into C code, compiled, and got them running on daisy though there is a problem with dac 1 and 2 outputs… they are not working completely even with included test examples…

I went through a little debugging of the issue and got to the conclusion that there might be a problem with the translation of PD patch into daisy code since other example projects (DaisyExamples) are working fine on the 1st and 2nd outputs, so that’s definitely not a hardware issue

@litviakk There’s a new version of pd2dsy coming out very soon, you may want to wait a few days for that. I suspect it could fix your issue!

@ben_serge @shensley any update on the PD2DSY update? i’m desperate to get stuck in with my new Pod and Seeds! thank-you

@crewdson it’s looking like we’re on track for making a release today or tomorrow! We’ll post back here when it’s live :slight_smile:

We’re just wrapping up some minor fixes and documenting changes to the installation/setup process.

If you want to try it out early, you can clone the json_and_boot branch of pd2dsy, run the install.sh, and give it a try!

Amazing. Very exciting. Thank-you @shensley