Products > Test Equipment

New bench scope - Fnirsi 1014D, 7", 1GSa/s

<< < (19/67) > >>

pcprogrammer:

--- Quote from: joseph4511 on April 30, 2022, 07:24:04 pm ---there s no rev. number written. Only 1014D OSC, nothing is different than old board but F1C100s

--- End quote ---

The only difference between the F1C100s and the F1C200s is the size of the DRAM. 32MB for the 100 and 64MB for the 200. It might be that they ran out of the 100 and used the 200 instead. Doubt that they changed the firmware to make use of the extra memory.

Would be interesting to see what is wrong with the old board 8)

joseph4511:
i tried to reflash every rom from new board nothing changed. Checked all boosters and xtals. Also checked with flir nothing gets hot than usual. Afaik problem occured when its off and plugged to voltage source. If you have any idea to start somewhere, i d be grateful :)

pcprogrammer:
The fact that the board is (was) able to load and display the startup image tells us that part of the system is working as it should. The fact that it hangs after displaying it tells us that it fails in either loading the real program or that the real program itself hangs before clearing the screen.

Running the firmware backup program I wrote will show if the system is capable of reading the whole flash and interact with the display. So that is one test you could do.

Other things that come to mind are:

* The DRAM in the F1C100s has a problem
* A peripheral in the F1C100s has a problem
* The GD32 chip for handling the buttons and knobs has a problem
* The FPGA has a problem
A test to perform is measure all the voltages on the board. The hardware is very similar to the 1013D so look at the schematics in the repository.

In the hack repository https://github.com/pecostm32/FNIRSI-1013D-Hack a lot of information is available to research the problem.

It could be a fun learning experience. It is possible to run linux on the F1C100s, but it needs a serial connection to one of the chips UART, so you have to figure out if it is possible to connect a USB -> serial converter to the one connected to the GD32 chip. There is a linux image in the repository that should work. (It does on the 1013D)

I myself would write my own test programs to check things, but that is me :-DD

Have fun with it :)

joseph4511:
i replaced F1C100s with 200s and worked on working board, broken is still same. Swapped GD32 with working one nothing have changed. I swapped SE 98 marked component and i have 2 dead board with same issue now :(

pcprogrammer:
Is also a way to get to the broken component. Requires good soldering skills and tools :)

I looked at my board but did not see a chip with SE 98 marking on it. Can you take pictures of the board and show which component you are talking about?

Attached is a picture of my board.

Edit: Made markings on the board picture to identify some of the parts on it.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod