FNIRSI-1013D "100MHz" tablet oscilloscope

[pcprogrammer]

I see that your panel is covered on both sides, so the traces to the sensor lines are hidden. I can't find the pictures of mine to show what I mean, but it is not such a big deal.

Lets first focus on getting the original firmware modified, so it won't screw up the touch panel again. I will write some code to get this done. No need to buy a programmer. It will take a couple of days to get it done along with other jobs that need taking care of.

Like shaving my week old beard that is starting to itch 

[email hidden]

Ok. Zatím děkuji.
Ok. Thank you for now.

[pcprogrammer]

Hi Mirek,

here is a program to restore the flash of your scope. It needs to be installed on the SD card, just like how it is done for the open source firmware or the backup program.

It looks for a file named "FNIRSI_1013D_main.bin" or "FNIRSI_1013D_full.bin" on the SD card and if found it will load it to the flash. There is no check on the validity of the file.

The _main one is written to address 0x00027000 in the flash. The _full one starts writing at address 0x00000000.

Attached are both the restore program and the _main firmware that I modified to leave the touch panel alone.

Make sure the "FNIRSI_1013D_main.bin" file is on the SD card in the top directory. It does not matter if there are other files on the SD card.

After the writing of the flash, the program removes itself from the SD card and after power up the scope starts with the original firmware.

The touch panel configuration is up next, but that probably will require some back and forth experimenting to get it right.

[Cronyx]

If I record like this, then after starting the picture freezes and does not change in any way.
(Attachment Link)

There was little information and pictures.  Why are you uploading the configuration there, the FW is already uploaded?  Boot configuration is set as?

boot 0.04. firmware v0.025x

[email hidden]

OK.
I'm waiting to see what happens next.

[Atlan]

If I record like this, then after starting the picture freezes and does not change in any way.
(Attachment Link)

There was little information and pictures.  Why are you uploading the configuration there, the FW is already uploaded?  Boot configuration is set as?

boot 0.04. firmware v0.025x

Upload a video on YouTube of what happens after switching on.  Have you tried another sdcart?

[sub77]

Hi Sub77 oh wow its so easy to break small SMD items .. I have taken mine 1013D apart which i fitted the RTC - (Its all ways best to remove the item then measure with test equipment however to risky so did not this time  ) Removed one wire measured in circuit as per pictures .. Measured across the white capacitor Hope it helps 

Hi, haven't been on the forum for a long time...
thanks for your help!

[sub77]

Hi

Thank you for your work and development of this project.
 Unfortunately, when I installing rtc, I broke the capacitor.
Please, if there is information about its characteristics (capacity) for its replacement, I will be grateful. Thanks in advance

It might just work without the capacitor. Normally one would not even add a capacitor between I2C SCL and SDA, but they did it to overcome some problems they have with the bit banged I2C.

Try it without and if it works with the original firmware, don't bother putting another one in. If it does not try it with the 2.2nF Russell2024UK measured.

Hi, Thanks!

it works without capacitor

[Cronyx]

There was little information and pictures.  Why are you uploading the configuration there, the FW is already uploaded?  Boot configuration is set as?

boot 0.04. firmware v0.025x
[/quote]

Upload a video on YouTube of what happens after switching on.  Have you tried another sdcart?
[/quote]

https://youtu.be/CYbQw0VLc1Y

[Atlan]

In boot run as fnirsi.  That way, TP should work properly.  Then activate UsB mode, run loader 1.1.3 and configure TP settings. 

The PC will know what to change.

The line below shows the configuration data for the standard display and touch panel
0xAA 0xAA 0xAA 0xAA 0x55 0x55 0x55 0x55 0x4A 0x00 0x1E 0x04 0x17 0x00 0x1A 0x04 0xCC 0xCC 0xCC 0xCC 0x33 0x33 0x33 0x33 0x5F 0x00 0x38 0x08 0xFF 0xFF

The byte order is little endian and thus least significant byte first.

The first 8 bytes are a pre amble and need too be as shown. In the software these are seen as 32 bit values 0xAAAAAAAA and 0x55555555
The next 4 bytes are the horizontal timing setting. In the software this is also seen as a 32 bit value. 0x041E004A
The following 4 bytes are the vertical timing. In the software this is also seen as a 32 bit value. 0x041A0017
Then an 8 bytes post amble follows. In the software these are seen as 32 bit values 0xCCCCCCCC and 0x33333333
The next 4 bytes are a checksum over the first 6 32 bit values. It is a simple sum of these unsigned integers.

For controlling the touch panel the next two bytes are used. In the original configuration files these are defaulted to 0xFF, so as such no swap.
When set to zero (0x00) the cooradinates are swapped. The first byte is for the X coordinate and the second byte for the Y coordinate.

[email hidden]

I'll just add, TP still the same, Fnirsi loader doesn't change the TP settings.

[pcprogrammer]

I'll just add, TP still the same, Fnirsi loader doesn't change the TP settings.

Patience, I'm working on it. 

[email hidden]

Yes. I will wait.

[pcprogrammer]

Well was not to long was it. 

Here is the program to write the touch panel configuration. Needs to be placed on the SD card, just like the other programs.

But this one does not delete itself from the SD card after use. So it is best to use a second card to make testing easier.

The program looks for a "FNIRSI_1013D_tp_config.bin" file on the card that has to be at least 186 bytes. If found it writes it to the touch panel. At the end it will make a connection with the PC to allow writing of another file to the card. To write this new configuration to the touch panel a power cycle is needed.

To test the configuration remove the card and insert another one to run the original firmware of the scope. Getting that to work correctly is first priority.

The attached touch panel configuration is set for 14 sensors and 24 drivers, but I'm not sure if the set values are correct. Up to now I have only seen a panel with 12 sensors and 19 drivers.

Try this one first and report back how it works. If there are still issues we can do a course on setting the configuration.

[Atlan]

There was little information and pictures.  Why are you uploading the configuration there, the FW is already uploaded?  Boot configuration is set as?

boot 0.04. firmware v0.025x

Upload a video on YouTube of what happens after switching on.  Have you tried another sdcart?
[/quote]

https://youtu.be/CYbQw0VLc1Y
[/quote]

The line below shows the configuration data for the standard display and touch panel
0xAA 0xAA 0xAA 0xAA 0x55 0x55 0x55 0x55 0x4A 0x00 0x1E 0x04 0x17 0x00 0x1A 0x04 0xCC 0xCC 0xCC 0xCC 0x33 0x33 0x33 0x33 0x5F 0x00 0x38 0x08 0xFF 0xFF

The byte order is little endian and thus least significant byte first.

The first 8 bytes are a pre amble and need too be as shown. In the software these are seen as 32 bit values 0xAAAAAAAA and 0x55555555
The next 4 bytes are the horizontal timing setting. In the software this is also seen as a 32 bit value. 0x041E004A
The following 4 bytes are the vertical timing. In the software this is also seen as a 32 bit value. 0x041A0017
Then an 8 bytes post amble follows. In the software these are seen as 32 bit values 0xCCCCCCCC and 0x33333333
The next 4 bytes are a checksum over the first 6 32 bit values. It is a simple sum of these unsigned integers.

For controlling the touch panel the next two bytes are used. In the original configuration files these are defaulted to 0xFF, so as such no swap.
When set to zero (0x00) the cooradinates are swapped. The first byte is for the X coordinate and the second byte for the Y coordinate.

[email hidden]

Ok. It's spread across the entire screen. It would like to flip X and Y. And it also looks like the left half doesn't work.

[pcprogrammer]

In the attached image you can see which bytes are of importance. Also attached are the GT911 manuals, which also apply to the GT9157.

On page 5 of the programming manual you can see which bit of the touch reversal is for which direction.

The resolution setting (0x8048 - 0x804B) should not be changed, because the scope software relies on these to be set like this.

The number of sensors set in 0x8064 tells the IC which sensor lines are used, and the connections to the sensors are indicated in the array on addresses 0x80B7 - 0x80C4. Unused sensors are set to 0xFF, but, based on what I have seen of your panel, in your case all of them are used. In the other configurations I have seen the values used are even, so I expect these to be correct.

The drivers are set in the addresses 0x80D5 - 0x80EE. Unused drivers are set to 0xFF. In another high res panel the settings I saw seemed a bit random in spacing, so not sure if these are correct.

The direction of the touch can also be changed with the two arrays. By reversing the order of the values (see the attached high res one which comes from my second 1013D scope) the same is achieved as using the two bits explained above.

Try the one from my touch panel and see what it does. If still not good, try playing with the settings.

[email hidden]

That last file didn't do anything. It stayed the same after the previous one. I'll try to dig through it.

https://youtu.be/pFOsyXAPgzc?si=lVQSEmtMRwLv7foR

[pcprogrammer]

You have the tools and the information now, so hopefully you manage to get it working.

[email hidden]

Couldn't it be that the oscilloscope won't let me rewrite the panel? As I wrote down your first TP configuration, no change since then. Even the oldest CNF TP won't change anything. Still half without a function. No return as I bought it.

[pcprogrammer]

Strange, I have tested it with my scope and deliberately wrote an inverted configuration. It did change things and after that I was able to restore it to what it needed to be.

You can check the configuration by running the backup program again. It will read the configuration and write it back to the card. This way you can see if things have changed.

Also check the backup from the FLASH to see if the modified firmware is indeed written. At address 0x03EAA8 in the full backup the bytes should be 0x00, 0x00, 0xA0, 0xE1.
These bytes are for a read r0 onto r0, kind of a nop instruction and replace a jump to the touch panel configure routine.

This modification would most certainly also be needed with most of the 7 inch touch panels available on Aliexpress or Banggood for that matter.

[email hidden]

I'm reporting. No success yet. CNFs that contain FF lines cannot be written. Your program says "DONE" but no change in the panel. Writing not done. I also tried reading the old panel, writing to the new one. Unable to write. HEX in the panel does not change. The only CNF that is written to TP is the first one you sent me, it extended Y but completely messed up X. I tried flipping bits in this one, no response.
Your last CNF also has FF set. Unable to write.

[pcprogrammer]

What you can try is to set the first byte to 0 and make sure the last byte is 1. This should reset the version to A (0x41). After that you can try new settings with increasing this version number.

For the X direction the driver settings are most likely wrong then. But what they need to be is the big mystery. The manual has no information on that, and I extended it based on what I have seen in my panel with more sensors and drivers than the basic one.

What you could try is measure the I2C signals with your other scope to see if maybe there is something wrong with them. There is this issue with the capacitor that is connected across the SCL and SDA lines. Maybe removing the capacitor solves an issue that made you believe the original touch panel is defective.

Always tricky, this kind of problems. Even if you bought the one found on Aliexpress, there is a big chance the configuration needs adaptation to work with the original firmware.

[waterstarrunner]

I have an interesting one...

I got the offset calibration failed check hardware message that was demoed back on page 73.

Calibration seems to run happy enough on the fnirsi software, and when I check the behavior of my dividers they all seem to be behaving as they should in both firmwares (except the fnirsi 50 mv/div setting where it has 100mv/div  behavior)


Any thoughts on how to overcome this?

ps- yeah, my front label is Utrnix brand and a yeapook original bootscreen logo

[Atlan]

This is the output of this function uint32 scope_do_baseline_calibration(void).  The subroutine tries to set the pwm output so that the value at the output of the converter corresponds to the middle of the ADC 127 range. Try to measure the reference voltage on the AD converter, what is its value.  And measure the voltages at the AD converter input. The operational amplifier on one of the channels may be damaged or the resistors on the BNC connector may be damaged.