Member
Joined 2018
Member
Joined 2018
Hi @CyberPit yes, it's better, but the potentiometer isn't as responsive.
Debounce 3 and potentiometer AUXADC0 in the same position, sometimes a different value appears there:
Param Value: 0.78515625
Param Value: 0.7861328125
And here's how AUXADC5 behaves with debounce 3:
Param Value: 0.1982421875
Param Value: 0.2001953125
Does it happen to you as well, or is it just an anomaly on my hardware?
Do you also use such debounce? It's only a 10-bit AUXADC, but I still feel like something is wrong.
Many Thanks, Tom
Debounce 3 and potentiometer AUXADC0 in the same position, sometimes a different value appears there:
Param Value: 0.78515625
Param Value: 0.7861328125
And here's how AUXADC5 behaves with debounce 3:
Param Value: 0.1982421875
Param Value: 0.2001953125
Does it happen to you as well, or is it just an anomaly on my hardware?
Do you also use such debounce? It's only a 10-bit AUXADC, but I still feel like something is wrong.
Many Thanks, Tom
In addition to this, all the noise that comes to the ADC penetrates into the useful signal, I got rid of this problem by simply installing a 10th order low-pass filter with a cutoff frequency of 3Hz after the ADC.
Many thanks @CyberPit @uriy-ch
debounce didn't quite suit me, or rather, I didn't find a value that solves my problem. Adding a low pass is better, it stabilizes after a while, just need to fix negative values. So far, it seems stable to me.
3 Hz doesn't work for me: there's simply always a 0 at the output. However, 4 Hz works fine.
debounce didn't quite suit me, or rather, I didn't find a value that solves my problem. Adding a low pass is better, it stabilizes after a while, just need to fix negative values. So far, it seems stable to me.
3 Hz doesn't work for me: there's simply always a 0 at the output. However, 4 Hz works fine.
Hi,
I've tested York with ADAU1452 in 8 channel TDM mode. Here is the working configuration:
(York v1 does not support TDM8 right now, it needs one wire to be soldered and a firmware update. I plan to do the fix by end of May for v1)
With clocking from on-board oscillators (which are 22.5792 and 24.576 MHz) max Fs in TDM mode is 48 kHz, with PLL clocking it can be up to 96kHz.
Since in FreeDSP masterclock is generated by ADAU and not connected to Amanero header, ASRC usage is mandatory. So it does not really matter which clock to use for York (in regards to clock's phase noise). So PLL clock is better option in this use case.
Here is my test setup: post
TDM signal look like this: pink - data, yellow - wck. Only two channels are active at this waveforms:
I've tested York with ADAU1452 in 8 channel TDM mode. Here is the working configuration:
(York v1 does not support TDM8 right now, it needs one wire to be soldered and a firmware update. I plan to do the fix by end of May for v1)
With clocking from on-board oscillators (which are 22.5792 and 24.576 MHz) max Fs in TDM mode is 48 kHz, with PLL clocking it can be up to 96kHz.
Since in FreeDSP masterclock is generated by ADAU and not connected to Amanero header, ASRC usage is mandatory. So it does not really matter which clock to use for York (in regards to clock's phase noise). So PLL clock is better option in this use case.
Here is my test setup: post
TDM signal look like this: pink - data, yellow - wck. Only two channels are active at this waveforms:
Hi @CyberPit,
while testfitting the new York from @eclipsevl I notice that the spacing of the mounting holes for amanero don't align with the ones on the york.
The spacing on the ocativa is 24mm while the spacing on the york is 25mm. According to the spec of the Amanero COMBO384 25mm is the correct spacing.
Do you have a different Amanero board is this a mistake in the PCB design?
Best Regards,
Ludwig
while testfitting the new York from @eclipsevl I notice that the spacing of the mounting holes for amanero don't align with the ones on the york.
The spacing on the ocativa is 24mm while the spacing on the york is 25mm. According to the spec of the Amanero COMBO384 25mm is the correct spacing.
Do you have a different Amanero board is this a mistake in the PCB design?
Best Regards,
Ludwig
Member
Joined 2018
Hello Ludwig-San,
Thanks for informing the spacing issue.
I will fix that design and Footprint Library later.
CyberPit
Thanks for informing the spacing issue.
I will fix that design and Footprint Library later.
CyberPit
@eclipsevl I have to say, the York is a very nice and suitable addition for the octavia. USB audio works like a charm ( I have only tested normal stereo I2s so far) and also the the adau configuration and live connection works very well and both over the same USB connection.
If anyone is looking into buying amanero, I would recommend having a look at the York.
If anyone is looking into buying amanero, I would recommend having a look at the York.
Hello, I am resuming the use of OCTAVIA, and I encounter a problem of writing in the MEM in SPI. SS_M/MP0 always remains at 3.3Volts whereas it should go to zero volts in programming. I lose the data when I turn off the card and turn it back on.
Any advice?.
Thanks.
Any advice?.
Thanks.
The problem has disappeared, it depends on the program, with some it works and others not.
Thanks
Thanks
Member
Joined 2018
Hi sb-San,
Well, sometimes the SigmaStudio generates 🧟♂️ junk code, especially after the Sleep/Hibernation operation case.
In a few cases, I needed to disable the self-boot before programming additionally.
🤷♂️
CyberPit
Well, sometimes the SigmaStudio generates 🧟♂️ junk code, especially after the Sleep/Hibernation operation case.
In a few cases, I needed to disable the self-boot before programming additionally.
🤷♂️
CyberPit
Hello CyberPit , still the same problems writing in the EEprom, but when I do an Erase Memory from DSP the program appears again and works,
when I turn off and on again I also have to do an Erase Memory from DSP.
Any idea?
I use a TINYSINE USBI JTAG DSP Programmateur Sigma DSP.
Thanks
Serge B.
when I turn off and on again I also have to do an Erase Memory from DSP.
Any idea?
I use a TINYSINE USBI JTAG DSP Programmateur Sigma DSP.
Thanks
Serge B.
Member
Joined 2018
Hello sb-San,
The DSP's SPI master port will write the EEPROM. This means the DSP does not overwrite the EEPROM somehow. In my case, the EEPROM could not be overwritten cause of unbootable junk code. (Even in this case, programming through DSP works correctly)
In this case, I turned off SELF-BOOT (short connection on JP1 during power-up) and then USBi connected. After overwriting EEPROM, the self-boot function comes back to work correctly.
I hope you will succeed in erasing the Zombi junk code...
CyberPIt
The DSP's SPI master port will write the EEPROM. This means the DSP does not overwrite the EEPROM somehow. In my case, the EEPROM could not be overwritten cause of unbootable junk code. (Even in this case, programming through DSP works correctly)
In this case, I turned off SELF-BOOT (short connection on JP1 during power-up) and then USBi connected. After overwriting EEPROM, the self-boot function comes back to work correctly.
I hope you will succeed in erasing the Zombi junk code...
CyberPIt