T8SG Lite

No startup screen anymore. I've got 2 choices: 1. DFU Mode or 2. USB Mode. So what to do?

Does anyone has a tip of how I can flash the RC to the old status back?

Like I sad before the only modes still working is ENT Button + ON/OFF to enable USB Mode or SEL Button + ON/OFF to enable DFU Mode.
File system is not accessable at all via desktop nor formatting possible.

Hope someone has a solution.

Any deviation radio consist of two parts, the firmware file flashed to the Tx, using the bootloader tool.

Then in USB mode the Tx, works like a drive on this drive there is the filesystem inc model files settings files etc, all is needed to function properly.

When not closing the USB correctly or unplugging the file system can get corrupted. Prrobably this is what happened.
So in that case you have to, format the transmitter USB drive, default settings is fine, than copy the directories and file structure to the USB drive.

Disconnect using, windows disconnect USB, before unplugging.


You could put the latest nightly build, but better than also flqsh latest firmware.

Hi Fernandez,

pretty quick reaction and thanks for giving me this explanation.

I have no access to the filesystem at all. Neither via Windows nor via Linux. Information I got is: system needs formatting.
Whenever I try to do that, command breaks with the comment: cannot access, formatting not finished.
I even changed the Flash-ROM on the board so I'm pretty sure that HW isn't the cause for that behavior.

I'm all ears for any further suggestion.

By the way I'm pretty disappointed about the reaction of jumper. This was a brand new RC and my Mail has not been answered yet.
I guess, next RC isn't Jumper anymore.

Cheers
Michael

Go to the User Manual link in the left column for Devo 7e/10/12e (similar to t8sg). Follow the directions in the Installation section to do a fresh install of deviation firmware (available in the Downloads link). That should get the tx going as long as it's not a hardware problem.

Still strange behaivior. Press ON/OFF button shortly will put the red LED on but then goes off. Pressing the ON/OFF half a second, then it stays on and with a short delay the green LED turns on, too,

Can get in contact to the Radio via the DFU Utility but Upload Util does not work (only to "unknown" transmitter.

For today I'm giving up and I guess it is a more serious issue to solve.

Thks. hexfet & Fernandez for your first hints.

Maybe I make a short video to show of what is going on.

Cheers for today
Michael

(https://c.web.de/@337599667434952044/A3lyCU5RTvO0NYPOLi_Dlw)

Below this link a short video explains the situation.

In short: No access to the file system via USB. Any try to format filesystem new fails. Beside this you have access via DFU and USB. With the upgrade tool you never ever see a valid Device (either Devo 7 or Unknown)

Can anybody help? Does anyone have the binary files of the CPU to give it a try via ST-Link2?

I'm all ears.

Try downloading the driver Installer here . Install the Walkera driver, then see if the tx is recognized by Windows in DFU mode (EXT + power). If so perform a full install.

Your suggestion was one of the first things I did. Unfortunately without success. I can enter only via dfu mode the access to the java upgrade tool. Then I should see the actual device in the headline of the menue. The only device I see is either "devo 7" (default) or "unknown".

Please read my inputs above. By the way the explanation according to 7e I followed step by step. I cannot get access to the file system of the t8sg. Neither with the upgrade tool nor via the dfu tool. Seems that latest the access to the file system is complete blocked. I even checked on HW Layer to change the flash (in my case winbond 25q32) but that didn't worked either,

The only chance which comes into my mind is to flash the CPU ST32f303 with a new SW/firmware or whatever you call it. For me it seems that something in the inner softwarestack is corrupted out of whatever reason and so the communication in its fundamentals is disturbed.

If anyone has an idea of how to get it running again, I'm delighted.

Hi vlad_vy,

did via dfu the upgrade of the modified file you provided. Shut off the device and tried to switch on again by pressing the ent button. This time no usb logo appears. Nevertheless access to file system is prohibited and a pop up screen asks for formatting. I see a different behaivior with repect to the reaction by pressing the on/off button and by entering the usb mode.

vlad_vy you respond pretty quick, thats super kind of you.
From what I see the SPI Flash is from Winbond 25Q32JV and don't forget we are talking T8SG Lite here.
So than the utility does not cover the content of the flash.

Your Utility addresses 16MB and the actual one 32MB, is that correct?

Do you have a solution for the other size?

Any chance to get a modified update covering the larger memory space?
By the way, does this influence the content to be downloaded, too?

Quick answer. Again thanks for you reaction.

I'm not a developer nor a sw specialist. I guess the sw has to be compiled by including those specs you have given. Is there an easy way to call a make instruction and the process will generate a binary file with the specs according to my HW? T8SG (lite) is (as far as I know) based on the same motherboard. This leads to similar definition for most of the HW. The difference might be the SPI ROM(Flash). Display, analog Ports and SW ports should stay the same.

Can you give me a helping hand how to set-up the compiling enviroment and show me the files that needs adaption?

Hope it works.

Try to set-up the compiling enviroment and make the suggested changes. Maybe I go with Ubuntu to keep on PC for developments.

Can you give a hint in which file I have to put in the SPI flash information, the winbond one?

Container is set-up. does compiling for a selected device (e.g. T8SG_V2) but it seems that source is not local but online.
How can I change the source (e.g. target_defs.h)?

I like the idea with the container! Great thoughts behind to make even for dummies live easier!!!

I may sit down an explain my findings so far to help other overcome first hick-ups with the system.

I guess it was you who wrote that interrupts can cause a corrupted file system. It happend me by switching in parallel trimm and on/off button.