No, not until the non-beta version.jhasler wrote:Does that image include your pullup fix?
If dom's suggestion doesn't fix it try this bootcode.bin file: https://github.com/raspberrypi/firmware ... otcode.bin.Any other suggestions on how I can tell it its a bad unit?
The red LED labeled PWR comes on if power is ok. The green LED labeled OK flashes while the "firmware" is executing and while the OS is loading. If it never flashes nothing was read from the SD card.Should I get some flashing indicators at boot time?
I just received my Ras Pi from element14 and it didn't boot off the two Sandisk SD cards I had prepared (both with the beta image of debian wheezy).Paul_L wrote:The download image does not include the latest firmware. I have used it but to make it work on all cards I replaced the firmware files with newer firmware files from github.
It did it with "wheezy" img.For anyone that wants to try it out, boot the RPI off wheezy and let it get stuck where the PWR and OK LED are both solidly on. Turn the PI over and place your finger over the left one-third of the pins. Move your finger until the LEDs change state. Not really a science nor an art.
While it is true that bad power is often the cause of trouble, too many cards that work fine in other devices were failing for card problems to be due just to bad cards. There was a bug in bootcode.bin such that the chip's internal pullup resistors were not being properly enabled. The bug is (we hope) fixed in the new bootcode.bin available at https://github.com/raspberrypi/firmware ... otcode.bin. Please try it with your non-working cards.It seems that a fair amount of the "Red LED on Faint Green LED" problems relates to either a too weak power source or a bad SD card.
Exactly what symptoms are you seeing?I tried the new bootcode with all the distros and multiple power supplies that I know are good (5V +/- 1% and >1A) and shelling out $50 on new SD cards of various types from the known good list. I have just raised an RMA with element14.
Can you:FalseIdle wrote: Now back to that magic thing. I really feel the need to understand this. My SD reader has been used to transfer GB's of photos from SD cards and to copy data to and from Android devices and not once has there been any noticeable corruptions so I cant see it being that. I am left with 2 thoughts on the matter . one both the raspbmc installer and win32imager do not control my specific SD reader correctly and the data is indeed wrong on the card. I will investigate this later by trying dd in linux on my laptop and I will also read back the image programmed using win32imager on mine on the other laptop and diff against gold.
Wife using the laptop that has the good SD reader (Had to be the wife's that worked and not mine) but when its free I shall do as you asked and report back.dom wrote: Can you:
use win32imager on the bad sdcard reader to write the card. Then use it on the good sdcard reader to read the image off the sdcard.
use win32imager on the good sdcard reader to write the card. Then use it on the good sdcard reader to read the image off the sdcard.
You now have two images that should be the same (and the same as the downloaded image). Compare them. I'm guess the one written with bad sdcard reader will look different.
Be interesting to see if it has occasional incorrect bytes, or it is truncated, or there's nothing recognisable there at all.
I had the same problem, but not with the same SD card. I fixed it by using another SD card and another monitor. You might want to check if it works with no or a different monitor.Semy wrote:I've got a solid red LED and a green LED that, on start up, will occasionally flicker intermittently but stop after a few seconds. Depending on which distro I have used there will sometimes be a pinprick of light in the green LED.
I've got a "SanDisk Secure Digital High Capacity Card Extreme Video HD 16GB Class 10" bought from a seller on Amazon (http://www.amazon.co.uk/gp/product/B003 ... 02_s00_i00). I'm fairly sure it isn't fake. Unfortunately I don't have another SD card.
So far I have tested:dom wrote:I'd start with Wheezy image and update bootcode.bin and start.elf.psypher246 wrote:Just tried writing the debian image with DD and then downloaded the new bootcode.bin and replaced it on the SD card but still not booting.
Otherwise, trying a different sdcard could work.
Sorry I forgot to mention my symptoms:Stefan_C wrote:After placing the order mid March and waiting patiently until it arrived last week, I am starting to doubt if this is going to work. I tried the new bootcode with all the distros and multiple power supplies that I know are good (5V +/- 1% and >1A) and shelling out $50 on new SD cards of various types from the known good list. I have just raised an RMA with element14. Let's hope I can get a new board soon, and that it works. Very dissappointed enthusiast...
Is there anyone else with a Pi you could swap bits with?
It may be the Pi is faulty. Possibly a problem with the sdcard connector.
Sorry for my english.jhasler wrote:Do cards written with that card reader work well in other devices?