0

"UPDI Initialization falied" when trying to flash the power controller

Felix

June 27, 2021 12:10

None

Follow

Hello,

maybe somebody has some advice:

I wanted to program the power controller, but I didn't get too far :-(

My programming efforts are resulting in the message:

# pyupdi -c /dev/ttyAMA0 -d mega808 -f firmware.hex
Traceback (most recent call last):
File "/bin/pyupdi", line 11, in <module>
load_entry_point('pyupdi==0.0.0', 'console_scripts', 'pyupdi')()
File "/usr/lib/python3.9/site-packages/updi/pyupdi.py", line 95, in _main
File "/usr/lib/python3.9/site-packages/updi/nvm.py", line 17, in __init__
File "/usr/lib/python3.9/site-packages/updi/application.py", line 17, in __init__
File "/usr/lib/python3.9/site-packages/updi/link.py", line 32, in __init__
Exception: UPDI initialisation failed

 

I did start the tool

/opt/hifiberry/bin/enable-updi

in advance, though, and I also checked that there is the line

dtoverlay=disable-bt

in the config file, but for some reason the systems seems to ignore that (?)

I was logged in as "root" all the time.

Thanks in advance for any help!

 

 

• Facebook
• Twitter
• LinkedIn

22 comments

• 0
  
  HiFiBerry team June 28, 2021 06:19

  Did you reboot after enabling updi? If you did, there might be a hardware issue. Check that the cable is plugged in correctly.

• 0
  
  Chris Hasty July 24, 2021 16:15

  I'm having the same issue on my Pi4. Works great on the Pi3 and I'm using it with no issue. However when I moved the controller from the Pi3 to the Pi4 it will not recognize it or allow me to continue.

• 0
  
  Benedikt Rombach January 08, 2022 19:35

  Hi Folks,

  I've got almost the same problem here - using a Pi3, an Amp2 1.1 and a PowerController v1.1 11/20:

  I did follow the flashing instructions word by word, but when checking the communication I get the same error as above:

  # pyupdi -c /dev/ttyAMA0 -d mega808 -fr
  Traceback (most recent call last):
  File "/bin/pyupdi", line 11, in <module>
  load_entry_point('pyupdi==0.0.0', 'console_scripts', 'pyupdi')()
  File "/usr/lib/python3.9/site-packages/updi/pyupdi.py", line 95, in _main
  File "/usr/lib/python3.9/site-packages/updi/nvm.py", line 17, in __init__
  File "/usr/lib/python3.9/site-packages/updi/application.py", line 17, in __init__
  File "/usr/lib/python3.9/site-packages/updi/link.py", line 32, in __init__
  Exception: UPDI initialisation failed

  Anything else I can try? Or are there additional infos I can provide to narrow down the possible error cause?

• 0
  
  HiFiBerry team January 10, 2022 10:16

  Can you try an older HBOS release (e.g. the May release). We have sen problems in some newer installations.

• 0
  
  Benedikt Rombach January 29, 2022 12:58

  Thanks for the answer, that did work out for me!

• 0
  
  Thomas Schläppi March 04, 2022 18:13

  Dear HifiBerry team,

  Can you try an older HBOS release (e.g. the May release). We have sen problems in some newer installations.

  I' am stuck in the same situation - sadly, a rollback to the may version isn't possible anymore using the ui. I can download the old release from github, but it scares me to death to use a version which is nearly one year old.

  There is in fact an issue in on the UPDI Github page - but it does not seem to help (they say, that there is a communication problem, but I think, there is a software problem).

   

  What do you think, ist it the OS, python, or other dependency upgrade which causes the failure, or ist it maybe an upgrade of the UPDI software between the may release and the current one?

  Thanks,

  Thomas

   

• 0
  
  David Stiles March 16, 2022 05:18

  Hi,

  I am also stuck at this stage:

  File "/usr/lib/python3.9/site-package/updi/link.py", line 32, in __init__ 
  Exception: UPDI initialisation failed

  I tried it with May release and didn't get any further.

  Although in diagnostic information, power controller shows '0x00/0x01' instead of previously 'not detected'.  Any work around yet?

• 0
  
  HiFiBerry team March 16, 2022 06:09

  Are you using a Pi4?

• 0
  
  David Stiles March 16, 2022 06:23

  I am using Pi3B+

   

• 0
  
  HiFiBerry team March 16, 2022 09:35

  That's trange as the controller seems to work in this case. How did you connect it?

• 0
  
  David Stiles March 16, 2022 10:19

  Initially Power Controller was connected to the extra header on a Beocreate board.  When that didn't work, I tried it directly to the Pi with nothing else connected.  I have the jumper in so it is powered from Beocreate in the first instance and the Pi in the second attempt.   Red wire toward the SD card end of Pi as per picture.  

   

• 0
  
  HiFiBerry team March 16, 2022 10:21

  You can't flash the firmware via the Beocreate. You need to remove the Beocreate and directly connect the power controller to the Pi using the provided flat ribbon cable.

• 0
  
  David Stiles March 16, 2022 10:23

  With Beocreate attempt I used the current release.  When connected directly to Pi, I used the May release.   I have not tried it attached to Beocreate using the May release.  Would this be worth a try?

• 0
  
  David Stiles March 16, 2022 10:50

  So, I have tried flashing direct Pi to power controller using May release.  

  That's when I got the error message:  

  File "/usr/lib/python3.9/site-package/updi/link.py", line 32, in __init__ 
  Exception: UPDI initialisation failed

• 0
  
  HiFiBerry team March 16, 2022 16:55

  It might be a problem with either the Pi or the power controller. The fact that the system displays version 0x00/0x01 shows that the controller itself is powered and running. There might still be a problem with the programming interface, but there's also a good chance that the Pi is causing the trouble as the firmware has been flashed onto this chip before. Do you have another Pi to test?

• 0
  
  David Stiles March 18, 2022 09:38

  After a few attempts, I believe it has now flashed successfully. What is correct orientation of GPIO plug connection to Beocreate board?

• 0
  
  HiFiBerry team March 18, 2022 09:44

  There is no "correct orientation". The power controller can't be directly connected to the Beocreate. The Beocreate's GPIO header is not compatible with the power controller. The necessary signals are not available on the Beocreate extension header. You would have to solder cables directly onto the Pi to make this work.

• 0
  
  David Stiles March 18, 2022 09:48

  Thank you, that's good information.

• 0
  
  David Stiles March 21, 2022 09:17

  I was mistaken in previous message above.  I still have not been able to flash the power controller.  I am still stuck at:

  File "/usr/lib/python3.9/site-packages/updi/link.py", line 32, in __init__ 
  Exception: UPDI initialisation failed

  I have attempted it again with a brand new Pi3B+   Power controller shows address 0x00/0x01 in diagnostic information.   Could it be faulty power controller?

• 0
  
  HiFiBerry team March 21, 2022 19:46

  Could be, could also be a problem with the Pi or the software. Unfortunately I can't say more. You can send us the PC for a check. Please contact us at support@hifiberry.com if you want to do this.

• 0
  
  David Stiles April 08, 2022 04:58

  Rather than return old one, I ordered a new power controller from Hifiberry.  Connected it directly to a new Pi3B+.  Created fresh install of latest HifiberryOS for Pi3 on a micro SD.  Ran through steps exactly as per instructions on github.  

  Still get: UPDI initialisation failed

  What could be I be doing wrong?

  Thanks

• 0
  
  David Stiles April 08, 2022 05:33

  OK, just went through the process again with May 2021 release and have been able to proceed to next step.