Tiny Core Base > Raspberry Pi

Tiny Core not booting on some pi3a+

<< < (2/3) > >>

gadget42:
are you able to determine if the failing 20 units all came from one "batch" from your purchases via farnell?

i wonder if we can determine a serial number range for the failing units so that it might be possible for others to determine if they have these failing units as well?

Rich:
Hi SteveatXitek
I seem to remember reading somewhere that the boot loader
on these devices can be updated. Are those 20 boards using
the same boot loader as the other 280?

gadget42:
according to this post:

https://forums.raspberrypi.com/viewtopic.php?t=352778#p2114933


--- Quote ---If it DOES boot when using bootcode.bin with the timeout file, then you may be able to get it working by setting another OTP bit that increases the wait time for the USB drive to become ready from the default 2 seconds to 5 seconds (this is a permanent change). To enable the additional wait time for USB drives, add "program_usb_boot_timeout=1" to config.txt on a Raspbian SD card and boot it once in the system. After that the system will wait up to 5 seconds for USB drives to become ready.
--- End quote ---

what if the ones that don't work properly with TCL maybe have this 2 second timeout and that isn't long enough for TCL?

(please read the whole post and probably the whole thread for the entire content/context)

Paul_123:
1) The timeout only applies to drives connected to the USB port.  It does not affect /dev/mmcblk0
2) While you can manipulate the OTP, there is no upgradeable bootloader on the pi3* boards.  It is all files on the boot partition.
3) If you connect HDMI and sdcard image on the built in SD card.  You should at a very minimum see the rainbow square screen from the firmware.   If you do not see this, then you have some other hardware problem.


--- Quote ---all using the same iso for flashing the cards
--- End quote ---

We do not supply iso's, they are img files.   Where specifically have you downloaded from?

SteveatXitek:
Hi All , Thanks for the replies, However, I isolated the issue as being an early version of BusyBox bootloader, later versions work fine. We were using the Busy box that came with the V10.1 Tiny core, and I noticed that the version of Busybox was updated for V11.1 Tinycore , this later combination worked.

Navigation

[0] Message Index

[#] Next page

[*] Previous page