ERSKY9X Coding

[jhsa]

Mike, about the encoder wheel and centre button functions. Shouldn't the encoder wheel work on the bootloader mode menu and maintenance mode menu??

João

[tsenecal]

tested the encoder wheel operation on the bind button... works as expected.

[MikeB]

Adding the encoder on the boot and maintenance is something on my list. Not straightforward as, on things like the confirmation screen I normally use MENU LONG to action and EXIT to cancel. You can't use a single button as easily, I need to look into possibilities.

Adding PPM2 and COM2 isn't quick to add as I need to sort a special driver for COM2 to handle serial, non-inverted operation.

Mike.

[jhsa]

Thanks Mike, hopefully sometime in the future there is the possibility to flash the modules that are installed internally.
These can't be removed for flashing. In my case I had to install a connector in my radio's case and make an adapter with an FTDI. It would be nice if this wasn't needed at all..

João

[ReSt]

Tomorrow I will try if all of the testversions give me this problem or if it was introduced with a certain version.

Reinhard

Now I know a little bit more about my problem and why you don't get it.

Mike pushed all the modified source files to github on 2017.03.19 00:03:25

I did a clone from the repository on 2017.03.20

Into this database I added my private modifications (a lot of cosmetic changes but also some functional ones like enhanced templates and some modified menues).

I do not touch the eEprom. It stays the same for all of the following tests.

When I flash my radio with this newly created fw, I get the sound problem.

From that on, flashing any of the supplied testversions (a1, a2, a3, a7, b1, b4, b5, b6, b9, c3) will fail with this same problem.

Then, when I flash (my privately modified) version 820, the problem is gone, voices work as they should.

And now all the testversions that did fail before, do work.

That looks like some setting in the CPU is "changed" by my code and is only readjusted by r220 but not from the testversion ???

Does that make sense?

Reinhard

[jhsa]

You mean, version 220, not 820?

Recently Mike change the way Audio is generated and he added new features like the Music player for example. You also have a separate volume setting for the vario, and I believe there were other modifications to the Audio (beeps) as well..

João

[ReSt]

Yes, r220

Reinhard

If helpful, I could upload my compiled version as well as my source code.

[MikeB]

Any possibility of extending this wonderful feature also to PPM2 and COM2 to flash internally installed Multi Modules??

Is your connection to COM2 using inverted or non-inverted serial data?
With all the different possibilities of wiring up, this could get quite complicated. The bootloader, to be compatible with FTDI type devices, operates with non-inverted data. Maintenance mode currently assumes, on COM1, that there is a hardware inverter in the radio.

Mike.

[MikeB]

If helpful, I could upload my compiled version as well as my source code.

Perhaps just post your EEPROM both with and without the problem so we may look to see if something gets changed.

Mike.

[jhsa]

Mike, I have that module (STM32) installed internally in the 9XT. COM2 in the 9XT accepts non inverted data, so that is what I'm using.
Also in the Ar9x board you can connect COM2 as inverted or not inverted, depending on what you need.. Multi module normally needs non inverted anyway, but it can be compiled either way..

Thanks
João

[ReSt]

Here are the eeproms

Reinhard

eeproms.zip

(4.94 KiB) Downloaded 228 times

[MikeB]

The only differences to the general settings and the current model are those where the total time is stored.
At the moment I can't think what is happening.

Mike.

[ReSt]

I don't know if this can be a hint.
When the underrun occurred, powering off takes much longer then otherwise.
Normally the "Shutting down" message is displayed less than a second and when the error happened, it takes more than 7 seconds.

Reinhard

[MikeB]

An added feature is the shutdown voice message. To allow this to be announced, the shutdown stays displayed for longer while the audio is active. It does have a timeout in case the audio doesn't stop. I would guess the audio is flagged as active after the underrun, so this causes the long shutdown time.
Something may not be tidying up after the underrun, which is then blocking all voice output.
When the voice stops, do you get any beeps?

Mike.

[ReSt]

No beeps after the underrun.

But why remains the problem active, when I flash a known working fw (> r220).
There must be something permanently set in the cpu that is corrected with the r220 fw and no longer with the successors

Reinhard

p.s which keys do I have to hold at power on to clear the eeprom?

[MikeB]

The CPU doesn't have any non-volatile storage, except for the flash. The EEPROM only differs in the total time values, which are expected to be different. The SD card is the only other place I can think of where something is stored, but I can't think what at present might cause your problem.

There is no built in way of clearing the EEPROM. To completely blank the EEPROM, you need to write a 512K byte file that contains 0xFF everywhere. I can create such a file if you need it.

Mike.

[ReSt]

I now found, that I can even make the prov221_c3 code fail. Even if i flashed the r220 code before.
It's harder to make it fail than with my (privately modified) code. You have to toggle some switches repeatedly and shift the throttle stick forth and back while the startupmessages are playing (Welcome to Ersky9x, throttle not in the correct position, switches are not in default position).
So probably nothing to be retained somewhere to make it fail.

I did not succeed to make it fail while the timer(1) is counting down (messages are shorter).
Normally when the failure occurs, the voice is interrupted and stopped immediately.
But I noticed two times that it seemed that the voice ended normal. But status2 screen showed a voice underrun and beeps and voice had stopped working.

I can create an empty file myself. Thanks

Reinhard

[jhsa]

Reinhard, before you do something else please press up long to go to the debug menus. Now press left or right until you get to the SD Card status menu.
On the first line you have "Present Yes", and then on the same line at the end (right side) you have a number. What number do you have? I have 32.

João

[ReSt]

It's 32.
But I just verified, in case the voice underrun has happened, it is 0 !!! (Albeight it is flagged as present and ready)

Reinhard

[MikeB]

That number is the cluster size on the SD card. A 0 means there is something going wrong reading the SD card.
Do you have another SD card you could try?

Mike.

[ReSt]

Thanks, Mike, thanks João

It is working now

I tried the card from a different radio that I formatted and copied the files on; and it worked.
Then i reformatted the original card and copied the files onto it; and it also works.

So it looks like the performance of the card is a little bit more critical with the newer fw ?

Reinhard

[jhsa]

Use the free "SD Card Formatter " tool to format your cards.. Don't use windows.. Get it here:

https://www.sdcard.org/downloads/formatter_4/

João

[MikeB]

I've looked into adding encoder support in the bootloader. More difficult than elsewhere as the bootloader cannot "know" what divider you need on the encoder.

Mike.

[jhsa]

I can see the problem.. Is it not possible to do a 1 time test/calibration and store it somewhere?

Thanks

[Kilrah]

The bootloader has no access to any storage it may use at this point.

[jhsa]

It was just an idea.maybe Mike finds a way. He is very good at it. We've seen it happen many times
He said it will be difficult, didn't say impossible. If it was impossible he wouldn't be looking at it

João

[MikeB]

If I use a divider of 4, the worse that happens is you need to rotate the encoder 4 clicks to move up/down one place, but it will work.
The encoder I have in my SKY board Tx needs a divider of 4.

Mike.

[jhsa]

Most radios of us use the 7 way encoder, which needs a divider of 2. On my PRO I have one that needs a divider of 4. Those we can buy on ebay that look like a pot.. The 7 way encoder doesn't fit on the PRO..

Mike, there is a little problem with the 9xtreme when enabling the hardware menu. If we take a bit longer holding the left horizontal trim at power ON, it will play the voices assigned to the THR switch and the hardware menu is not enabled.
If I release the trim only a second after turning the radio ON, it enables the hardware menu and no extra voices apart from the welcome message and model name will be played.

This happens only with the 9XT.. Don't know about taranis.

Thanks

João

[MikeB]

It's supposed to stay showing "Hardware Menu Enabled" until you release the trim switch, but I've missed out re-triggering the watchdog so you get hit by a watchdog reset that skips the waiting.

Will be fixed in "c5".

Mike.

[jhsa]

Thanks Mike.. Caught that one while trying to find out the divider the encoder on this radio used

Would you mind explaining the picture feature again please? How big/resolution the picture must be and where must it be placed?
I will try to test it..
Thanks

João