by shaman2014 » Mon Feb 19, 2018 6:37 pm
I have been able to detemine some additional information:
First note:
1. The problem is due to the fact that Newark was forced to change the RAM and
Flash chips (end of lifed) and the new chips require some changes in the
firmware to support them (which they have provided). But it also appears
that the kernel must be changed to support the new chips.
2. I am using a CM not a CM3 (cannot upgrade due to power constraints).
3. The modules in question start with the serial number ND****.
4. I am using the rpi image (not the rpi2 or rpi3 images).
5. I am using onboard eMMC.
6. I get the multi-colored screen and nothing else. If I understand correctly
that means that the bootcode.bin and the start.elf have loaded but it hangs
when the kernel loads (the color screen does not go away)
7. I have also tried to do a full system upgrade from our current image to the
latest stuff available in the ArchLinux ARM repositories and it is even worse.
In this case I do not even get the colored screen.
8. The latest Rasbian image boots fine but none of the ArchLinux ARM images
from November to current work, they all hang in the same place.
I have a PI3 board that I started testing last Friday:
1. The rpi3 images boots but is VERY unstable.
2. The rpi2 images seems to work fine.
3. This shows the possiblity that a CM3 might work but that does not help
due to the fact that I have 1000+ CM modules that I CAN NOT use.
The problem is that Newark has not been very open about the changes nor have
they been helpful in providing information about the actually changes needed.
It almost appears that they have tried to conceal the change and to slip the
changes in quietly.
At this point the odds are pretty good that we will be shipping 1000+ CM modules
back to Newark expecting a FULL refund. And we will be forced to find a different
solution, one that does not use a Raspberry PI.