Chrskly: Chrskly moved page Zombiverter programing to Zombieverter programing: Typo in the name

2025-02-03T12:10:12Z

Chrskly moved page Zombiverter programing to Zombieverter programing: Typo in the name

← Older revision	Revision as of 12:10, 3 February 2025
(No difference)

Landsi: /* Software update */ added hint about external board power option during flashing

2025-02-02T11:59:46Z

Software update: added hint about external board power option during flashing

← Older revision		Revision as of 11:59, 2 February 2025
Line 54:		Line 54:


	The connections needed to use the ST-Link loader are shown below:[[File:0B35D4F9-BA64-46E7-A570-A0CE1D619D63.jpg\|none\|thumb]]		The connections needed to use the ST-Link loader are shown below (the red wire provides power to the chip. If the vcu is powered by it’s 12v pins instead, the red wire can be omitted):[[File:0B35D4F9-BA64-46E7-A570-A0CE1D619D63.jpg\|none\|thumb]]
	===Initializing an ISA Shunt===		===Initializing an ISA Shunt===
	Under Comms in the web interface, there is now an ISAMode option. By default its in "Normal" (Off on Rev 2). If you want to initialize a new shunt, connect it up, power on the shunt and vcu, select "Init" (On on Rev 2), hit save parameters to flash. Power cycle the vcu and shunt at same time (they should be on same 12v feed anyway). The shunt will initialize. Select ISAMode "normal" (Off on Rev 2), save to flash again and reboot again. The shunt should now be up and running. If the shunt doesn't initialise correctly, separate the shunt and VCU supplies and power cycle the VCU two or three seconds after the shunt power is cycled. This has fixed an initialise issue for a number of ISA shunts and possibly requires a VCU code fix that delays the initialising for a few seconds to allow the shunt to power up.		Under Comms in the web interface, there is now an ISAMode option. By default its in "Normal" (Off on Rev 2). If you want to initialize a new shunt, connect it up, power on the shunt and vcu, select "Init" (On on Rev 2), hit save parameters to flash. Power cycle the vcu and shunt at same time (they should be on same 12v feed anyway). The shunt will initialize. Select ISAMode "normal" (Off on Rev 2), save to flash again and reboot again. The shunt should now be up and running. If the shunt doesn't initialise correctly, separate the shunt and VCU supplies and power cycle the VCU two or three seconds after the shunt power is cycled. This has fixed an initialise issue for a number of ISA shunts and possibly requires a VCU code fix that delays the initialising for a few seconds to allow the shunt to power up.

Bratitude: Created page with ">Use this bootloader: https://github.com/jsphuebner/stm32-CANBootloader '''GD variant:''' ''Status as of November 20 2021'' ''Early boards fitted with the GigaDevices '''GD32F107''' aka "GD chip" require different firmware routines than '''STM32F107''' equipped boards. See this [https://openinverter.org/forum/viewtopic.php?p=33758#p33758 Zombieverter VCU Support Thread forum post]'' ''The GigaDevices `[https://www.gigadevice.com/products/microcontrollers/gd32/arm-c..."

2025-01-31T23:25:57Z

Created page with ">Use this bootloader: https://github.com/jsphuebner/stm32-CANBootloader '''GD variant:''' ''Status as of November 20 2021'' ''Early boards fitted with the GigaDevices '''GD32F107''' aka "GD chip" require different firmware routines than '''STM32F107''' equipped boards. See this [https://openinverter.org/forum/viewtopic.php?p=33758#p33758 Zombieverter VCU Support Thread forum post]'' ''The GigaDevices `[https://www.gigadevice.com/products/microcontrollers/gd32/arm-c..."

New page

>Use this bootloader: https://github.com/jsphuebner/stm32-CANBootloader

'''GD variant:'''

''Status as of November 20 2021''

''Early boards fitted with the GigaDevices '''GD32F107''' aka "GD chip" require different firmware routines than '''STM32F107''' equipped boards. See this [https://openinverter.org/forum/viewtopic.php?p=33758#p33758 Zombieverter VCU Support Thread forum post]''

''The GigaDevices `[https://www.gigadevice.com/products/microcontrollers/gd32/arm-cortex-m3/connectivity-line/gd32f107-series/ GD32F107] was chosen as an alternative to the ST equivalent due to microchip shortages during the COVID-19 pandemic. A specific branch of firmware code for the GD32F107 variant is found here: https://github.com/damienmaguire/Stm32-vcu/tree/GD_Zombie However development of this variant was abandoned shortly after it's release.''

''As of this writing , The [https://github.com/damienmaguire/Stm32-vcu/tree/GD_Zombie GD_Zombie] branch has fallen behind and substantially diverged from the primary code base. It has been suggested that work needs to be done to make the present firmware chip agnostic via detection routines. See this [https://openinverter.org/forum/viewtopic.php?p=34220#p34220 Zombieverter Development Thread forum post]. As of this writing that work has yet to be undertaken and remains to be organized and completed. And issue has be devoted to tracking this progress here: [https://github.com/damienmaguire/Stm32-vcu/issues/21 Issue #21]''

Here is a link to a post with a pre compiled bin and hex for the GD_Zombie created by Damien on the 23/11/21; [https://openinverter.org/forum/viewtopic.php?p=34264#p34264 ZombieVerter VCU Support - Page 9 - openinverter forum] This is based on the 16/6/21 code it is <u>'''not'''</u> an update. Ensure you rename the binaries to stm32_vcu.xxx to ensure no wifi issues.

''UPDATE November 23 2021''

''Updated information about the necessary edits to make to the STM32 based firmware have been posted in a [https://openinverter.org/forum/viewtopic.php?p=34264#p34264 forum post here.] In order to get the firmware to compile and run on the '''GD32F107''' you must make the following changes:''

''In the file "'''anain.cpp'''" @ line 68:''

''<code>68 - // adc_start_conversion_regular(ADC1); // Comment out for GD MCU</code>In the file'' ''"'''stm32_can.cpp'''" @ starting at line 305 modify as follows :''

''<code>305 - gpio_set_mode(GPIO_BANK_CAN2_RE_RX, GPIO_MODE_INPUT, GPIO_CNF_INPUT_PULL_UPDOWN, GPIO_CAN2_RE_RX);</code>''

''<code>306 - gpio_set(GPIO_BANK_CAN2_RE_RX, GPIO_CAN2_RE_RX);</code>''

''<code>307 - // Configure CAN pin: TX.-</code>''

''<code>308 - gpio_set_mode(GPIO_BANK_CAN2_RE_TX, GPIO_MODE_OUTPUT_50_MHZ, GPIO_CNF_OUTPUT_ALTFN_PUSHPULL, GPIO_CAN2_RE_TX);</code>''

If you properly clone the repository with '''git''' on the command line that looks like this;

<code>git clone --recurse-submodules git@github.com:damienmaguire/Stm32-vcu.git</code>

That recursively pulls in copies of '''''libopeninv''''', etc and tracks them... Hence your file-path should look like

<code>./Stm32-vcu/libopeninv/src/</code>

within the '''''libopeninv''''' src (source) directory you will find '''''anain.cpp''''' and '''''stm32_can.cpp'''''

Make the above changes to these files for the '''GigaDevices GD32F107'''.
==Software update==
As supplied, both the ESP8266 (the wifi plug-in board) and the STM32 (main MPU) are pre-loaded.

The "UART Update" field on the GUI can be given a '''stm32_vcu.bin''' file to update the firmware. Note that at this time, loading via Windows 10 is suspect and may lock you out of the board. Ubuntu works best.

'''Unless you have a specific reason not to, end users should use a released version from: https://github.com/damienmaguire/Stm32-vcu/releases'''.

By using the ST-Link V2 in-circuit loader, '''.hex''' files can be sent to the board to initialize a fresh STM32 MCU, or if it can't be loaded via the bootloader.

'''Unless you have a specific reason not to, end users should use a released version from: https://github.com/damienmaguire/Stm32-vcu/releases'''.

The connections needed to use the ST-Link loader are shown below:[[File:0B35D4F9-BA64-46E7-A570-A0CE1D619D63.jpg|none|thumb]]
===Initializing an ISA Shunt===
Under Comms in the web interface, there is now an ISAMode option. By default its in "Normal" (Off on Rev 2). If you want to initialize a new shunt, connect it up, power on the shunt and vcu, select "Init" (On on Rev 2), hit save parameters to flash. Power cycle the vcu and shunt at same time (they should be on same 12v feed anyway). The shunt will initialize. Select ISAMode "normal" (Off on Rev 2), save to flash again and reboot again. The shunt should now be up and running. If the shunt doesn't initialise correctly, separate the shunt and VCU supplies and power cycle the VCU two or three seconds after the shunt power is cycled. This has fixed an initialise issue for a number of ISA shunts and possibly requires a VCU code fix that delays the initialising for a few seconds to allow the shunt to power up.

Zombieverter programing - Revision history

Chrskly: Chrskly moved page Zombiverter programing to Zombieverter programing: Typo in the name

Landsi: /* Software update */ added hint about external board power option during flashing