Hi !
I have a Raspberry PI 3B+, downloaded the latest image today and burned it with baleaEtcher to an 64 and 32GB SD Card.
The Pi is not showing anything bejond the colored screen?
Any help is very welcome.
Thanks a lot,
This site is now in read-only archive mode. Please move all discussion, and create a new account at the new Victron Community site.
Hi !
I have a Raspberry PI 3B+, downloaded the latest image today and burned it with baleaEtcher to an 64 and 32GB SD Card.
The Pi is not showing anything bejond the colored screen?
Any help is very welcome.
Thanks a lot,
Hi,
please try again using Win32DiskImager.
https://raspberry-projects.com/pi/pi-operating-systems/win32diskimager
This is a proven way to write RPI Images to SD cards.
Regards,
Markus
Hi @Markus,
thank you very much for your quick reply.
Unfortunately there is no windows available here.
Any other Image I tested now (jessie or octopi for ex.) are working well.
So I am not sure the Problem is the etcher software?
Maybe any other idea ?
Did you try writing an older Venus Image to the SD card? Does that work?
@digitalxxl which file exactly did you write to the card?
I tried
venus-image-raspberrypi2.rpi-sdimg.zip |
2019-12-20 21:07 | 95M |
as well as v2.30
Every image i tried showed the same behaviour.. stopped at colored pi screen.
Thanks for your support and best regards
You did unzip it before? ;o)
I just tried using dd on macOS and that works with no problem.
I would suggest, using a different method of writing the image to the SD card.
Regards,
Markus
HI !
Pretty weird.. i tried both - burning the zip (which is automatically extracted to 1.9GB) and tried to burn the unzipped sdimg. Every time the same result, pi not booting..
OSX Version is High sierra and Catalina (tried on both machines),
Thanks for your support and best regards,
Stephan
I just tried dd..
sudo dd if=~/Downloads/venus-image-raspberrypi2-20191220165723-v2.42.rootfs.rpi-sdimg of=/dev/rdisk4 bs=1m
same result.. pi not booting.. colored screen
Strange, did you try yet another SD card? I am running out of ideas. This should work...
Same here.. I tried an 32GB SanDisk as well as the 64GB SanDisk..
after dd the card looks like:
/dev/disk4 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: FDisk_partition_scheme *63.9 GB disk4
1: Windows_FAT_32 NO NAME 41.9 MB disk4s1
2: Linux 524.3 MB disk4s2
3: Linux 524.3 MB disk4s3
4: Linux 805.3 MB disk4s4
Good Morning !
I have now switched to the pi4 which has done other things in my home before and burned the image for the pi4 (which i found here: https://community.victronenergy.com/questions/25666/venus-on-raspberry-pi-4.html) to the 32GB SD-Card with Etcher and everything starts up perfectly and works like expected.
Why my pi3B+ does not start up is totally unclear at the moment. Nevertheless I have ordered another 3B+ to rule out any hardware issues.
I will report back once the new pi has arrived. ;)
Cheers and regards,
Hi @digitalxxl,
did you manage to make your pi 3B+ work? I've had a similar problem, with the pi booting the first time but the console shows nothing and sometimes after around 5 to 8 minutes it restarts and stays on the black screen of the console with nothing on it.
Sometimes it just shows the colored screen of the pi and won't pass from it.
I burned the image of the Venus OS v.2.70~15 with BalenaEtcher on macOS.
I tested the pi and the same SD card with Venus OS v2.66 and it worked without issues, so I know is the v.2.70 that's just not working here.
Cheers,
Hi !
No, that pi I had was not able to boot the sd image (RS Electronics).
I bought a new pi3B+ from another company and it worked perfectly.
The two look quite different even they both are telling they are pi3b+.
The one that is not willing to boot from the sd image also has other problems in other environments. My guess is that it might be buggy.
Hope that helps..
Additional resources still need to be added for this topic
Raspberry Pi running Victron’s Venus firmware - Blog Post
Venus OS Large image: Signal K and Node-RED - Install
raspberrypi install venus image
15 People are following this question.