Code: Select all
bool oldVal=nonVolatileSettings.audioPromptMode;
Cheers.
---
Daniel
Code: Select all
bool oldVal=nonVolatileSettings.audioPromptMode;
Hi,F1RMB wrote: ↑Wed Jul 29, 2020 8:28 pmHi,
You don't have to change the code to build a platform specific version. In the top button bar, one looks like a hammer (IIRC), click on the small arrow on the right, that will display all the platforms in a drop-down widget. Select the one you're interested in, then click the hammer icon, if needed.
The firmware won't run if you build in Release mode.OK1TE wrote: ↑Thu Oct 01, 2020 8:17 amHi,F1RMB wrote: ↑Wed Jul 29, 2020 8:28 pmHi,
You don't have to change the code to build a platform specific version. In the top button bar, one looks like a hammer (IIRC), click on the small arrow on the right, that will display all the platforms in a drop-down widget. Select the one you're interested in, then click the hammer icon, if needed.
and how to use the "Release" configuration please? I can build all the debug platforms, but have compilation errors in the Release, mainly connected to GPIO and other definitions.
Thank you,
Jan OK1TE
Thanks Roger for explanation.VK3KYY wrote: ↑Thu Oct 01, 2020 10:37 pmThe firmware won't run if you build in Release mode.
The "Debug" builds are effectively release, with the exception of a few files which must have optimisation disabled otherwise the firmware doesn't work.
Please feel free to try to make release build work, but IMO there appears to be a bug in the I2S SDK which prevents that system working correctly if compiled with -oS optimisation
I googled for this already and saw the same response, but it does not really help.OK1TE wrote: ↑Fri Oct 02, 2020 1:35 pmThanks Roger for explanation.
I'll give Google a try about possible bug in the I2S, but my intuition sugests there might be some variables which should be declared volatile.
Interesting problem, I've saved it in my stack, but now we have more important issues. `-)
"I2S audio subsystem changed to use compiler optimisation"
I don't think there was a specific bug in I2S code.