martinayotte
-
Posts
3892 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by martinayotte
-
-
You could do locally on your own tree by editing the config/boards/orangepilite.conf file, and change the line below :
KERNEL_TARGET="default,next,dev" -
2 minutes ago, zador.blood.stained said:
This is only for the mainline/dev images
I always forget about that, since I always running Mainline ...
-
Even if you change the boot.cmd, this will only affect the kernel output, but u-boot will still output stuff on that serial port.
To use other serial ports, you simple need to turn them on by using overlays.
To do so, add the following in /boot/armbianEnv.txt :
overlays=uart1 uart2 uart3... and then reboot ...
-
The XR819 crappy driver isn't present in 4.11.x builds, simply because it is crappy and we don't want to officially support it.
The only way to get it compiled, is to build your own image with the patches and defconfig enabling it.
-
Without looking at the output log on serial debug, it is pretty hard to narrow the cause.
If the serial debug doesn't even show u-boot starting, it could be hardware issue.
-
To remove the logo, simply delete the file /boot/boot.bmp
-
Right ! This is true for all 64bits SoC, I've narrowed that on PineA64 too...
There is not so much "unsigned int" to "unsigned long" conversion required, if I remember : 2 in the gpio_lib.h and 2 in gpio_lib.c.
-
"ftd set" is a u-boot command to alter existing DT, here, in this case, changing status to "okay".
-
Are you sure it is an Armbian image and not a ayufan one ?
-
Unfortunately, the http://kaiser-edv.de/tmp/NumpU4/brcmfmac43430-sdio-broadpwn-fix.tar files don't seems to work.
I'm getting timeout and refuse to register its interface :
[ 15.660083] brcmfmac: brcmf_fw_map_chip_to_name: using brcm/brcmfmac43430a0-sdio.bin for chip 0x00a9a6(43430) rev 0x000000 [ 16.840982] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50 [ 17.868309] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50 [ 18.872331] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50Replacing back the old A0 firmware files, and it works again :
[ 7.900828] brcmfmac: F1 signature read @0x18000000=0x1530a9a6 [ 7.903201] brcmfmac: brcmf_fw_map_chip_to_name: using brcm/brcmfmac43430a0-sdio.bin for chip 0x00a9a6(43430) rev 0x000000 [ 7.903368] usbcore: registered new interface driver brcmfmac [ 8.180503] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Jul 1 2016 18:02:40 version 7.10.1 (A0 Station/P2P feature) FWID 01-bae8afee -
Yes, this is a discrepancy between u-boot version and only occurs when doing an update instead of using fresh build.
-
I wished to have the AP6212 WiFi working on my NanoPi-K2 !
BTW, it is a AP6212 Non-A ...
So, at first it didn't work. After investigation and few tries, I figured out that a another firmware was needed :
as discuss by Hans back in June https://patchwork.kernel.org/patch/9791523/
http://jwrdegoede.danny.cz/brcm-firmware/brcmfmac43430a0-sdio.bin.7.10.1.244.ucode940.1020
to be rename as brcmfmac43430a0-sdio.bin
http://jwrdegoede.danny.cz/brcm-firmware/brcmfmac43430a0-sdio.txt.jumper-ezpad-mini3
to be rename as brcmfmac43430a0-sdio.txt
Hans patch is already merged in 4.13...
-
Yes, shorting video could damage it !
You're better to solder wire to an external jack.
-
Post the RPi overlay version here, we can probably just tweak it.
-
404 means "File not found" .
Usually, it is simply that some URLs are not up-to-date. So, a simple "apt-get update" will take the list of latest URLs.
-
17 hours ago, TonyMac32 said:
This image (if it works) expects /boot/boot.scr to exist and tell it about the bootargs, the dtb, etc just like the "le potato" image I linked earlier. It also expects an EXT4 filesystem.
@TonyMac32 This one is working too, after creating a boot.scr.
The only strange thing I seen is that "saveenv" isn't working, but it is not a big issue, since boot.scr is doing all the things.
gxb_p201_v1#saveenv Saving Environment to aml-storage... emmc/sd response timeout, cmd8, status=0x3ff2800 emmc/sd response timeout, cmd55, status=0x3ff2800 emmc/sd response timeout, cmd1, status=0x3ff2800 MMC init failed -
17 hours ago, martinayotte said:
For a permanent change of ttyAML0, I've done it in board/amlogic/configs/nanopi-k2.h, but it seems to be overwritten and keep getting back to ttyS0, although a "strings fip/u-boot.bin.sd.bin" reveal that my change is actually present.
Any hints ?
Answering to myself : stupid me ! the u-boot default args are overwritten by "saved" args, so I've done them manually again but I had to "saveenv" to keep them ...
-
@TonyMac32 , I will try you u-boot tomorrow and find what are behaviour differences ...
Initially, I wished to have Armbian nanopi-k2.wip working as I did few months ago for OPiPC2 with the help of André and Zador with their patches for FIT/ATF, but the AmLogic u-boot looks really different ... Is FIP almost equivalent to FIT ?
So, I doubt I will be able to automate nanopi-k2.wip builds soon, since I even have to manually issued u-boot command, but at least I've got this kernel booted ...
-
I must admit that I didn't tried it on Pinebook, since I'm still running ayufan image ont it.
But nand-sata-install should work the same way as for other boards ...
Do you have an USB-TTL to Audio Jack to figure out where it is choking ?
-
Thanks @balbes150 for the hint !
It was really using the ttyS0 instead of the ttyAML0 ...
At the prompt of this u-boot compiled with https://github.com/friendlyarm/u-boot/tree/nanopi-k2-v2015.01 , I've manually changed it and see that it booted further.
I've than noticed that the kernel didn't succeeded to mount the ROOTFS, so I've added "rootwait rootfstype=ext4" to my manual command.
For a permanent change of ttyAML0, I've done it in board/amlogic/configs/nanopi-k2.h, but it seems to be overwritten and keep getting back to ttyS0, although a "strings fip/u-boot.bin.sd.bin" reveal that my change is actually present.
Any hints ?
Also, is that u-boot is the same as Mainline where it should execute a boot.scr ? I'm not seeing any on the current image.
-
I've also tried balbes today's image, fused the newly compiled u-boot, tweak image/ramdisk to match its filenames accordingly, booted but still stop at "starting kernel" ...
(I will take a break now, since I'm pulling too many of my hairs)
-
I did "./mk gxl_libretech_cc"
I must admit that I'm a bit lost with this board, compared with all the the work I've done with Allwinner ones.
-
Thanks @TonyMac32 !
Unfortunately, still doesn't work ! Boot loop mentioned above still there an u-boot never started ...
You u-boot build successfully, I've only had to change the CROSS_COMPILER path in the Makefile. The "make sure" you've mentioned were already present, so I've "dd" the resulting "u-boot.bin".
It looks like it doesn't even load that u-boot. What those means exectly ?
GXBB:BL1:08dafd:0a8993;FEAT:EDFC318C;POC:3;RCY:0;EMMC:800;NAND:81;SD:0;READ:0;CHK:F3;USB:8;LOOP:1;Some thing look strange to me : doing "strings u-boot.bin" doesn't show any default variables like it used too with any other u-boot.
EDIT : btw, are you sure about "bs=512 seek=1" ? It seems to be pretty low compare to AllWinner where u-boot is usually placed at "bs=1024 seek=8"
-
Do you means that you've used a OdroidC2 build to run on LePotato and you didn't face the protection I've mentioned ?
I will try to build a LePotato image and try to boot it on K2 ... Thanks !
EDIT : Unfortunately, a LePotato image doesn't work, it produce the same boot loop I've originally mentioned few weeks ago.
GXBB:BL1:08dafd:0a8993;FEAT:EDFC318C;POC:3;RCY:0;EMMC:800;NAND:81;SD:0;READ:0;CHK:F3;USB:8;LOOP:1;EMMC:800;NAND:81;SD:0;READ:0;CHK:F3;USB:8;LOOP:2;EMMC:800;NAND:81;SD:0;READ:0;CHK:F3;USB:8;And of course, fusing the crappy k2uboot.bin was waste of time, because it require a FAT boot partition.
I think I'm missing a lot of knowledge on those AmLogic (I'm too fluent with AllWinner).
Armbian for OrangePi PC2, AllWinner H5
in Allwinner sunxi
Posted
@John BrooksThe Next-4.13 has been added by Zador for several H3 boards only 5 days ago ... So, not a lot of tests have been done ...
Why not starting by using the one well tested since months : Dev-4.11 ?