+- PINE64 (https://forum.pine64.org)
+-- Forum: PINE A64-LTS / SOPINE Compute Module (https://forum.pine64.org/forumdisplay.php?fid=66)
+--- Forum: Clusterboard (https://forum.pine64.org/forumdisplay.php?fid=91)
+--- Thread: Differences in hardware revision 2.2 vs. 2.3? (/showthread.php?tid=12218)
Differences in hardware revision 2.2 vs. 2.3? - poVoq - 11-19-2020
https://wiki.pine64.org/wiki/SOPine_Clusterboard
Sadly this page does not specify and differences between the 2.2 and 2.3 hardware revisions, and it seems something changed
on how the emmc is used, as the current Armbian images seem to only have working emmc with hardware revision 2.3
If there was some details from Pine64 what was changed, maybe it would be possible to fix the Armbian image for version 2.2.
@tllim
RE: Differences in hardware revision 2.2 vs. 2.3? - tllim - 11-21-2020
(11-19-2020, 08:29 AM)poVoq Wrote: https://wiki.pine64.org/wiki/SOPine_ClusterboardI just aware there is only one Clusterboard version and will check with hardware team.
Sadly this page does not specify and differences between the 2.2 and 2.3 hardware revisions, and it seems something changed
on how the emmc is used, as the current Armbian images seem to only have working emmc with hardware revision 2.3
If there was some details from Pine64 what was changed, maybe it would be possible to fix the Armbian image for version 2.2.
@tllim
RE: Differences in hardware revision 2.2 vs. 2.3? - poVoq - 12-03-2020
@tllim any response from the hardware team?
It would be really great if I could get the emmc working on my 2.2 clusterboard, but I ran out of ideas. If they confirm that it is actually broken on 2.2 then that would be also good to know as I could then stop trying...
RE: Differences in hardware revision 2.2 vs. 2.3? - dsimic - 02-20-2021
There are at least three versions of the Clusterboard. The first version had to be fixed manually for the eMMC to work, and the second version included that fix. The third version no longer includes the components necessary to connect Lithium batteries to each of the SOPine modules.
It would be great if that could be somehow officially documented.