54 minutes ago, Coulomb said:

OK, then JTAG is your friend.

It looks like ST-LINK is the original JTAG emulator for ST ARM devices, and GigaDevice makes a similar thing called GDLink. So you probably want inexpensive devices based on GDLink. This seems to be one such:

https://www.aliexpress.com/item/1005004576805005.html

It's totally not clear to me what software you get with it, or what you are supposed to find yourself and download. It doesn't sound like it's tested on a whole lot of GigaDevice chips, but for the purposes of flash programming, I'm guessing that it should be good enough.

You will need some link wires as per the Boom! post; take note of the one with GND, DIO, CLK, and 3V3 (partly obscured) in it, and locate that 5-pin connector on your display board. Make sure you get the right orientation (observe the notches). Or you could make up a custom connector with the 10-pin header at one end, and a suitable JST plug at the other end; you might be able to make it from two off-the-shelf cables.

It might be worth downloading the manual before committing to a purchase, so see if you (perhaps with the forum's help) can figure out what you need to do. If you don't like this one, just do another search for GDLink and GigaDevice.

There is possibly the bootloader problem. But it seems to me that your bootloader will still be there; if necessary you could read it out (I recommend that in case you accidentally do a bulk erase). You should be able to erase and flash only the non-bootloader flash segments. That's assuming that they haven't protected the firmware as yet.

Basically, it looks pretty doable.

Ok. I will order this then. Where can I ask for help programming this then? 

53 minutes ago, Gilberto said:

Where can I ask for help programming this then? 

I have no idea if there is an ARM JTAG forum, but I can do my best right here.

20 hours ago, Coulomb said:

I have no idea if there is an ARM JTAG forum, but I can do my best right here.

seems as u can use a st link to program? 

Hi all. I updated more mpp and easun inverters 8kw, and i realised that inverters with 2nd firnware 112.15 works great only with thr firnwares that have arenaflash tool app, and others with 1st 46.05 and 2nd 12.06 works only with reflashtoolx. DONT COMBINE THE FILES BETWEEN THE TWO PATCHES ! Here are a lot of versions for twice inveters made by George and Coloumb.

17 minutes ago, add1c7ed55 said:

Hi all. I updated more mpp and easun inverters 8kw, and i realised that inverters with 2nd firnware 112.15 works great only with thr firnwares that have arenaflash tool app, and others with 1st 46.05 and 2nd 12.06 works only with reflashtoolx. DONT COMBINE THE FILES BETWEEN THE TWO PATCHES ! Here are a lot of versions for twice inveters made by George and Coloumb.

So mine is version 2? 

2 hours ago, Gilberto said:

So mine is version 2?

U didnt need to update the display, only 1st firmware, u upgraded the wrong firnware, for u is ok the firnware that Coulomb made, 92.05 with arenaflash tool. U can try it now, but now u have changed the disply firmware and now i think they dont comunicate.

4 hours ago, Gilberto said:

seems as u can use a st link to program? 

Interesting. Though for me the takeaway is that there are differences, specifically the bootloaders are not compatible.

3 hours ago, Gilberto said:

So mine is version 2? 

I'm not sure that we understand the issue as yet, so it may not be so simple.

I asked what your original firmwares were, and you posted a screen shot showing 46.05 (main) and 112.14 (secondary/display). That's one of the combinations that I thought was impossible. I thought 46.05 would have been a reflashtool main firmware, yet the display firmware has a "1" in the hundreds column. That sounds like it needs the ArenaFlash tool. But it looks like it can't be as simple as that.

BTW, @Gilberto, can you confirm that those two versions were before you updated anything? You said you updated to 90.06, so that seems like it was before any updates.

6 minutes ago, Coulomb said:

I'm not sure that we understand the issue as yet, so it may not be so simple.

I asked what your original firmwares were, and you posted a screen shot showing 46.05 (main) and 112.14 (secondary/display). That's one of the combinations that I thought was impossible. I thought 46.05 would have been a reflashtool main firmware, yet the display firmware has a "1" in the hundreds column. That sounds like it needs the ArenaFlash tool. But it looks like it can't be as simple as that.

BTW, @Gilberto, can you confirm that those two versions were before you updated anything? You said you updated to 90.06, so that seems like it was before any updates.

I really don’t know at this stage what firmware there was at the beginning. 
I did an upgrade without checking this. 
this is what happens too noob people when trying to solve something and then has a bigger problem 

1 minute ago, Gilberto said:

I really don’t know at this stage what firmware there was at the beginning. 

Ah, OK. Better to know this than to try to make theories based on incorrect information.

It looks like there may be 4 combinations: 2 types of DSP chip, and two types of display chip.

The DSP could be the TMS320F2809, with the dual power supplies (3.3 V and 1.8 V, so the control boards have the two  voltage regulators), or the TMS320F28066 chip (with the single 3.3 V power supply, so only one voltage regulator on the control board).

The Value line models (e.g. VM II, VM III, VM IV) use the TMS320F8062 chip, with only 128k bytes (64k words) of flash memory. Also only a single power supply.

I can tell the difference in the firmware, by the call to 0x3D7C80 (just before the start of flash memory), which only the '28066 firmwares have.

The display chip could have an ST32F107 chip (possibly an ST32F105 chip would do), or a GigaDevice GD32F105 chip (possibly a GD32F107 would also work). It looks like these are pretty compatible for userland code, but bootstrap loaders are different. Maybe the bootloaders are located at a different address, because if all the differences are in the bootloader, and the bootloader never gets overwritten (JTAG programming possibly excepted), then there should be no problem. I suspect that some of the peripherals are either at different addresses, or have subtle differences, that the simple temperature display example in the video is not affected by. So you can't mix firmwares designed for other chips.

There must be some differences in main firmware update protocol too, because it seems to be important to use the correct reflash tool. Though if the protocols were vastly different, bricking would presumably not be possible.

I don't understand why it's important to match the reflash tool (which affects the DSP firmware) with the right display firmware (which should just talk to the DSP via RS-232 commands, and those should not depend on any chip version).

Maybe you can only use the new display chip (and its firmware) with the new DSP chip (and its firmware and reflash tool). I thought I was going to sort everything out with this post, but I find I'm just as confused as before.

But surely we'll get to the bottom of this mess soon. Thanks all for helping figure this out.

11 minutes ago, Coulomb said:

It looks like there may be 4 combinations: 2 types of DSP chip, and two types of display chip.

The DSP could be the TMS320F2809, with the dual power supplies (3.3 V and 1.8 V, so the control boards have the two  voltage regulators), or the TMS320F28066 chip (with the single 3.3 V power supply, so only one voltage regulator on the control board).

The Value line models (e.g. VM II, VM III, VM IV) use the TMS320F8062 chip, with only 128k bytes (64k words) of flash memory. Also only a single power supply.

I can tell the difference in the firmware, by the call to 0x3D7C80 (just before the start of flash memory), which only the '28066 firmwares have.

The display chip could have an ST32F107 chip (possibly an ST32F105 chip would do), or a GigaDevice GD32F105 chip (possibly a GD32F107 would also work). It looks like these are pretty compatible for userland code, but bootstrap loaders are different. Maybe the bootloaders are located at a different address, because if all the differences are in the bootloader, and the bootloader never gets overwritten (JTAG programming possibly excepted), then there should be no problem. I suspect that some of the peripherals are either at different addresses, or have subtle differences, that the simple temperature display example in the video is not affected by. So you can't mix firmwares designed for other chips.

There must be some differences in main firmware update protocol too, because it seems to be important to use the correct reflash tool. Though if the protocols were vastly different, bricking would presumably not be possible.

I don't understand why it's important to match the reflash tool (which affects the DSP firmware) with the right display firmware (which should just talk to the DSP via RS-232 commands, and those should not depend on any chip version).

Maybe you can only use the new display chip (and its firmware) with the new DSP chip (and its firmware and reflash tool). I thought I was going to sort everything out with this post, but I find I'm just as confused as before.

But surely we'll get to the bottom of this mess soon. Thanks all for helping figure this out.

Ohh this seems out of my confort doing all this. This is all Chinese for me 😂

3 minutes ago, Gilberto said:

This is all Chinese for me

That's OK; it's partly for myself to write down what I know, but mostly for others who are more technical to comment on. The damage is unfortunately done for your machine; I'm trying to prevent this happening to others.

I'm thinking now that you have a machine with the new DSP and the new display chip. When you flashed the main firmware, it was an old firmware, 90.06, so that's why you got the comms error. When you flashed the display firmware, you used 12.13 (that's what is in the rar file you used), and that's a firmware for the ST chip, and you have the GD chip.

I updated with succes 46.05 with 112.14 with arena 90.05. All was ok.

What a mess. If i had Time i will check my own display panel to check the chip because It's strange it works for me

18 minutes ago, sharkut said:

What a mess. If i had Time i will check my own display panel to check the chip because It's strange it works for me

 

36 minutes ago, sharkut said:

What a mess. If i had Time i will check my own display panel to check the chip because It's strange it works for me

What firmware u use and what program? Can u give me a link? 

5 hours ago, Coulomb said:

That's OK; it's partly for myself to write down what I know, but mostly for others who are more technical to comment on. The damage is unfortunately done for your machine; I'm trying to prevent this happening to others.

I'm thinking now that you have a machine with the new DSP and the new display chip. When you flashed the main firmware, it was an old firmware, 90.06, so that's why you got the comms error. When you flashed the display firmware, you used 12.13 (that's what is in the rar file you used), and that's a firmware for the ST chip, and you have the GD chip.

Yea I know! I am very thankful for your help! I ordered the gdlink but it takes time to arrive. I will buy a stlink locally tomorrow to try out. But I will need some guidance 

Recieved the st link. Will try it out later. Any link how to use it on the remote controller? 

30 minutes ago, Gilberto said:

Any link how to use it on the remote controller? 

Yes, as I've indicated before, it's all in the Boom! post:

Note in particular this image:

The bottom pin that's slightly obscured is the 3V3 pin. I assume that you power the display board via the JTAG adapter only.

Do you have any software with the JTAG? Or links to software?

 

Use ST Visual Programmer

http://www.bdtic.com/st/STVP.html

6 hours ago, Coulomb said:

Yes, as I've indicated before, it's all in the Boom! post:

Note in particular this image:

The bottom pin that's slightly obscured is the 3V3 pin. I assume that you power the display board via the JTAG adapter only.

Do you have any software with the JTAG? Or links to software?

 

Hello! I only recieved the stlink. No software. Do u know with one is it? 

6 hours ago, Coulomb said:

Yes, as I've indicated before, it's all in the Boom! post:

Note in particular this image:

The bottom pin that's slightly obscured is the 3V3 pin. I assume that you power the display board via the JTAG adapter only.

Do you have any software with the JTAG? Or links to software?

 

Gives me this error. Something that I am doing wrong? Im a total noob doing this! 

4 hours ago, Gilberto said:

Gives me this error.

Could you post a screen dump, please? That photo is extremely hard to read.

I see you found some software; which one?

You seem to be powering the display board, at least the 3.3 V part of it. My guess is that you haven't connected the wires correctly (3.3 V and ground must be correct, so it would be the other two), or you need to try the other protocol. I don't know ARMs at this level. It's possible that it just doesn't know the GD chip.

Can you set the device to an STM32F105, perhaps in the drop down box in the toolbar?

Use GD-Link for GD32, not work with ST-Link, also need aplication for GD32

i programmed GD device with jlink interface

Edited November 17, 20223 yr by mihaigsm2003
added jlink