samoraj wrote:Ok...let' go step by step
1. I flashed with EN open9x-frsky on OPEN9X wiki binaries. I've tried with open9x as was attached above. Still blank screen
OK. Well that should work, once you fix the firmware in your programmer -- assuming the one you have is hardware compatible with the firmware you found in the other forum post. Hope so.
Oh and quite right -- the sodding thing does not report any errors! It took my two weeks of logic analyser and digital scope work to figure out WTF was going on, when we were developing the gProg programmer.
2. I didn't use [down] and [up] while power up because I didn't knew I should.
Oh. Well, I did include all that information in previous emails. I know my emails are often quite long. But they're long because they contain a bunch of good and important information.
My understanding of bootloader was that this is installed program to boot directly with USB connection
(Image1)
The attachment image1.jpg is no longer available
it's not working directly to my computer..
The purpose of the bootloader is to replace the gProg programmer -- or any other AVR programmer that might connect to the 6-pin ISP header. The bootloader system is more reliable and much faster than an external USBasp programmer, too.
If you want to use the bootloader again (
highly recommended) then you need to first use your repaired AVR programmer (or replacement gProg, when it arrives) to install the bootloader hex file (attached).
IMPORTANT: Once the bootloader is installed, you should never use the 6-pin AVR programming header, since that erases the bootloader (the whole chip, in fact) before writing the hex file in question. Instead, you should hold down [UP] and [DOWN] when powering on the radio, to put the G9X board into USBasp compatible, self-programming mode.
3. I'm using HK USBASP (image2)...maybe this is the problem..although no error is shown while burning .hex
Just so others who might come to this post first, can know ... to the best of my knowledge, that programmer has the same buggy firmware that almost all USBasp programmers out there have and will NOT work properly on ATmega2560 chip, unless you re-flash with fixed firmware. You mentioned already that you've found a post (above) with information on how to do that.
To be clear. Last time I checked, the firmware available from the inventor of USBasp still did NOT have corrected firmware. Hence,
ALL USBasp programmers based on that project (and there are many) will NOT work reliably with AVR chips having more than 64K of Flash. I have communicated with them, but got no reply. *shrug*
4. My settings in companion are:
... all fine to me.
Where am I doing things wrong??

To be perfectly frank, the main thing you are doing wrong is not reading all my previous emails carefully and completely -- emails (or forum posts) in which I've put a lot of effort, to help you avoid all these problems. That is to say, I have mentioned ALL of the above before -- probably twice. Never mind though. We're all human.
So then. The steps to take now are ...
1. Reply here to tell me exactly what appears to be wrong with your gProg -- just so I know. I'm sending you another one anyway.
2. Either wait for the new gProg or re-flash your HK programmer, to get that working correctly.
3. Use the working programmer to install the bootloader hex (attached)
4. From then on, use only the bootloader for companion9x. Keep an external programmer on hand, only in case something goes horribly wrong and you need it some day.
Bryan.