Hi,
I have been working on a project for some time that now needs to be compiled in a bigger size than that small. The weird thing is that when I flash with the Small options it’s fine, it’s really just in Big or Huge that my patch is then unresponsive.
There’s no need to look at the patch in its entirety, only one of its sub patch is enough to see if the flashing is conclusive or not. Here’s a picture of it:
In short, I have on my breadboard two buttons, one that rises the level of the cv outputs, one that lowers it. I can see the levels rising on my breadboard with the help of LEDs connected to my CV output by using a TL072 in a buffer configuration.
I have seen other posts of the forum talking about making sure to see the LED on the daisy seed blink to make sure that the bootloader is well installed, and all seems to say that it’s no problem. In fact, I have tried booting up in the same patch a very basic [osc~ 440] to a [dac~] and this works fine.
The compiler window doesn’t seem to have any relevant information.
From this subpatch I can’t see anything peculiar that could cause issues with the bootloader.
Only these trigger objects that are redundant, because the select already outputs a bang:
Btw for the bootloader the LED shouldn’t blink, it should fade in/out.
Yeah this doesn’t make no sense to me. I have just finished doing something a bit more robust with this circuit (it’s crazy how much you progress fast when you get into it) and I have came up with this:
I also confirmed with my oscilloscope that when compiling with the ‘‘Big’’ option, [keyup] and [keydown] are not floating at 3.3 V while waiting. Could it be a problem of big mode not compiling correctly the Json files? Here is a copy-paste of mine:
},
"keyup": {
"component": "Switch",
"pin": "29"
},
"keydown": {
"component": "Switch",
"pin": "30"
}
I would also like to point out that all the rest of my project seems to be working fine; audio effect, sequencer, potentiometers, all of it works fine. Could it be because they are the only one programmed as switches? Is it a problems with the pins assigned to? Thank you
Ah, I see the issue here. The pins you are using have a bug in the current version of libDaisy and the bootloader that we have in the plugdata toolchain. This was resolved last year, however we need to do a big port of the json2daisy library before we can move to newer libdaisy.
Basically these pins don’t work with our current version of the bootloader at all (they are the same pins that are used on the Field for the left and right switch below the oled screen). It was discussed in this ticket: SRAM Bootloader Breaks SW1 and SW2 on Daisy Field · Issue #534 · electro-smith/libDaisy · GitHub
Unfortunately I cannot give a timeline on when this will be updated as it completely depends on my free time and focus which are both very limited these days. I do hope we can work on this later this year, but I cannot make any guarantees of course.
Okay, thank you for the response, i will try to see what i can do on my part. Fortunately I still have 3 other digital pins that I still have unused, so i should be able to do some desoldering to fix it all. Is there any other pecuniar bugs with the pins that I should know about?
Thank you
