[Csnd] Trying out Daisy

The Csound Mailinglist
1

Hi!

Happy new year to everyone!

This is mostly meant for Aman and Victor - as you demonstrated so inspiringly the bare metal Csound on Daisy platform in Vienna.

I got a Daisy pod now, I was able to set up the build tools and got the demos of Daisy/Examples built and working. But I have not managed to have Csound on the board yet…

What I did was:

Cloned Amar’s repo: https://github.com/amanjagwani/DaisyCsound

flashed daisyCsound.bin from the build directory to Daisy. It got installed but nothing happened. I tried to connect a MIDI controller via usb port on the pod to play some notes but it did nothing.

I wanted to replace the Csound code with something that makes sound by itself.

I compiled and installed Csound7 according to the instructions in Daisy folder of Csound sources. I replaced libDaisy/core/STM32H750IB_qspi.lds with the one form csound/Daisy folder, as instructed.

Then I created a new project to the DaisyExamples folder and started to go step by step, using the leds on the pod to signal what gets executed (I don’t have a debugging probe yet, so it is really hard to guess, what is happening).

One thing I found out: when I added this to my Makefile (to load the binary to extended RAM):
APP_TYPE = BOOT_QSPI

  • even with a simple LED program, nothing happened with the STM32H750IB_qspi.lds from Csound sources. When I used the original file, it worked as expected.
    I used make program-boot && make program-dfu to flash it.

Then I tried to add some minimal Csound and seems that the program gets stuck in creating Csound object:

int main(void)
{
hw.Init();

hw.led1.Set(0, 0, 1); // blue
hw.UpdateLeds();

System::Delay(5000);
CSOUND *cs = csoundCreate(NULL, NULL);

hw.led1.Set(0, 1, 0); // green
hw.UpdateLeds();

When I use the original STM32H750IB_qsp - the led is lit blue but never green.
When I use Csound’s STM32H750IB_qsp - nothing is lit, even blue.

What can be the reason? How to proceed?

Aman, Victor, do you have some ready, working .bin that makes some sound and does not require MIDI for testing?

By the way, daisyCsound.cpp and .hpp files in DaisyCsound repo are outdated and do not compile with present Csound7 API any more. I copied the source files from Daisy/example to that repo, since the Makefile there is nice to use, made necessary changes and then it built well.

If I get through of this, I will write the whole process down for others to follow. It is pretty exciting to get Csound to the small chips!

I attach my .cpp and Makefile.

Thanks!
tarmo

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

(Attachment Makefile is missing)

(Attachment TestProject.cpp is missing)

2

Hi!

I am not sure if the previous message got through because of the attachments, I try again, now with .txt extensions on the files.

TestProject.txt (1.41 KB)

Makefile.txt (943 Bytes)

3

You mentioned ‘pod’ but as far as I know the configuration files we have are for the Daisy seed. So that may be the issue, the Csound binary etc is the same but where things go in memory etc may be different, so you might need a slight different lds file for the pod.

The reason Csound gets stuck with the provided lds is that there isn’t enough memory onboard for the Csound engine and we need to configure the loader to use other memory locations.

I think it should be possible to figure out the changes required. Aman can help.

best

Prof. Victor Lazzarini
Maynooth University
Ireland

4

Thanks!

Daisy pod is basically Daisy Seed on a breakout board with some knobs, leds and 3.5 mm audio sockets. So everything that concerns memory and software should be basically the same.

Also in the libDaisy folder, lds files are all in the same, core directory, they don’t seem to depend on the board flavour.

My guess is that the STM32H750IB_qspi.lds in Csound sources does not work somehow with the Csound library I built locally, since there might have been API changes, but maybe also not. I don’t undertand the embedded devices world much…

Aman, if you can comment, I will be all ears!

Best!
Tarmo

P, 5. jaanuar 2025 00:47 Victor Lazzarini <000010b17ddd988e-dmarc-request@listserv.heanet.ie> kirjutas:

You mentioned ‘pod’ but as far as I know the configuration files we have are for the Daisy seed. So that may be the issue, the Csound binary etc is the same but where things go in memory etc may be different, so you might need a slight different lds file for the pod.

The reason Csound gets stuck with the provided lds is that there isn’t enough memory onboard for the Csound engine and we need to configure the loader to use other memory locations.

I think it should be possible to figure out the changes required. Aman can help.

best

Prof. Victor Lazzarini
Maynooth University
Ireland

Warning

This email originated from outside of Maynooth University’s Mail System. Do not reply, click links or open attachments unless you recognise the sender and know the content is safe.

Hi!

Happy new year to everyone!

This is mostly meant for Aman and Victor - as you demonstrated so inspiringly the bare metal Csound on Daisy platform in Vienna.

I got a Daisy pod now, I was able to set up the build tools and got the demos of Daisy/Examples built and working. But I have not managed to have Csound on the board yet…

What I did was:

Cloned Amar’s repo: https://github.com/amanjagwani/DaisyCsound

flashed daisyCsound.bin from the build directory to Daisy. It got installed but nothing happened. I tried to connect a MIDI controller via usb port on the pod to play some notes but it did nothing.

I wanted to replace the Csound code with something that makes sound by itself.

I compiled and installed Csound7 according to the instructions in Daisy folder of Csound sources. I replaced libDaisy/core/STM32H750IB_qspi.lds with the one form csound/Daisy folder, as instructed.

Then I created a new project to the DaisyExamples folder and started to go step by step, using the leds on the pod to signal what gets executed (I don’t have a debugging probe yet, so it is really hard to guess, what is happening).

One thing I found out: when I added this to my Makefile (to load the binary to extended RAM):
APP_TYPE = BOOT_QSPI

  • even with a simple LED program, nothing happened with the STM32H750IB_qspi.lds from Csound sources. When I used the original file, it worked as expected.
    I used make program-boot && make program-dfu to flash it.

Then I tried to add some minimal Csound and seems that the program gets stuck in creating Csound object:

int main(void)
{
hw.Init();

hw.led1.Set(0, 0, 1); // blue
hw.UpdateLeds();

System::Delay(5000);
CSOUND *cs = csoundCreate(NULL, NULL);

hw.led1.Set(0, 1, 0); // green
hw.UpdateLeds();

When I use the original STM32H750IB_qsp - the led is lit blue but never green.
When I use Csound’s STM32H750IB_qsp - nothing is lit, even blue.

What can be the reason? How to proceed?

Aman, Victor, do you have some ready, working .bin that makes some sound and does not require MIDI for testing?

By the way, daisyCsound.cpp and .hpp files in DaisyCsound repo are outdated and do not compile with present Csound7 API any more. I copied the source files from Daisy/example to that repo, since the Makefile there is nice to use, made necessary changes and then it built well.

If I get through of this, I will write the whole process down for others to follow. It is pretty exciting to get Csound to the small chips!

I attach my .cpp and Makefile.

Thanks!
tarmo

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

<TestProject.cpp>

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

5

Those files are not dependent on the API or Csound library changes, they are only to do with changing memory locations etc.

I would expect that the basic lds files would be the same for all boards, but we need to customise the loader so Csound can
work, so that part may differ. I have pinged Aman and he should be able to comment.

6

Re-reading your email, I wasn’t sure that you have the latest files.
Did you try the files from the Csound repository develop branch? The example code there should be up-to-date with the
latest Csound library (at least).

7

Hi!

Thank you, Victor!

… but as far as I know the configuration files we have are for the Daisy seed

This was worth a try, I remembered there is a .vscode subfolder and perhaps it is different for a seed build. So I created a project for seed in the root folder of DaisyExamples.

./helper.py create seed/SeedTest --board seed

For testing I added those lines to main():

hw.Init();

hw.SetLed(true);
System::Delay(5000);
CSOUND *cs = csoundCreate(NULL, NULL);
hw.SetLed(false);

I went through the same steps but the result is the same - when I use the STM32H750IB_qspi.lds provided by Csound, the program seems not to start at all - the led is nenver lit. When I use original STM32H750IB_qspi.lds, the led is lit but never turned off, ie the program gets stuck by soundCeate().

To flash the program, I used first make program-boot, pressed Resed on seed and then make program-dfu.

I discovered that when I use the the bootloader from the build with STM32H750IB_qspi of Csound, and then any working porgam, like my own tryout without Csound or Blink, it never starts. So it seems to be some problem of the bootloader. Or can easily be that I am doing something wrong…

Did you try the files from the Csound repository develop branch?

  • Yes, these build fine, the ones in https://github.com/amanjagwani/DaisyCsound/ not. But this is fine, it was probably meant as a testing repo at some stadium anyway. When all things will be sorted out, it might be good to add a demo Makefile to the Daisy/Example folder. I can do it and I will make a pull request with updated Readme and the Makefile, if I get through it and things working

Thanks!
tarmo

Kontakt Victor Lazzarini (<000010b17ddd988e-dmarc-request@listserv.heanet.ie>) kirjutas kuupäeval P, 5. jaanuar 2025 kell 02:16:

Re-reading your email, I wasn’t sure that you have the latest files.
Did you try the files from the Csound repository develop branch? The example code there should be up-to-date with the
latest Csound library (at least).

Prof. Victor Lazzarini
Maynooth University
Ireland

Thanks!

Daisy pod is basically Daisy Seed on a breakout board with some knobs, leds and 3.5 mm audio sockets. So everything that concerns memory and software should be basically the same.

Also in the libDaisy folder, lds files are all in the same, core directory, they don’t seem to depend on the board flavour.

My guess is that the STM32H750IB_qspi.lds in Csound sources does not work somehow with the Csound library I built locally, since there might have been API changes, but maybe also not. I don’t undertand the embedded devices world much…

Aman, if you can comment, I will be all ears!

Best!
Tarmo

P, 5. jaanuar 2025 00:47 Victor Lazzarini <000010b17ddd988e-dmarc-request@listserv.heanet.ie> kirjutas:
You mentioned ‘pod’ but as far as I know the configuration files we have are for the Daisy seed. So that may be the issue, the Csound binary etc is the same but where things go in memory etc may be different, so you might need a slight different lds file for the pod.

The reason Csound gets stuck with the provided lds is that there isn’t enough memory onboard for the Csound engine and we need to configure the loader to use other memory locations.

I think it should be possible to figure out the changes required. Aman can help.

best
Prof. Victor Lazzarini
Maynooth University
Ireland

Warning
This email originated from outside of Maynooth University’s Mail System. Do not reply, click links or open attachments unless you recognise the sender and know the content is safe.
Hi!

Happy new year to everyone!

This is mostly meant for Aman and Victor - as you demonstrated so inspiringly the bare metal Csound on Daisy platform in Vienna.

I got a Daisy pod now, I was able to set up the build tools and got the demos of Daisy/Examples built and working. But I have not managed to have Csound on the board yet…

What I did was:

Cloned Amar’s repo: https://github.com/amanjagwani/DaisyCsound

flashed daisyCsound.bin from the build directory to Daisy. It got installed but nothing happened. I tried to connect a MIDI controller via usb port on the pod to play some notes but it did nothing.

I wanted to replace the Csound code with something that makes sound by itself.
I compiled and installed Csound7 according to the instructions in Daisy folder of Csound sources. I replaced libDaisy/core/STM32H750IB_qspi.lds with the one form csound/Daisy folder, as instructed.

Then I created a new project to the DaisyExamples folder and started to go step by step, using the leds on the pod to signal what gets executed (I don’t have a debugging probe yet, so it is really hard to guess, what is happening).

One thing I found out: when I added this to my Makefile (to load the binary to extended RAM):
APP_TYPE = BOOT_QSPI

  • even with a simple LED program, nothing happened with the STM32H750IB_qspi.lds from Csound sources. When I used the original file, it worked as expected.
    I used make program-boot && make program-dfu to flash it.

Then I tried to add some minimal Csound and seems that the program gets stuck in creating Csound object:

int main(void)
{
hw.Init();

hw.led1.Set(0, 0, 1); // blue
hw.UpdateLeds();

System::Delay(5000);
CSOUND *cs = csoundCreate(NULL, NULL);

hw.led1.Set(0, 1, 0); // green
hw.UpdateLeds();
When I use the original STM32H750IB_qsp - the led is lit blue but never green.
When I use Csound’s STM32H750IB_qsp - nothing is lit, even blue.

What can be the reason? How to proceed?

Aman, Victor, do you have some ready, working .bin that makes some sound and does not require MIDI for testing?
By the way, daisyCsound.cpp and .hpp files in DaisyCsound repo are outdated and do not compile with present Csound7 API any more. I copied the source files from Daisy/example to that repo, since the Makefile there is nice to use, made necessary changes and then it built well.

If I get through of this, I will write the whole process down for others to follow. It is pretty exciting to get Csound to the small chips!

I attach my .cpp and Makefile.

Thanks!
tarmo

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

<TestProject.cpp>
Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here