Oh thanks,
I was wondering if there is any tutorial how to use the updi ?
I’ve never done that before…
And sit here with the 4.50 modules without any software on it.
Look for the video of the shunt.
And read the github.
I also didnt know that the system has changed.
I changed to the new controller because it is easy to program the modules.
When this does not work anymore there is no advantage on the new controller for me.
For me it was not difficult to get 841. I ordered them via Alibaba in china.
Took only a few days.
And I have only 1.9f boards.
Best Regards
I used a generic USB UART TTL adapter using the diagram shown here. I use pymcuprog to flash the shunt and would use similar for these modules.
The 2x3 IDC header on the ESP32 controller PCB is only compatible with the ATTiny841 modules.
1 Like
Maybe.
But this is again a system for people who know how.
The advantage of the new controller with AVM programmer was:
- you need no knowledge about external programmer and programs
- no knowledge how to use the programs
- no knowledge about any coding and syntax.
Only sticking the modules and tell the BMS which firmware.
Work for noobs.
Now you have to use a programmer and some programs to do.
Some more tasks which can be difficult if you have no experience.
I agree, but unfortunately there is no UPDI programmer that will run on the ESP32 (I tried one and it failed miserably). Additionally the resistor is not present on the controller PCB to combine RX/TX.
The only reason Stuart changed this is because the ATTINY841 are becoming very hard to locate and the price has increased, the new ATTINY1614 is much cheaper and more readly avalaible, I am sure in due course someone will release a video on how to flash it.
1 Like
I say again. I ordered the 841 in China and got it in a week.
Maybe the 16xx is an Euro cheaper.
But it is very uncomfortable to flash.
And the new Controller becomes partly obsolete.
for now. It should be feasible to have an adapter PCB of sorts that adds the missing resistor and a bit of time to sort out issues with the UPDI protocol.
I’m very excited…
I have the same problem, i dont know why. The controller program the module before, now always show the error code like you have on the picture. I’ve checked the pins, they’re in right orientation
Same problem?
You try to program 4.5 modules with attiny 1614 with the new BMS controller?
I did program the attiny1624 with an arduino uno. Therefore the Arduno himself must be programmed with the jtag2updi: GitHub - ElTangas/jtag2updi: UPDI programmer software for Arduino (targets Tiny AVR-0/1/2, Mega AVR-0 and AVR-DA/DB MCUs)
after doing the job with the Arduino I used the AVRDUDESS:
Thank you all!
Thank God I have some crazy order failures here…
Flashed the old board successfully…
Does the tx and Rx cables need the correct polarity?
Thx
Yes. They need. But when you put in the cable in the wrong direction: nothing happens.
You only wont have success to flash.
I ment the Rx and tx cables for communication…
Does the just plugs need to be in a specific polarity and work only when a battery is plugged in ?
Polarity of the cable: from left to right.
If you turn the cable 180° it won´t work and it will not harm your cell board.
You are not allowed to have voltage on the cell board.
Will not work and will harm the controller and cell board.
Finish:
- no voltage on the cell board allowed
- plug in the right direction
Thats all.
Hello, what is must setting fuses on attiny 1624 chip? arduino ide default setting is:
--fuses 0:0b00000000 2:0x02 6:0x04 7:0x00 8:0x00
It is correct values?
Looks OK to me:
1614
C:\Users\mgx\AppData\Local\Arduino15\packages\megaTinyCore\tools\python3\3.7.2-post1/python3 -u C:\Users\mgx\AppData\Local\Arduino15\packages\megaTinyCore\hardware\megaavr\2.6.5/tools/prog.py -t uart -u COM6 -b 460800 -d attiny1614 --fuses 0:0b00000000 2:0x02 6:0x04 7:0x00 8:0x00 -fmodule_fw_V450_5K_ATtiny1624_450_e0_h0_l0.hex -a write -v
3224
C:\Users\mgx\AppData\Local\Arduino15\packages\megaTinyCore\tools\python3\3.7.2-post1/python3 -u C:\Users\mgx\AppData\Local\Arduino15\packages\megaTinyCore\hardware\megaavr\2.6.5/tools/prog.py -t uart -u COM6 -b 230400 -d attiny3224 --fuses 0:0b00000000 2:0x02 6:0x04 7:0x00 8:0x00 -fmodule_fw_V450_5K_ATtiny1624_450_e0_h0_l0.hex -a write -v
Hi all,
I have the same issue, " Failed, error code 3 FAILED_ENTER_PROG_MODE" but with V4.4 controller and modules. Below is a detailed description:
Controller V4.4 – ESP32 WROOM 32 D DevKitC
Modules V4.4
2.8” SPI TFT screen
Using
- NodeMCU for flashing the ESP 32
- Silicon Labs CP210x USB to UART bridge driver for the ESP32 microcontroller
- PuTTY terminal emulator for setting the Wi-Fi configuration
Issues:
- Programming the modules.
14 modules were prepared for loading the firmware, version 17-Mar-2023. Later, 2 previous versions were tried, but the issue was not resolved.
Out of 14 modules, only 6 were successfully programmed.
Thinking that possibly the AVR ISP wires between the controller and the module were loose, I double checked the connections and started again to load the program on the 8 modules that failed initially. After many attempts, 5 more were successfully programmed. It proved that the wires connection was good, so the fault is somewhere else.
The remaining 3 could not be programmed no matter how many times I tried. The same error kept showing: Failed, error code 3 FAILED_ENTER_PROG_MODE
When I click “Program Device” , the blue LED on the module lights up faintly.
Also, on 2 occasions error 2 COMMIT, appeared.
- I connected 2 modules to the controller, but there was no communication. The message on the red bar of the web interface was “Waiting for the modules”. On the “Modules” tab, the controller detected 2 modules, but no voltage was shown and no graph on the “Home” tab.
On the controller board I measured the voltage at RX = 3.3 V and TX = 0 V. Is this what it should be?
Module 1 when connected to TX @ control board stopped flashing the blue LED
Module 2 continued flashing when connected to RX @ control board.
I checked with the multi-meter for short circuit between + & - @ modules power connections and there is no resistance, so this part was fine.
To summarize, the AVR ISP wires connection shouldn’t be the fault. I have 4 ESP32s and tried them all. 3 of them were programmed, one did not work, although all 4 are new, purchased for this project. All 3 behaved the same. Could it be the controller board? It was ordered from JLCPCB, I only soldered the pins and the connectors. I can prepare another one and test it.
Your opinion would be greatly appreciated.
Cheers,
Paul
I programmed 80 Modules and I had to start the programming twice for about 7 modules. One I could not program. Reason was a bad solder joint at the ATINI, so check your soldering.