I am at ITS World Congress in downtown Detroit today, so I can't do any
testing until this evening...
On 09/09/2014 07:02 AM, Hans de Goede wrote:
Hi,
On 09/09/2014 12:28 PM, Robert Moskowitz wrote:
On 09/09/2014 02:41 AM, Hans de Goede wrote:
Hi,
On 09/09/2014 07:40 AM, Marcin Juszkiewicz wrote:
W dniu 09.09.2014 o 04:51, Robert Moskowitz pisze:
Read Hans de Goede's post on the F19 and the Allwinner (Cubie) back on
12/26/2013. He supposedly uses the SID for a consistant local scope
MACaddr. I Do get that on my Cubieboard2, but not on my Cubietruck.
Hans also told that there was a bunch of Cubie* with pre-production cpus
which lacked serial number.
AFAIK only cubieboard2 and olinuxino-a20-micro suffer from this, the
cubietruck is fine. On machines with an all 0 sid this indeed does not
work.
My SIX Cubieboard2 all are fine with a consistant MAC address.
Good, then later runs of the cubieboard2 have gotten a proper SID, that is good.
My one Cubietruck keeps coming up with the unique MACaddr. Exact opposite of what you are reporting.
Which version of Fedora are you running on your Cubietruck ?
Your F19 and last the 9/5 build of F21-minimal. Here is what I do for
the F19:
http://docs.cubieboard.org/tutorials/cb2/installation/cb2_fedora_19_card_install
xzcat /home/rgm/arm/Fedora-19-a10-armhfp-r3.img.xz > /dev/sdb; sync
<reinsert card>
/run/media/rgm/uboot/select-board.sh cubieboard2[cubietruck]
umount /run/media/rgm/uboot
umount /run/media/rgm/rootfs
I never saw anything after the R3 release.
With the respin images the kernel takes care of getting the MAC from the SID,
with the official F-21 images, u-boot needs to do this, and the u-boot included
is (not yet) new enough.
hmmm. For cubieboard2, I use your git repo:
git clone https://github.com/jwrdegoede/u-boot-sunxi.git
cd u-boot-sunxi
git checkout -B next origin/next
make -j4 CROSS_COMPILE=arm-linux-gnu- Cubieboard2_defconfig
make -j4 CROSS_COMPILE=arm-linux-gnu-
dd if=u-boot-sunxi-with-spl.bin of=/dev/sdb bs=1024 seek=8
sync
Is there a way to also make a uboot for the cubietruck to update what is
on koji?
Perhaps there is a rev difference in the shipped nand? In all cases, I never did anything with the nand image, but went right to the SDcard image. I just don't get how to do the nand poking to get something working from it.
The SID is in the SoC, it has nothing to do with the nand.
Well that is a start.
Is there any test I can run on my CT?
You can dump the sid by hooking up a serial console, and then pressing a
key to interrupt u-boot, then do:
md 1c23800 4
If I don't have an SDcard in the unit I end up at a sunxi# prompt. Is
this the same thing?
To get the SID contents, see here for example SID-s :
http://linux-sunxi.org/SID_Register_Guide
If this is non-0 on your cubietruck, then you should get a consistent MAC
with the respin images, and you should be able to get a consistent MAC
with F-21 by building (and installing) u-boot from here:
http://git.denx.de/?p=u-boot.git;a=summary
Makes no sense to me. What do I do with this?
Those are the official u-boot sources, and those now have everything needed
to run F-21. Note do not use this u-boot with the respin images, that does
not work (yet).
I did try yesterday. And it did not work. ;)
anyway to set the SID if it is zero?
Not that we know of.
I will test the CT tonight.
_______________________________________________
arm mailing list
arm@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/arm
