FNIRSI-1013D "100MHz" tablet oscilloscope

[corgon]

Default didn’t help. It’s the same.

[Atlan]

Now what FPGA firmware is there? Have you tried to bring a signal? Try uploading the original fpga firmware, it is located under the flash fpga button

[Atlan]

If that doesn't help, turn on the serial port and dev mode in the menu. Turn the oscilloscope off and on. Turn on some serial port terminal so you can enter values. (any speed, e.g. 9600. Connect to the oscilloscope and leave the empty character res. Press enter. We are interested in the value under the letter f. Alternatively, write: f3000 and Enter

[corgon]

FW DSO, 1.00l8

Exactly according to the instructions, I enabled the serial port and dev mode in the menu.

- I turned the oscilloscope off and on again, and booted PECO.
- USB connected, the USB serial port was detected.
- I opened the terminal, but there was no data stream and no response to ENTER or to f3000.

Next, I tried AUTO SET several times in a row, and occasionally it set correctly.
When connecting the calibration signal from the oscilloscope’s output, the signal is displayed correctly

[Atlan]

What terminal did you use? Arduino?

[corgon]

I’m using Termite.
I also tried the terminal from the MRS environment and PuTTY.

[Atlan]

And after pressing enter, did it also send some kind of CR termination command? It doesn't really matter.

The problem is in auto mode if no trigger is found. Then we should have collected samples and terminated after the timeout. But the FPGA is written in such a way that although the writing to the memory is terminated, the address reading continues, and then it draws random data from the memory to the screen.

Here is the software version of the solution, but it has some bugs. But you can still go back to firmware 0.27u or even fpga. It's a question of 2 taps on the screen. When I have time, I'll fix the FPGA.

[corgon]

Sure, I tried with CR LF and without, using different terminals, but it didn’t work. The only thing I noticed was the oscilloscope display flickering when pressing ENTER or sending f3000.
However, there was no response on the terminals.

Regarding the current FW version, Scope v1.00l9 is installed and it seems to be working.
I will continue testing.

Question: Are the 4 wires connected from the original FLASH now permanent, or can they be removed?
Do you have anything specific you want me to focus on during testing?

By the way, great work, Atlan.

[Atlan]

4 wires, permanent. You can assemble an oscilloscope. Theoretically. The DSO program and FPGA firmware update will be done via Updater.

In the generator menu, it is possible to change the frequency from 0 to 5Mhz and the duty cycle from 0 to 100%, the other items are there for other things, the oscilloscope hardware does not support it.

The trigger is fixed at 750, 1500 and 2250.

The standard memory is 16300, but it is basically set to 3000 samples. It is strange with the serial port, I tried it in Win Arduino Console and Linux and it works. f9000 sets it to 9000 samples. Just be careful when entering it because it is not controlled by anything. Entering a wrong number will cause it to be written to who knows where in the memory.

[kd7eir]

Hopefully the author of the application will forgive me and allow minor changes.
THANKS for Hiban for APP DSO2512G-APP-beta10

What would I need to do to connect to the app with USB?

[Atlan]

fixed timeout in auto mode in FPGA, DSO has samples set to 16000.

[Atlan]

Hopefully the author of the application will forgive me and allow minor changes.
THANKS for Hiban for APP DSO2512G-APP-beta10

What would I need to do to connect to the app with USB?

turn on USB serial mode in the oscilloscope menu, turn off the oscilloscope. And most importantly, use the version that has it implemented. scope v0.27s.bin.hex

But that was just for fun, because the program in the PC is adapted to another oscilloscope, the whole sending of samples is like this... for every few samples of 9600, 28000 data is sent...

[corgon]

fixed timeout in auto mode in FPGA, DSO has samples set to 16000.

I tried your latest FW scope v1.00m.bin and FPGA.bin.
The trigger issue still persists.
Here is a short video showing how it behaves:
https://www.youtube.com/shorts/NP-vzh8Kzew

[mishail71]

Atlant, thank you very much...
If it's not too much trouble, for some reason I can't send Fnirsi FPGA.bin.txt.
Perhaps I missed something.. Thanks.
SPI deleted...I think I was able to download Fnirsi FPGA.

[mishail71]

I think I was able to download Fnirsi FPGA.

[corgon]

I decided to give it another try and reflashed the entire stack
Bootloader, Updater, DSO FW, and FPGA FW, and it appears to have resolved the trigger issue.
For now, the device is behaving normally. I’ll continue testing and reprt back. 

[mishail71]

It seems like I've completely bricked my device, guys!!! It won't turn on at all..)))

[Atlan]

What did you upload to the fpga? You will need a ch341 programmer with a 3.3V switch. With a clip.

[mishail71]

I accidentally clicked "UPLOAD CPI BACKUP Flash," and after that the screen went black. I have this programmer. What firmware should I upload? If it's the original firmware, I've already tried it. The result was zero. The device won't turn on at all.
Thank you

[Atlan]

If there is a bootloader, then you can upload the program, connect a programmer or use a clip, turn on the oscilloscope and try to detect the chip. Try loading the content several times and watch if the loaded data does not change. If it does not change, you can overwrite the original fnirasi file (the file that the osi uploaded is not fnirasi but an alternative, so you do not have a backup) use this one. Another thing you can do with the flash is to write fuses against programming. Give a photo of what software you use for programming. The programmer is adjusted to 3.3V because it usually puts 5V there

[mishail71]

Atlant, please tell me if I need to unsolder four wires to flash the firmware...the program I'm using is CH341A_C. And is it possible to flash the SPI off-board? Thanks.

Forgive me, this is all a dark forest!!!
Atlant, could you tell me where I can watch a video showing this solution? The operating and boot (recovery) algorithms are completely unknown to me! Thank you. In the post above, you described the device recovery algorithm. But I don't understand these terms...))

[Atlan]

Desoldering the SPI flash is the safest way to program it.

[mishail71]

Atlant, that's what I did... I just don't get it, do I need to upload your fpga-1013D-1-zb25vq80.bin.txt file to the SPI?
It's probably a coincidence... and the controller itself has failed. The power indicator doesn't work when turned on. The display backlight doesn't light. The computer doesn't recognize the connected device. Oh well... I never used it anyway. Thanks, Atlant, for all the help.

[Atlan]

The backlight is turned on by the FPGA. The uP also checks for the presence of the FPGA at startup, if the fpga is not working, the uP remains in a loop. Yes, open the file in the programmer, detect the memory and upload the data. I already asked you for a photo of the software. If you want to help.

More than once, I managed to block the oscilloscope with a bad fpga program.
Yes, it looks dead, but don't worry. Just need the right FPGA content, it will come to life.

[Atlan]

v1.00n fix switch sensitivity in main screen without update base time. Add orange center line for single mode. Because of the resolution of tapping above and below the X axis, it has different functions.