martinayotte
-
Posts
3892 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by martinayotte
-
-
There is a lot of changes that occured between 5.20 and 5.24, so don't worry about things that are missing, it would be useless to add them.
But for root=UUID, yes, you need to fix that, either by placing proper one, or simply by using "root=/dev/mmcblk1p1".
Yes, you will need to use mkimage command to get the boot.scr updated, then reboot without SD.
-
Boot from SD again, then do "mount /dev/mmcblk1p1 /mnt", then check /mnt/boot/boot.cmd and make sure the rootdev=/dev/mmcblk1p1.
Also check the same thing in /mnt/boot/armbianEnv.txt (I'm not sure if this file exist in older 5.20).
Check the /mnt/etc/fstab too for the device or UUID used in "/" partition.
(If some UUID is used, check what "blkid" is reporting)
-
try to get this to support h2 and h3 boards by using some autodection for
https://github.com/duxingkei33/orangepi_PC_gpio_pyH3/tree/master/pyA20/gpio ?
What is your question exactly about this PyA20 ?
-
dd if=/usr/lib/linux-u-boot-dev-orangepipcplus_5.24_armhf/u-boot-sunxi-with-spl.bin of=/dev/mmcblk2 bs=1024 seek=8
You also need to check rootdev is set properly in your /boot/boot.cmd
-
This can occurs on any Linux or even on other OS where files a cached and written to disk in background after a certain amount of time.
If you wish to ensure that files are not cache any more, the "sync" command will force the caching to be written on disk.
Power failure will always produce such behaviour, even on PC or Mac.
-
@TKaiser, 5 cents is pretty low estimate, I would rather say 20 cents, even 30 cents if we wish 128Mbits
BTW, today, I've worked on get U-Boot-SPL-SPI running on my Zero-M2+ ...
I've finally got it working few minutes ago, it was able to boot from USB dongle without SDCard via this U-Boot-SPL-SPI.
Next steps is to get it able to boot from network ...
For H5, I presume there still a lot of work to get it work, André told me that it still WIP.
-
Be careful, some of those USL-TTL Serial are 5V not 3.3V, in such case, TX must have a additional voltage divider to avoid problem with 3.3V target if the input is not 5V tolerant.
-
Personally, I prefer python. But C libs can be usefull when speed is needed. Sysfs should be already handled by kernels.
-
Yes, RPi.GPIO is coming from RaspberryPi community, I'm using the RPi.GPIO-PineA64 derivative since it is already as most pins there, I've submit a PR yesterday to add SPI/I2C borrowed from Olimex pyA20 to this pineA64 derivative, original Pi version still don't support those yet.
On H3, I prefer using the orangepi_PC_gpio_pyH3 since it is a derivative directly from Olimex pyA20 : https://github.com/duxingkei33/orangepi_PC_gpio_pyH3
-
Yes, I've read the irclog you've provided.
I don't know why it should not have been done that way in first place.
Something Mainline gurus are taking shortcuts ... ;-)
-
Did you verify the rootfs in /boot/boot.cmd and /etc/fstab ?
If those are perfect, then, you will need to hook some USB-TTL Serial on Debug port and provide us the boot log output.
-
Right ! This method could also be used when you wish to re-install a small image on smaller SDCard.
-
Here is how to shrink an existing image.
In "gparted", do "edit/resize" of the partition, but leave a certain percentage of free space, then "Apply".
Replace the "endsect" by the actual number shown by fdisk.
sudo modprobe loop sudo losetup -f sudo losetup /dev/loop0 myimage.img sudo partprobe /dev/loop0 sudo gparted /dev/loop0 sudo losetup -d /dev/loop0 fdisk -l myimage.img truncate --size=$[(endsect+1)*512] myimage.img
-
Yes, indeed, my previous post could help.
Check also the root partition in /boot/boot.cmd and also in /etc/fstab files located in the eMMC.
-
No, he did a lot more work that Icenowy has not done yet. Many empty stubs were still there in her branch.
https://github.com/Icenowy/xradio/compare/master...fifteenhex:master
For the MAC, he merged a commit from her :
https://github.com/fifteenhex/xradio/commit/911c488ebab45d075215ae4967044134df358ad7
-
Hoping that fifteenhex will send a PR to Icenowy for his work.
-
It seems that Icenowy is working to port the XRadio WiFi driver into mainline. Not ready yet, but should be there soon.
-
(alphabet - 1) * 31 + pin no. = A3 = (0-1)*31+3 = 3
This is not true !
it should be calculated as :
(alphabet - 'A') * 32 + pin no. = A3 = (0)*32 + 3 = 3
And for PG11 :
(alphabet - 'A') * 32 + pin no. = A3 = (6)*32 + 11 = 203
-
Yes, this is true for all Soc from AllWinner.
-
If you OPi doesn't act as a router between 2 ethernet ports, there is no reason to add port forwarding on the OPi.
If the OPi is inside your network and works perfectly from inside, then your issue is really on your external router.
-
dtc: invalid option -- '@'
This means that you have the stock version of DTC which is unaware of overlays, not the one which understand overlays.
You can get the good one, version DTC 1.4.1-g47216cdb, from :
https://github.com/pantoniou/dtc.git
and choose the proper branch :
dt-overlays5
-
Yes, if you do the change directly into the main DTS, only "okay" should be required.
For overlay, your issue is probably that you didn't use "-@" option of DTC, the command line should be :
dtc -@ -I dts -O dtb -o i2c-enable.dtb i2c-enable.dts
-
That is probably a completely different issue...
-
I have M64 which has similar Gbe issue as Pine64 if not the exact same issue, unfortunately this possible fix did not work on M64.
Oh ! this is bad news !
So, maybe it won't work for Pine64 too ...
boot from sd/usb to emmc
in Allwinner sunxi
Posted
You seems to be at 2 inch from success ...
The "disk" in /dev/disk/mmcblk1p1 should not be there ...
Maybe the error isn't in boot.cmd, since you provide proper root there.
Did you check again in /etc/fstab of the eMMC ? (so in /mnt/etc/fstab when mounted from sd boot)