|
You posted this in two different sections. Please try not to double post. Since this is probably a more appropriate place for your question I hope the moderator will delete the other post, so I will reproduce here the relevant part of my reply:
"2 - my guess is that if you have a solid red LED on, your board is booting, you just don't get to see it on your monitor. My first option would be to connect the pi to a console and see what's happening, but in case you don't have the hardware for that (simple and cheap cable) you can always try to reach your pi from another networked device. For that there are many alternatives and possibilities. The images your tried probably come preconfigured to use DHCP, so all you need is a DHCP server on your network and then scan the network for your pi. In my case, I do not use DHCP on my private network, so I set static IPs to my devices and I already know which is which. Probably there is simply something wrong with the display, you either have a monitor that does not support the resolution set in script.bin (edit script.fex), or there is something wrong with the HDMI-VGA adapter you are using. Since you state that you have tried Android too, I assume it was with the exact same setup, and if you get to see an image displayed with Android (before it freezes), then your HDMI-VGA adapter is probably not the issue. Thus, the most probable cause is the resolution set in script.bin. Most images come configured to run at 720p (media/boot/script.bin), check if your monitor supports 720p, or better, check all resolutions supported by your monitor and see what suits you best. Good luck!"
|
|