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

Linux Distributions for Orange PI H3 boards

  [Copy link]

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

5071

credits

Moderator

Rank: 7Rank: 7Rank: 7

credits
5071
 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

5071

credits

Moderator

Rank: 7Rank: 7Rank: 7

credits
5071
 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

5071

credits

Moderator

Rank: 7Rank: 7Rank: 7

credits
5071
 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.

7

threads

100

posts

647

credits

Senior member

Rank: 4

credits
647
Published in 2015-8-31 03:28:35 | Show all floors
Thank you. It had worked. I had to copy the files from fat to emmc fat extra.

I think you are the same who had presented in freaktab forum a linux solution for mk808b+.
I have the prob that keyboard and lan do not work after switching from android tu mate. In android both work.
Any idea what ca happened.

Have you seen this
https://www.youtube.com/watch?v=mAs75Ck4RAU

Is it realistic that this is ok and a beginner than I can build such an image.

Thx for your kind reply

3

threads

28

posts

151

credits

Registered member

Rank: 2

credits
151
Published in 2015-8-31 16:41:55 | Show all floors
Hi!
Please tell me which of your assemblies
i can use
UART 1-3, USBtoCOM, SPI, i2c, PWM, intrrupt GPIO, intrrupt Timer?
and compiler GCC ?
how to modify your project (detail)
thank.

10

threads

448

posts

5071

credits

Moderator

Rank: 7Rank: 7Rank: 7

credits
5071
 Author| Published in 2015-8-31 18:36:27 | Show all floors
Vladimir55 replied at 2015-8-31 09:41
Hi!
Please tell me which of your assemblies
i can use

gpio0-30, uart0, spi0, i2c0 (twi0) are enabled
usb2serial drivers are available for CP210x, FTDI and PL2302

In the next kernel version I'll enable pwm and uart1-3

I don't understand what do you mean by "and compiler GCC ?" and "how to modify your project"

10

threads

448

posts

5071

credits

Moderator

Rank: 7Rank: 7Rank: 7

credits
5071
 Author| Published in 2015-8-31 18:59:24 | Show all floors
Edited by loboris at 2015-8-31 13:05

Update:
  • Debian Jessie with XFCE desktop uploaded to Mega.
  • desktop & install scripts (desktop_scripts.tar.gz) updated
  • build scripts (make_linux.tar.gz) updated
  • added new script install_to_sdcard. Use it to backup your emmc installation to bootable sd card. See 1st post for details


Hints:
  • When installing to emmc, you can use btrfs option to format your emmc Linux partition as btrfs, it will be mounted with compress=lzo option and you can save up to 40% of emmc size.
  • Check the 1st post to see if there are updated kernels, script.bin (scriptbin_kernel.tar.gz) and install scripts (desktop_scripts.tar.gz) available


You need to log in before you can reply login | Register

Points Rule

Quick reply Top Return list