WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Is it always 1 version for B+ and 1 version for B2 ??  (Read 1374 times)

Offline bkm

  • Jr. Member
  • **
  • Posts: 72
Is it always 1 version for B+ and 1 version for B2 ??
« on: March 31, 2015, 07:58:50 AM »
Greetings everyone,

I am nearly finished with my redevelopment project to move my application from and old x86 based on T/C v.3.x to the Raspberry Pi with P/C v.6.0.

However, it seems as fast as I am working, the supply of RPi hardware is changing even faster!!! :o

I started with the RPi Model B about 2 months ago, and now that I am nearly finished, the Model B has become scarce, and where it is available, it has jumped in price to nearly $45US. It looks as if it will go away completely soon. While everything seems to be compatible with the newer Model B+ (which is still priced reasonably) it has forced me to again redesign my enclosure to fit the different layout of the B+ with extra USB ports and different locations for everything else! So now more delays for the newer enclosure. I deploy these devices into an industrial environment and need specialized enclosures.

If that weren't enough trouble, the newest Model B2 was released during the time I was in development. It also has the same footprint as the Model B+ but my current PiCore v.6.0 will not boot on the newest B2 model (probably due to the new processor).

I want to be able to release a package that will be supportable for more than just a few months, but I am very concerned that the Model B+ may also go the way of the older Model B and I will be stuck with the newest B2 as replacement hardware.

Ultimately, I am wondering if there will ALWAYS be 2 separate versions of the PiCore for the B+ and B2 hardware or if they will ever become a single package? I am just very frustrated by trying to develop to a moving target.

I know it seems like it shouldn't be that bad, but when your application is bundled with the operating system and is designed to be automatically downloaded and installed by folks with no knowledge of software (like my factory floor workers). It needs to be as simple as "click here to install". This presents many problems to have 2 completely different versions for hardware that (to the end user) looks identical.

Pardon my rant... I guess the frustration got the better of me.

I guess the real question here is going to be... "Can a version of PiCore me made that will boot on the newest model B2 and still be downward compatible to also boot on the model B+?" (or the other way around  to boot an the B+ and be to be upward compatible to the B2)

If not, then I might need to abandon the RPi and look for some other stable hardware. It would be a shame to abandon this, but as of now I cannot count on my package to be usable into the future with this many incompatibilities.

Any advice? anyone?

Thanks,

BKM

Offline bmarkus

  • Administrator
  • Hero Member
  • *****
  • Posts: 7035
    • My Community Forum
Re: Is it always 1 version for B+ and 1 version for B2 ??
« Reply #1 on: March 31, 2015, 08:52:49 AM »
Hi,

I see your point. It is possible to create a common image for armv6 and armv7 similar to Raspbian. You need two different kernel for the different CPU-s. Also you need a combined initrd file which contains kernel modules for both. It is just a simple repacking. In config.txt you can have conditional parts so maybe you can load the two original initrd files without combining but I have never tried it. Shortly yes, it is possible to have one image for two.

Why is it not done by default? It is against Tiny Core basics to add anything to the image which is not used. One can argue that it is not important, SD cards have large capacity, 15-20 Mbyte is not important. If there will be a strong demand we can review the case.

If you need help to make the version you need PM me.
Béla
Ham Radio callsign: HA5DI

"Amateur Radio: The First Technology-Based Social Network."