please choosego to mobile | Continue to access the PC version
Author: loboris

Linux Distributions for Orange PI H3 boards

  [Copy link]

0

threads

4

posts

32

credits

Novice

Rank: 1

credits
32
Published in 2015-8-30 17:01:22 | Show all floors
Edited by ismu at 2015-8-30 17:16
loboris replied at 2015-8-30 16:49
The uploaded desktop images are base image (mini) + desktop (installed with install_xxx_desktop scr ...

Thanks for anserws. I wait for modified uImage When can we expect it (approximately, it is important for you)? But I need only boot from /dev/sdb1, it is possible make it fast? I know you are a lot of work

10

threads

448

posts

4562

credits

Moderator

Rank: 7Rank: 7Rank: 7

credits
4562
 Author| Published in 2015-8-30 17:17:57 | Show all floors
ismu replied at 2015-8-30 10:01
Thanks for anserws. I wait for modified uImage  When can we expect it (approximately, it is impo ...

Maybe today, if testing goes well.
I'll include also the script to install Linux to USB HD (similar to install_to_emmc).

3

threads

38

posts

223

credits

Intermediate member

Rank: 3Rank: 3

credits
223
Published in 2015-8-30 18:35:23 | Show all floors
Edited by Sitheek at 2015-8-30 19:21

@loboris : I have tested your's new mini images - jessie and vivid - There are some problems with kernel, first I am getting gmac error and ethernet does not work, second if reboot or poweroff command is issued you will get kernel panic message.

We have succesfully compiled kernel on Debian Jessie X86_64 and Ubuntu Vivid x86_64. It is necessary to add i386 architecture support to compile it from SDK with loboris scripts and install toolchain acording to H3 manual build documentation.

@loboris : Why have you deleted lechee.tar.gz from mega? Is it still neccesary or not?

I do not understand some of menuconfig options, what is soc camera support. I built these modules but i can not load it neither with modprobe nor insmod. It says no such file or directory. What is the difference between these modules and modules from vfe_sunxi subdirectory?

I will try to play with script.fex acording to instructions from orangepi v1, but I am still not sure what drivers should be loaded to get CSI Camera working.

For now i am not able to use OV5640 CSI Camera


7

threads

100

posts

647

credits

Senior member

Rank: 4

credits
647
Published in 2015-8-30 18:44:11 | Show all floors
What can be the reason when opi+ STOPS after 30,07 sec.
I replaced the Lib, the uImage and the script.bin

thank you

This thread contains more resources

You need to Log in to download or view,No account?    Register

x

1

threads

46

posts

583

credits

Senior member

Rank: 4

credits
583
Published in 2015-8-30 20:00:14 | Show all floors
Hi loboris,

Thanks for uploading to Google Drive.  Much appreciated.

Cheers,
Steven

10

threads

448

posts

4562

credits

Moderator

Rank: 7Rank: 7Rank: 7

credits
4562
 Author| Published in 2015-8-30 21:19:15 | Show all floors
New kernel version uploaded.
Fixed problems with booting on trusty & wheezy images and with old images.

Please download scriptbin_kernel.tar.gz from Mega or Google drive, unpack and replace the kernel (uImage) on your SD Card (FAT partition), according with board used.

@john0815 I think the problem should be solved with new kernel.
@Sitheek
  have you copied the right script.bin and uImage ? Please use the new kernels.
  lechee.tar.gz was removed because there were some changes. I'll upload it again soon. It was needed only if you wanted to build your own kernel.
  I've ordered the camera module, when I receive it I'll try to fix the camera issues. For now I can't help you with anything related to camera. Sorry.

3

threads

38

posts

223

credits

Intermediate member

Rank: 3Rank: 3

credits
223
Published in 2015-8-30 21:42:56 | Show all floors
loboris replied at 2015-8-30 21:19
New kernel version uploaded.
Fixed problems with booting on trusty & wheezy images and with old i ...

I think the trick is related with proper settings of CSI sections in script.bin

I have changed only name of the camera form gc2035 to ov5640 and dmesg says somthing different than before :

[  277.578918] [VFE]cci probe start cci_sel = 0!
[  277.579014] [VFE]cci probe end cci_sel = 0!
[  277.579312] [VFE]cci_init end

[  299.283949] [VFE]Welcome to Video Front End driver
[  299.284292] [VFE]pdev->id = 0
[  299.284304] [VFE]dev->mipi_sel = 0
[  299.284311] [VFE]dev->vip_sel = 0
[  299.284318] [VFE]dev->isp_sel = 0
[  299.290142] [VFE_WARN]vfe vpu clock is null
[  299.298183] [VFE]..........................vfe clk open!.......................
[  299.298217] [ISP] isp platform_id = 5!
[  299.298378] [VFE]vfe_init end
[  299.300075] [VFE]probe_work_handle start!
[  299.300098] [VFE]v4l2 subdev register input_num = 0
[  299.300109] [VFE]vfe sensor detect start! input_num = 0
[  299.300123] [VFE]Find sensor name is "ov5640", i2c address is 78, type is "YUV" !
[  299.300135] [VFE]Sub device register "ov5640" i2c_addr = 0x78 start!
[  299.300149] [VFE]v4l2_device_register_subdev return 0
[  299.300158] [VFE]registered sensor subdev is OK!
[  299.300165] [VFE]Check sensor!
[  299.313469] [VFE]mclk on
[  299.380417] [VFE CCI_0 ERR] Status error at addr_8bit = 78, wr_flag = 1
[  299.380699] [VFE CCI_0 ERR] Status error at addr_8bit = 78, wr_flag = 1
[  299.380968] [VFE CCI_0 ERR] Status error at addr_8bit = 78, wr_flag = 1
[  299.380983] [OV5640]error at sensor_detect
[  299.380991] [OV5640]chip found is not an target chip.
[  299.381002] [VFE]mclk off
[  299.417317] [VFE]vfe sensor subdev unregister!
[  299.417341] [VFE]Sub device register "ov5640" failed!
[  299.417351] [VFE_ERR]vfe sensor register check error at input_num = 0
[  299.424816] [VFE]V4L2 device registered as video0
[  299.424847] [VFE]..........................vfe clk close!.......................
[  299.424871] [VFE]probe_work_handle end!
[  299.430795] [VFE]vfe_open
[  299.430815] [VFE]..........................vfe clk open!.......................
[  299.430850] [VFE]vfe_open ok
[  299.431044] [VFE]vfe_close
[  299.431056] [VFE]vfe select input flag = 0, s_input have not be used .
[  299.431075] [VFE]..........................vfe clk close!.......................
[  299.431110] [VFE]vfe_close end

Me and my friend will try to figure it out what to change in script.fex.
Superb, when you get the sensor we can work together to fix all issues

10

threads

448

posts

4562

credits

Moderator

Rank: 7Rank: 7Rank: 7

credits
4562
 Author| Published in 2015-8-30 22:51:58 | Show all floors
Edited by loboris at 2015-8-30 15:53

  install_xfce_desktop script updated.
  Fixed installing xfce desktop on Debian Jessie.

Download desktop_scripts.tar.gz from Mega or Google drive, extract to /usr/local/bin.

7

threads

100

posts

647

credits

Senior member

Rank: 4

credits
647
Published in 2015-8-30 23:36:48 | Show all floors
Edited by john0815 at 2015-8-30 23:54

Thank you - now boot from old image works.
Can you make a script to flash emmc from an older SD-Card image, I think there are some file missing, what your script needs.
Can you make a skript to make a Backup from emmc to SD-Card. So that we can use this SD card to flash another OPI

thx

10

threads

448

posts

4562

credits

Moderator

Rank: 7Rank: 7Rank: 7

credits
4562
 Author| Published in 2015-8-31 00:02:16 | Show all floors
Edited by loboris at 2015-8-30 18:23
john0815 replied at 2015-8-30 16:36
Thank you - now boot from old image works.

Question: How can I transfer my old system from sd-card  ...

Prepare your SD Card to work with new kernel/script.bin as described in the 1st post (use the newest scriptbin_kernel.tar.gz !)
Also copy all files (without lib directory) from scriptbin_kernel.tar.gz to /boot directory on your linux partition.
Then run install_to_emmc.
(script expects to find boot0_OPI.fex and u-boot_OPI-emmc.fex in /boot directory)

install_to_emmc can be easily adapted for reverse operation (emmc->sdcard). I'll do it later.
You need to log in before you can reply login | Register

Points Rule

Quick reply Top Return list