iFlight G071 E55 4in1 64k bootloader

[xagos]

I have unlocked and erased an iFlight Blitz E55 esc with STlinkV2 in Stm32Cube, to flash it with the last G071_64K Bootloader.
After that process, the esc(s) are not recognized by all Firmware update tools (Am32.ca etc.) I have tested.
Changing the bootloader to the "not 64KB" (v8) version seems to work - firmware can be flashed via FC passthrough, but some major information/feedbacks (description in the green boxes on the AM32.ca page) are missing.

[xagos]

Today I have testes the behavior of the actual Firmware "AM32_IFLIGHT_BLITZ_G071_2.12" on my iFlight Blitz E55 G071:
the motor are emitting a start sound (beep), but I am not able to connect betaflight to the ESCs - pass through (flashing firmware etc) is working, but I do not have the expected information in the AM32.ca config tool:

When I use the ESC_Config_tool I get:

but I am not able to drive the motors...

Is there a way to debug this?
Do I have to install Keil and compile a specific version for my ESC?
I thought, that the iFlight BLITZ E55 would run with the precompiled firmware out of the box, after installing the bootloader.

Regards...

[AlkaMotors]

There are two g071 versions of the iflight blitz. There are ones made with the g071 and ones made with the g071N variant. If you have the g071 standard version It uses the pb4 bootloader and g071 blitz firmware. Currently you have a pa6 input pin bootloader flashed but the firmware for the pb4 input.

[AlkaMotors]

The blitz firmware for the n variant is not released yet. Can you join the discord and we can give you test version for that esc.

[xagos]

Ok - the PB4 bootloader was my fist try, but than no esc was found. So PA6 is installed but the firmware is the wrong version. Never ever have used Discord before, but I have created an account now... Tanks for your support ;)

How do I get the .hex-File...?

[bhuism]

@xagos I think you can download it here: https://am32.ca/downloads

[xagos]

Thank you - I had access to the file via discord and I have successfully tested the G071N version (2.16RC3) for the iFlight E55 ESCs. Regards...

[xagos]

iFlight E55 G07N Test

Bootloader: STM32_G071_BOOTLOADER_PA6_V8.hex (PA6 for the "N" Version, there are variants of the iFlight K55 with a different pinout)
Firmware: AM32_IFLIGHT_BLITZ_N_G071_2.16.hex (RC3)

• erased Flash and programmed bootloader with the STLink and STM32Cube (linux) (but used STLink (win) to unlock the flash)
• flashed firmware with the ESC_Config_Tool_1.82 (AM32.CA did not run reliably)
• loaded default settings
• changed parameters (KV etc) with the ESC_Config_Tool, write, reboot...
• tested communication with the FC (betaflight 4.5.1 dshot600): OK
• checked motor behavior without props (sound, vibration, rotation direction, fc-feedback[speed, temp]): OK
• analog current feedback: OK
• ESC UART telemetry: 4x single Voltage but no total voltage
• ESC UART telemetry: 4x single Current (ca. 12.0A at zero speed), no total value (0.00)
• maiden test with props (hoovering, zero throttle, max throttle): OK
• maiden flight with standard PID and filter settings from the "old" BLHeli32 setup: OK

I could not find anything that "feels wrong" - the AM32.ca configurator did not show the bootloader and software version (no infos inside the four green (matched parameters) ESC-Boxes). Probably only a lookup issue...

Subjective impression compared to the BLHeli32 setup: same responsiveness but less power (only tested with 15degree timing). So I have tested the auto-timing-advanced feature of the RC3 - and this makes a huge difference compared to the initial values. It is hard for me to compare the dynamic of this version to the "old" BLHeli32 setup but with the advanced-timing option, it was feeling great.

After the second successfully flown battery pack, I have checked the temperatures of the motors (again) and everything was cold.

[bhuism]

@xagos can you please post a picture of the location of the SWCLK and SWDIO pad location?

[xagos]

Sorry - I did not took a picture and the ESC is "deep inside the copter" ;) But it is very easy to find next to the uC of each ESC... I did not solder it - i have used test pins with internal springs for the DIO / CK signals

[bhuism]

No worries, I got it all to work, thanks!

[benderl]

As I have the E55 still laying on my desk, I can post a picture of the pads. Red is CLK, yellow SWD.
Flashing was quite easy. Thanks to @xagos for the docs! The N-Firmware is already included in the last 2.16-rc3.

[benderl]

I still only have the battery connected to the esc. Configuring BF gives me some strange values for motor currents.

Voltage seems to be fine, but currents should be zero right now. Is this a known issue or will this be ok after connecting the motors?

[xagos]

I have mentioned exactly the same strange values of telemetry data in one of my feedbacks - I am using the FC-ADC capturing instead...

[AlkaMotors]

Each esc would need a current shunt to show individual current. There is no connection between the single current sensor on the board and the individual esc's. The esc are just reporting a floating unattached pin. Use the current sense direct to the fc from the 'cur' pin. There are iflight blitz e55 g071 single esc's that do have the current sensor attached but the not the 4 in 1.