Setup eePe to use with Bootloader and FTDI

[Saschko]

Hi all
I have a turnigy 9xr using er9x firmware.
Now I wan't to use the Bootloader with the FTDI-Cable
and downt know how to setup eePe correct.

When I try to start the Bootloader I got "Stopped" in the Display.
Is that correct?

Any help would be much appreciated.

Saschko

[jhsa]

I have a 9X with er9x as well, but mine says "bootloader" when in bootloader mode.
What do you want to do? Read the eeprom to/from the computer? Flash the firmware?
If it is a real FTDI with TTL logic level, not a RS232 adapter, you can connect it to the MISO, MOSI and GND on the 9XR programming plug.
In eepe confugure
Programmer - arduino
Chip - m128?
Your com port
Try to read the eeprom like this. Not sure if we need something in "Extra arguments" Need to try it again

[Saschko]

Whow, thanks for the fast answer.

Yes it is a real FTDI with TTL logic, and now I know how to setup eePe.

If I have no or the wrong bootloader, what can I do?
Where can i find the hex of the right bootloader?

[Saschko]

OK, I tried it, but AVRDude said something like "not in Sync".
Seems that I have no or wrong Bootloader

[jhsa]

Mike, I'm a bit confused here.. my m2561 radio with the latest test firmware, shows "Stopped" when in bootloader mode.
My m128 radio with the latest test firmware shows "Bootloader" when in bootloader mode.
Do they have different bootloaders? Also the OP has an 9XR radio but his radio say "Stopped". So, it looks like the bootloader changed? because I have the latest test version of the 128 and mine say "Bootloader"

I flashed the radio using the Usbasp, so the bootloaders were also flashed..

Thanks

João

[Saschko]

I also Updated with USBasp. I have installed version 1.127 er9x-r817.

Can I do any testing or help in other ways?

Thanks

Sascha

[MikeB]

At present the bootloader is only present in the '128 version of the firmware, it isn't in the '2561 version as that needs extra code to allow for the extra flash, you cannot directly address all the flash.

The 9XR stock firmware is actually the version for the M64 processor, only the recent '128 versions have the bootloader in them.
I'd guess the OP still has a version of er9x for the M64.

The 9XR should now be flashed with er9x-128.hex, but the EEPROM should be backed up first as the '128 version will update to using the 4K of EEPROM instead of the 2K available on the '64.

Mike.

[jhsa]

Oooook

But then, when I was testing the arduvoice module, I was having problems with the serial, and if i remember you told me to put the radio in bootloader mode so it didn't load the serial lines, but it doesn't have bootloader?
In fact, if I try to talk to the sd card from eepe with the radio started normally, the serial doesn't work.. If I start the radio as if it was in bootloader mode, the serial works. So, even without bootloader the radio doesn't load the serial lines? why? because er9x still didn't start as it is waiting for the bootloader? I'm confused now

Thanks

João

[jhsa]

I also Updated with USBasp. I have installed version 1.127 er9x-r817.

Can I do any testing or help in other ways?

Thanks

Sascha

Ok, but did you install the r817 for the m128 chip? or for the m64?
Your 9XR might have a m128 chip unless it is one of the first batch that shipped with an m64

[Saschko]

Thanks Mike.

After installing er9X-128.hex I get "Bootloader" on the display.
But I can still not read the Eprom-Data with the FTDI-Cable.

I get:
=================================================================================
AVRDUDE gestartet
C:/Program Files (x86)/eePe/avrdude.exe -c arduino -p m128 -P com5 -U eeprom:r:C:/Users/Client1/AppData/Local/Temp/temp.hex:i
=================================================================================
avrdude.exe: stk500_getsync(): not in sync: resp=0x00

avrdude.exe done. Thank you.

I tested to change RXD and TXD, but with both I got no sync.
Anything I can do now?

[jhsa]

Hmm, I have just tested mine and it worked.. Well, I had the RX and TX reversed at first and it gave me the same error as you had, but then it worked.
make sure you connect ONLY the TX, RX and GND from the FTDI.
My settings in eepe are
Arduino
m128
com19 (your com port here). I didn't remember if we needed some options in Extra arguments. But we don't.
We do really really really really really really, need profiles in eepe so we can just load the profile with all the settings for a given operation, different programmer, different radio, sound module, etc.

Start eepe, connect the FTDI to the computer, turn radio ON in bootloader mode, try to read your eeprom..

João

[MikeB]

Still worth trying -b 115200 in the extra arguments.
Do you have a telemetry mod fitted?

Profiles are NOT quick and easy to implement. I had a bit of a look a few days ago.

Mike.

[jhsa]

thanks Mike. I do believe they are not easy to implement.. But I think it is one of those things that are really necessary now that we use eepe for other operations as well..

Thank you for looking

João

[Daedalus66]

Profiles would be really helpful!

[MikeB]

I'm making a start towards adding 'profiles' to eepe. As a first step, I'm combining the "Preferences" dialog and the "Burn|Configure" dialog into a single dialog.
Some of the preferences options, like "show splash screen" (the eepe one) are not profile specific.

Mike.