Linux Distributions for Orange PI H3 boards

Vladimir55 · Published in 2015-8-31 21:46:28

Edited by Vladimir55 at 2015-8-31 21:48

Hi Loboris!
on line "gcc -o myfile myfile.c " - he says there is no such "gcc".
can not install the compiler gcc.
you have examples of projects C use
gpio0-30, uart0, spi0, i2c0, CP210x, FTDI and PL2302
uart1-3 ?
What you image should I use?
thank.

loboris · Published in 2015-8-31 22:52:27

Edited by loboris at 2015-8-31 15:57

Vladimir55 replied at 2015-8-31 14:46
Hi Loboris!
on line "gcc -o myfile myfile.c " - he says there is no such "gcc".
can not install the ...

You must install build-essential package.
There is nothing special about UARTS & USB2serial, you can use them same way as on any Linux PC (ttyUSB*, ttyS*)
About using gpio's see here, there is the link to some examples in the last post.
I'm planning to test i2c & spi next week...
You can use any image you want.

blindpet · Published in 2015-9-1 00:25:08

loboris, I am having an issue building using the new script. I set my parameters like I did last time but I am not seeing the right values for UBOOT for Orange Pi Plus, I have tried these but get FATAL error.

UIMAGE="orange/uImage_OPI-PLUS"
BL1="orange/script.bin.OPI-PLUS_1080p60"
UBOOT="orange/u-boot_OPI-PLUS.fex"

Copy code

Any plans to put this on github with a readme and stuff, will make it much easier to update and track bugs/issues.

loboris · Published in 2015-9-1 01:06:54

blindpet replied at 2015-8-31 17:25
loboris, I am having an issue building using the new script. I set my parameters like I did last tim ...

These parameters are no longer used and they don't exist in params.sh.
The script builds universal image for all OPI boards, you just have to to copy one of the uImage_* and script.bin.* files on fat partition before booting to the specific board (as described in the 1st post).
Download make_linux.tar.gz, extract, change params.sh for desired distro, release, and output options, do not add anything to it.
About github, maybe if I'll have more time, and the whole project becomes more complex.

blindpet · Published in 2015-9-1 01:28:44

Edited by blindpet at 2015-9-1 01:55

loboris replied at 2015-9-1 01:06
These parameters are no longer used and they don't exist in params.sh.
The script builds universal ...

I thought that was the case, it seemed even after I removed the UBOOT parameters it still didn't like me giving an image name and kep throwing the FATAL error, any idea why?

How would I go about mounting the img file and copying the boot files you mentioned? I would like to prepare images for each OPI H3 which include my Media Server Installer, it will be nice not to have to recompile 5 times

Is there a place in params.sh I can put custom shell commands I want included? I think I mentioned it a while ago, did you every implement it?

I also see that the NO BUDGET COOLING option is gone, what happened with that, is it no longer necessary?

blindpet · Published in 2015-9-1 02:24:43

Edited by blindpet at 2015-9-1 02:32

On the /boot partition I deleted everything but the uImage_OPI-PLUS and renamed script.bin.OPI-PLUS_720p50 to script.bin. I am not booting.
EDIT, uImage_OPI-PLUS must be renamed to uImage (I believe first post says only script.bin-xxxx needs renaming).

alexparadise · Published in 2015-9-1 02:33:59

Why I cannot connect to my ethernet? And why there there is my wireless card call rename7?

orangepi@OrangePI:~$ ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:698 errors:0 dropped:0 overruns:0 frame:0
TX packets:698 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:57536 (57.5 KB) TX bytes:57536 (57.5 KB)
rename7 Link encap:Ethernet HWaddr 00:e0:4c:f0:1d:8a
inet addr:192.168.0.10 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::2e0:4cff:fef0:1d8a/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4574 errors:0 dropped:168 overruns:0 frame:0
TX packets:1257 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:39558278 (39.5 MB) TX bytes:1290654 (1.2 MB)
wlan1 Link encap:Ethernet HWaddr 02:e0:4c:f0:1d:8a
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:242 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

Copy code

loboris · Published in 2015-9-1 02:34:50

blindpet replied at 2015-8-31 18:28
I thought that was the case, it seemed even after I removed the UBOOT parameters it still didn't li ...

The simplest way to build an image:

do not change anything (ubuntu vivid will be created, if you want different distro/release, just change distro and repo parameters)
run: sudo ./create_image
Ubuntu Vivid fs will be created in linux-vivid directory
... if you need to, change anything you want in that directory, as root ...
run: sudo ./image_from_dir linux_vivid /dev/sdX to create bootable OPI SD Card
or
run: sudo ./image_from_dir linux_vivid my_opi_linux_image to create SDCard image
my_opi_linux_image.img, my_opi_linux_image.xz, and md5sum files will be created (if you don't need compressed xz archive, set _compress="no" in params.sh)
you can write the image to sd card: dd if=my_opi_linux_image.img of=/dev/sdX bs=1M oflag=direct
After cd card is created, mount 1st partition (VFAT, LABEL=BOOT) and copy uImage & script.bin according to yo board type

I don't see any reason why would you have to recompile 5 times.

If you want to install some packages, or do any configuration during the image creation, you can put your code into second_stage script.
It is executed in chrooted environment with qemu-arm-static arm emulation.
You can put your code (bash commands) before the line rm -Rf /boot/* >> $_LOGFILE 2>&1 in second_stage script.

Thermal management in the new kernel is much better, so no need for NO BUDGET COOLING option.

loboris · Published in 2015-9-1 02:37:27

alexparadise replied at 2015-8-31 19:33
Why I cannot connect to my ethernet? And why there there is my wireless card call rename7?

Probably the wrong script.bin selected.

loboris · Published in 2015-9-1 02:39:44

blindpet replied at 2015-8-31 19:24
On the /boot partition I deleted everything but the uImage_OPI-PLUS and renamed script.bin.OPI-PLUS_ ...

From the 1st post:
Copy uImage_OPI-2 or uImage_OPI-PLUS (depending on your board type) to uImage (for OPI-PC use uImage_OPI-2)