piCore-2013-123.img doesn't boot?

[PiUser]

Hello all,

Cannot boot the subject image.   I usually use Win32DiskImager to write the image to the SD card.
The write worked as expected and I updated config.txt for my monitor and tried to boot .. nothing?

So then I booted to my Linux partition and used the dd command as described in the README.TXT
on the download page. This time I did not make any config.txt mods and still no boot.
I mean zero screen activity.

I'm not a beginner, have been using Raspian and OpenELEC since I got the Pi in August.  But this
has me stumped..  Any help, or even a direction to go to help myself would be much appreciated.

 -Jeff

[bmarkus]

There is typo in file name in subject.

Provide details on the issue, like how your SD card partitioned (output of fdisk or other partitioning program), type of monitor connection (analog, DVI, HDMI, TV or monitor), LED status (blinking LAN, HD), etc. Otherwise no one can help. No boot means nothing.

Zero screen activity doesn't mean 'no boot' for sure, it means only no screen activity, most likely an issue with the screen.

[mocore]

i geus it's was for case's like this that POST / beep codes  where created

seems they could be use full

in situations like this

[PiUser]

 Thanks for the quick response bmarkus.

 Yes, file name is actually piCore-20130123.img

 The SD card is not partitioned, this is just the first boot-to-a-command-line test.
 What I see is just the red LED (PWR), observed for more than 60 seconds.
 Monitor connection is HDMI -> DVI convert plug -> DVI input on a LCD monitor.
 ( This has worked for Raspian, OpenELEC, and even one time test with Xbian )

 With the first img I put on the card, I modified the config.txt with the following
 which I do with all Raspberry Pi images:

       hdmi_group=2
       hdmi_mode=32
       config_hdmi_boost=6

 Because without the config_hdmi_boost=6  my monitor shows so many green streaks
 ( not being driven hard enough ) it's difficult to read.

 However, the second image was downloaded and the MD5 hash checked (OK), and written to the
 SD card with the dd command shown in the README.TXT on the download page. There were no mods
 done to this image and still just the PWR LED, and no screen activity.

 I take your last point, but don't have any debug ideas without anything to start with.

 I have been working with my Pi since August, lots of fun and success ( I'm a retired software guy ),
 Just thought I'd ask here on the forum if there is anything different or unique about TinyCore
 on the Raspberry Pi I'm not getting.

  Thanks for your help!
  -Jeff   

[bmarkus]

For testing downloaded I downloaded referred image and copied to a 2G SD card with dd on Tiny Core Linux. It boots to prompt in 6 seconds. No any modification in boot, just as it is. I'm using an LCD monitor's DVI input driven from the Pi's HDMI output.

If it doesn't work, it must be an issue with the SD card itself or image is not copied properly. BTW, piCore is using the same boot as Raspbian. If Raspbian boots, piCore must do.

[PiUser]

The solution to my problem instantly raises another question.
 
OK, I had been trying this on a SanDisk 256 Meg SD card.  It is only a 40 Meg img,
and was written to the 256 meg card with no problems, but of course, will not boot.

THE SAME IMAGE written to a 32 Gig card works like a champ.

bmarkus, thanks for stating in your last post "must be a problem with the SD card...."
that made me try a different card.   Any thoughts on why the 256 Meg card won't fly?

Thanks for the quick responses,
 -Jeff

[PiUser]

  UPDATE:

 The conclusion to this "TinyCore won't boot" may have nothing to do with
 the TinyCore image.  Turns out that the Raspberry Pi has problems with many
 SD cards. You can see the cards that 'work' & 'don't work' list at this site:
   http://elinux.org/RPi_SD_cards

 I also found lots of talk about 'fake' SD Cards, cards that have been
 illegally modified to show a larger size than they actually are
 ( ie. 2GB card modified to present as a 16GB card ).  News to me.
 Anyway, I downloaded a free check-my-card program ( search for h2testw program ),
 and my 256 Meg card checked out genuine.
 
 Further seaching revealed that the bootcode.bin file ( part of the image for a
 Raspberry Pi ) is also suspect in booting certain cards.  There is a specific
 version of bootcode.bin file ( to aid this problem ) located here:
   https://github.com/raspberrypi/firmware/blob/234c19de7cbaaf4997671d61df20a05759066295/boot/bootcode.bin

  As referenced on this helpful page:
    http://elinux.org/R-Pi_Troubleshooting#SD_cards

 Replacing the bootcode.bin file in the TinyCore image with the special one (ref link above)
 allowed my 256 Meg card to boot right up!  6-7 seconds is right !!

 So is the bootcode.bin in the TinyCore image not 'the right' one ?  Or, does my ( genuine )
 SanDisk 256 Meg card need 'the fix' of a special bootcode.bin ?

 Don't know, but here are two items to chase down if you have a card that won't boot your Pi.

  -Jeff

[bmarkus]

Jeff

thanks for the feedback. bootcode.bin is one used by Raspbian, or at least was used a month ago, will check. Don't know your special version is compatible with other SD cards supported by current version.

Bela

[ian57]

Seems that SD class 4 card are not supported by the raspi

[bmarkus]

I have two Raspberrys, Model "B", one is a year old, the other is cca. 4 month and using a 8G Class 10, 8G Class 4 and 4G Class 4 cards. Older RPi boots all three, newer doesn't boots the 4G card.

[bmarkus]

Further notice, that it is not piCore specific. On the 4G card where piCore doesn't boot the same with current Raspbian too.

[ian57]

My card is a SanDisk 8Gb micro SD HC  with a small 4 into a circle. The card works well, but dos not boot in my raspi model B. I use it with a SD Adapter. Perhaps it comes from the specific one. Will try with another one

[bmarkus]

I have a bad experience with micro card adapters in general in RPi due to low quality socket in RPi. Those adapters I have do not fit properly, they have different mechanical parameters than normal cards.

[ian57]

I tried many adapter (at least 3) but always the same problem... does not boot. The adapter is fonctionnal, because another microsd is booting using it (not the same brand and class)

Thanks