Tiny Core Linux
Tiny Core Base => Raspberry Pi => Topic started by: vinceASPECT on July 24, 2022, 08:36:27 AM
-
Hello
is there a "piCORE 64 bit" version of TCL operating system available for arm cpu's......?
i was thinking that the regular "piCORE" for arm cpu's is compiled to armv6 and 32 bit?
If so, Where do we get it please?
what arm architecture is it compiled to please? (armv8?)
thx
C
-
Hi vinceASPECT
I've split your post into its own topic.
32 bit piCore for ARMv6, ARMv7, and ARMv7l can be found here:
http://tinycorelinux.net/13.x/armv6/releases/RPi/
http://tinycorelinux.net/13.x/armv7/releases/RPi/
http://tinycorelinux.net/13.x/armv7l/releases/RPi/
64 bit piCore for ARMv8 can be found here:
http://tinycorelinux.net/13.x/aarch64/releases/RPi/
-
Oh Rich,
Many many thanks.
Ridiculous that i could not shift up levels
of the "releases File structure" and see that those distro's for arm exist there.
Well, my Linux skills are essentially non existent.
Also, i did not actually "know" the distro's existed.
It is good to see Arm7 somehow.
many thanks Rich,
C
-
I want to write an article for wikipedia about architectures and hardware that TC support nowadays.
The major quastion is "Do you still support i486, i586? Can you give me a list of all ARM devices that works with TC."
-
only raspberry pi is supported by piCore
The packages would run on nearly any armv6/7/8 processor, however the boot loader and kernel modules would all need to be remastered for a specific board.
piCore14/piCore64 would require a >5.15.x kernel
-
The Core toolchain is compiled for i486.
-
@neonix, here is a link to a forum thread where we discovered/investigated what TC did/didn't run on(with respect to 486/586/686).
https://forum.tinycorelinux.net/index.php/topic,25098.0.html
sharing is caring
-
heLLO fORUM,
"pICORE " computer operating system.....IS tINYCORE FOR rASPEBRRY PI computers
So those computers use several ARM processors types (cores)........................so the compilation type for "picore" will be some version of ARM processor
"Armv6" version of Picore computer Operating system.........for example
Thx.
C
-
What about Orange Pi, Banana Pi, Mango Pi, and other clones?
There is also dCore Arm V7hf section with Allwinner-A10, GK802 and Allwinner-A20?
What is armv7hf?
BTW. Raspberry Pi Pico is not Linux compatible.
-
Every arm board has different bootLoader requirements. This requires someone to port the OS.
Nobody has ever stepped up to do it.
-
Every arm board has different bootLoader requirements. This requires someone to port the OS.
Nobody has ever stepped up to do it.
I have piCore 32 running on Odroid U3 (Exynos 4412), which is armv7hf.
As you indicate, it is needed:
- change the bootloader, in this case uboot
- and the kernel, in this case 5.4 upstream
piCore32 runs quite well on such device
-
BTW. Raspberry Pi Pico is not Linux compatible.
/ot
read the above and remembered this topic : 'Linux on an 8-bit micro?' - https://forum.tinycorelinux.net/index.php/topic,24898.msg158432.html#msg158432 ::) :P 8)
that is all.
;]
-
didn't want to start another new thread about raspberry pi but thought others should/would-like to be made aware:
"clang now makes binaries an original Pi B+ can't run" - Rachel Kroll
https://rachelbythebay.com/w/2023/11/30/armv6/
-
"clang now makes binaries an original Pi B+ can't run" - Rachel Kroll
LMAO!
If it ain't broke... just give it a minute!
-
Hi gadget42
Big deal. Just like gcc, you can specify the target:
clang++ --target=armv6-unknown-linux-gnueabihf -Wall -o t t.cc
If you add some context to your posts, they won't read
like the front page of a supermarket tabloid.
-
the whole world is a supermarket tabloid - unknown
-
It’s obvious that person has no idea what they are doing. It’s always necessary to need that stuff when cross compiling.
-
It’s obvious that person has no idea what they are doing. It’s always necessary to need that stuff when cross compiling.
to clarify, she said "So, I went and did a build on the B+ natively. It also broke."
are you saying that that is cross-compiling?
-
If the compiler was not built on armv6, then it’s always a problem.
-
Perhaps I was being too sensational in my response too. But to elaborate. I doubt there is a single distribution keeping separate repositories for every processor. Even piCore, where we have an armv6, armv7, armv7l the code in those repositories is not natively compiled. Also in piCore's case gcc is built on an armv7l processor gcc is configured by the maintainer to produce code compiled for armv6, and for the most part will do that for the casual user who builds code like
gcc -o foo foo.c
It is true that Clang/LLVM is much more restrictive in the code that it produces by default. But it has been that way, and you should always specify the desired target. If you download some source for a programs distribution, almost all of them use some sort of configure system (autoconf/libtool, meson, etc) The job of the configure system is to determine the host compiler and the target. Which then tells gcc/clang specifically what to do.
-
reminded of Bruce Schneier's 2006 post and referencing David A. Wheeler regarding trusting-trust and compiling-compilers
for reader convenience:
Mr. Schneier:
https://www.schneier.com/blog/archives/2006/01/countering_trus.html
Mr. Wheeler:
https://dwheeler.com/trusting-trust/
thought-provoking nevertheless
@Paul_123
as always, thank you and kudos for your considerations and thoughts!
20231201-0914am-cdt-usa-modified: originally forgot to add @Paul_123 comment
-
Hi vinceASPECT
I've split your post into its own topic.
32 bit piCore for ARMv6, ARMv7, and ARMv7l can be found here:
http://tinycorelinux.net/13.x/armv6/releases/RPi/
http://tinycorelinux.net/13.x/armv7/releases/RPi/
http://tinycorelinux.net/13.x/armv7l/releases/RPi/
64 bit piCore for ARMv8 can be found here:
http://tinycorelinux.net/13.x/aarch64/releases/RPi/
These ports are combatible only with Rasberry family-SOC I think? Whole ARM/SOC field (and armel) is "badly corrupted" for countless number of SOC's and driver mess (as Linus too has commented). Device Tree Blob -mechanism should help, but ports will probably more binded for SOC family rather than ARM-version, for ever....
-
Yes, because we only have a Raspi bootLoader and kernel. If you have those 2 things for a different arm board, the rest of the distribution would work.
The issue is only Raspberry pi properly supports their hardware. Everyone else waves a shiny board at you to sucker you out of your $$$.