JackTheVendicator
It would be great to put your fix in pmos69 firmware. Now I’m usnig a DSO_Sm_JTV_V1.71 and satisfied with it, but I would like to use the new features without losing the correct operation of single-mode.
There is another issue I have to report here. The wave out (analog) seems to be off by one index. If it is generating 1kHz, the output is actually 500Hz. I caught this while looking at the FFT display of frequency.
You’re using AC coupling…
Can’t seem to be able to reproduce that.
My tests all seem OK.
Actually, there was/is an error in the nyquist but that only affects the very highest sample rates.
Will release a fixed version soon.
So, it must show ZERO, didn’t it? =)
CH_B Vdc is near zero, AC coupling is set=)
CH_A is grounded.
CH_B is grounded
CH_A DC coupling
Just a small “math bug”. What’s a little overflow among friends. 
Actually it’s something I left in there while debugging after another bug (the errors introduced by chenging the Y displacement) 
It’s just one line of code. Next release will have the fix.
Will the next release include triggering fix from JTV?
if Jack comes through…
Here is a screenshot of the problem. What I did is record the Squarewave(A_Tab) @1kHz - Timebase is 1mS
I then changed the output to PWM(D_Tab) @1kHz 50% duty and captured the screen shot
Here [attachment=0]IMAG002.GIF[/attachment]
Indeed, the generator frequency is twice lower except PWM wave
Still can’t reproduce that.
Perhaps I changed something in the mean time.
Anyway…
[code]v1.19
- Fixed incorrect Nyquist in FFT at higher sample rates - Now uses the timebase interpolation coefficient.
- Fixed Vdc overflow bug introduced in v1.18
- Simple Spectrogram (Test version) - Select it from in the trigger mode/X_Y menu.[/code]
Here is a screen shot of the diff I took on the original process.c and the GCC port
[attachment=0]2012-03-15_105421.gif[/attachment]
Can’t reproduce that:
1.9 firmware crashes after calibration.
SPECT mode show blue screen and nothing on it…
In fact, screen is blue…
Strange vertical floating line…bug with SCAN mode…
Can’t check that now (working)
It’s just a test version.
You have to enable the FFT for the Spectrogram to work.
Issues/bugs list now available in the github site: https://github.com/pmos69/dso203_gcc/issues
…please contribute, either with reporting new issues or (preferably ) with fixes.
I’ve been able to fix the analog outputs by changing this table
</s><i>
</i>A_tab A_Tab[15] ={ // analog waveform output driver table synthesis, based on the 72MHz frequency, per 36
// STR PSC ARR
{"! 1Hz !", 20-1, 50000-1},
{"! 2Hz !", 20-1, 20000-1},
{"! 5Hz !", 20-1, 10000-1},
{" 10Hz ", 20-1, 5000-1},
{" 20Hz ", 10-1, 2000-1},
{" 50Hz ", 10-1, 1000-1},
{"!100Hz!", 10-1, 500-1},
{"!200Hz!", 10-1, 200-1},
{"!500Hz!", 10-1, 100-1},
{" 1KHz ", 10-1, 50-1},
{" 2KHz ", 10-1, 20-1},
{" 5KHz ", 10-1, 10-1},
{"!10KHz!", 10-1, 5-1},
{"!20KHz!", 10-1, 2-1},
{"!40KHz!", 4-1, 5-1}}; // this value is wrong
<e>
However, some of the frequencies are not correct - but near and I do not know what to change to set it right. I am new to the STM32 and also the toolchain.
I do not have a reference to the SYS1.52 sources which seem to have the __Set(ANALOG_PSC) command. It is not in the SYS1.51 source. See this fragment
[code]/*******************************************************************************
Update_Output:
*******************************************************************************/
void Update_Output(void)
{
u8 att;
switch (_Kind) {
case SINE:
for(att=0; att <72; att++){
ATT_DATA[att]=(SIN_DATA[att]*Title[OUTPUT][OUTATT].Value)/100;}
DMA2_Channel4->CCR &= ~DMA_CCR1_EN;
***** __Set(ANALOG_PSC, A_Tab[_Frqn].PSC);
__Set(ANALOG_CNT, 72);
__Set(ANALOG_PTR, (u32)ATT_DATA);
DMA2_Channel4->CCR |= DMA_CCR1_EN;
__Set(ANALOG_ARR, A_Tab[_Frqn].ARR);
break;
[/code]
My setup has Chip SYS1.51, HW 2.60.