Author: loboris

Linux Distributions for Orange PI H3 boards

  [Copy link]

3

threads

28

posts

151

credits

Registered member

Rank: 2

credits
151
Published in 2015-9-2 00:33:40 | Show all floors
Edited by Vladimir55 at 2015-9-2 00:45
loboris replied at 2015-9-1 23:19
Have you copied:
script.bin.OPI-2_1080p60  -->  script.bin
uImage_OPI-2  -->  uImage

Hello Loboris!
I'm probably not an expert
You can say details how and where that copy?
I have an image "Debian_jessie_mini.img"
what to do?

10

threads

448

posts

5042

credits

Moderator

Rank: 7Rank: 7Rank: 7

credits
5042
 Author| Published in 2015-9-2 01:00:50 | Show all floors
Vladimir55 replied at 2015-9-1 17:33
Hello Loboris!
I'm probably not an expert
You can say details how and where that copy?

If you are on Debian Jessie mini (no Desktop):
After writing the image (Debian_jessie_mini.img) to SD Card:
Insert the SD Cart into OPI
Power on, wait for login prompt
login (orangepi, orangepi)
run:
  1. sudo cp /media/boot/script.bin.OPI-2_1080p60 /media/boot/script.bin
  2. sudo cp /media/boot/uImage_OPI-2 /media/boot/uImage
  3. sudo reboot
Copy code
After reboot everything should be OK.
If it does not reboot (kernel panic), just power of, then power on.

3

threads

38

posts

223

credits

Intermediate member

Rank: 3Rank: 3

credits
223
Published in 2015-9-2 05:03:31 | Show all floors
Edited by Sitheek at 2015-9-2 05:10

Ok, my friend @mikexx debugged CSI port on Orange Pi 2 with logic analyzer so these are things we figured out:

1. There is no power supply for CSI camera because SoC pin PA17 is in down state - 0 volts. This pin is required to be in high state - it enables power supply for CSI camera.

2. I2c 0 works, probalby I2c 1 works too, but I2c 2 which is connected to CSI port will not work until again PA17 pin is in low state. Data and clock lines of I2c are pulled up through resistors from PA17, so if it is 0 volts I2c 2 can not work too.

To enable any CSI camera PA17 pin should be in high state. Setting it through script.bin does not work.

We tried using gpio-sunxi module without sucess. gpio-sunxi.ko does not allow to set PA17 pin.
I looked into sources of gpio-sunxi and it's includes, but I am not a coder.

I figured out that there are addresses of essential registers defined in /arch/arm/mach-sunxi/include/mach/sun8i/platform-sun8iw7p1.h, but I do not understend how gpio-sunxi kernel module knows what pins to use.

Accorging to Allwiner's H3 soc documentation - page 318 - PA17 pin can be used as gpio, but I do not know why it is not allowed by gpio-sunxi module.

@loborys could you help us and tell us how to set PA17 high? We can rebuild kernel, we use your's old lichee.tar.gz, could you post the new one?

10

threads

448

posts

5042

credits

Moderator

Rank: 7Rank: 7Rank: 7

credits
5042
 Author| Published in 2015-9-2 05:41:04 | Show all floors
Edited by loboris at 2015-9-1 22:43
Sitheek replied at 2015-9-1 22:03
Ok, my friend @mikexx debugged CSI port on Orange Pi 2 with logic analyzer so these are things we fi ...

I have not enough time to look deeper into it until next week, but I've tried a simple trick.I've replaced gpio deffinition for gpio_pin_28 in fex from PA20 to PA17:
orig:  gpio_pin_28      = port:PA20<1><default><default><0>

new:  gpio_pin_28      = port:PA17<1><default><default><0>

Now, PA17 apears in /sys/class/gpio_sw
You can download compiled script.bin with that change from here. Copy it as script.bin to fat partition.

3

threads

28

posts

151

credits

Registered member

Rank: 2

credits
151
Published in 2015-9-2 13:58:39 | Show all floors
loboris replied at 2015-9-2 01:00
If you are on Debian Jessie mini (no Desktop):
After writing the image (Debian_jessie_mini.img) to ...

Hi!
everything works thanks!
There is a problem with UART 0-2
Target data rate greater 115200. (230400-460800-921600)
instead 230400 we have 214000 (error baund)
the default is  uart_clock =24000000 Hz.
24000000/16/13 =115384.6 ~=115200  +/-2% permissible for UART
24000000/16/7 =214285.7  -error !
in rasberi Pi:
edit boot/config.txt
init_uart_clock = 14,745,600 Hz.
14745600/16/1=921600.
data rate =921600 - ok.
i need to change takt  UART c 24000000 to 14,745,600 Hz.
how can this be done in Orange PI?


10

threads

448

posts

5042

credits

Moderator

Rank: 7Rank: 7Rank: 7

credits
5042
 Author| Published in 2015-9-2 15:44:18 | Show all floors
Vladimir55 replied at 2015-9-2 06:58
Hi!
everything works thanks!
There is a problem with UART 0-2

I don't think it can be done easily.
For speeds greater than 115200 bd you have to use USB->Serial adapter.
I'm using CP2102 based adapter, it is only ~1.5$ and has all control signals exposed.

3

threads

28

posts

151

credits

Registered member

Rank: 2

credits
151
Published in 2015-9-2 16:01:29 | Show all floors
Ok!
but if not possible to change the cycle.
need to get into the H3 PLL registers...
cp2101-3 work, but it's USB and it is not very reliable.

SPI 0-1 has a question - will it work?


0

threads

16

posts

82

credits

Registered member

Rank: 2

credits
82
Published in 2015-9-2 17:16:45 | Show all floors
HI,

I still cannot get x2go server working. trying with both ubuntu mate img and debian jessie xfce img.
follow loboris instruction downloaded desktop_script.tar.gz copy to /usr/local/bin sudo install_x2goserver  
everything installed without any error. even with fresh image.

but when connect with x2go client

NXPROXY - Version 3.5.0

Copyright (C) 2001, 2010 NoMachine.
See http://www.nomachine.com/ for more information.

Info: Proxy running in client mode with pid '20746'.
Session: Starting session at 'Wed Sep  2 16:47:46 2015'.
Info: Using abstract X11
NXPROXY - Version 3.5.0

Copyright (C) 2001, 2010 NoMachine.
See http://www.nomachine.com/ for more information.

Info: Proxy running in client mode with pid '20804'.
Session: Starting session at 'Wed Sep  2 16:49:23 2015'.
Info: Using abstract X11 socket in kernel namespace for accessing DISPLAY=:0.
Info: Connecting to remote host 'localhost:31007'.
Info: Connection to remote proxy 'localhost:31007' established.
Error: The remote NX proxy closed the connection.
Error: Failure negotiating the session in stage '7'.
Error: Wrong version or invalid session authentication cookie.
Session: Terminating session at 'Wed Sep  2 16:49:23 2015'.
Session: Session terminated at 'Wed Sep  2 16:49:23 2015'.
socket in kernel namespace for accessing DISPLAY=:0.
Info: Connecting to remote host 'localhost:31004'.
Info: Connection to remote proxy 'localhost:31004' established.
Error: The remote NX proxy closed the connection.
Error: Failure negotiating the session in stage '7'.
Error: Wrong version or invalid session authentication cookie.
Session: Terminating session at 'Wed Sep  2 16:47:46 2015'.
Session: Session terminated at 'Wed Sep  2 16:47:46 2015'.

4

threads

52

posts

284

credits

Intermediate member

Rank: 3Rank: 3

credits
284
Published in 2015-9-2 18:41:36 | Show all floors
Edited by makama80 at 2015-9-2 18:42

@raid3868: Maybe you can try x11vnc as an alternative. I use it as well and it works also great, however: I prefer the x2go because it is a real X-window system.

@loboris: do you have the Mali also on your radar? I have a pcduino3 nano (A20/Mali400) where the Mali actually works in Linux. So it is possible to have it running under Linux.
Because I just received my OPI+, I did not yet try your images (which I certainly will!) and also do an attempt to get the Mali working. Any idea if it is possible with the way Linux runs on the OPI H3 boards?

I am going to start a.s.a.p. to create a document with screenshots and (hopefully!) clear instructions / tutorials to document what's in the forum. Currently a lot info is scattered here and there, and I think a single document with all info together can be of great help.

10

threads

448

posts

5042

credits

Moderator

Rank: 7Rank: 7Rank: 7

credits
5042
 Author| Published in 2015-9-2 20:52:08 | Show all floors
Edited by loboris at 2015-9-2 19:25
raid3868 replied at 2015-9-2 10:16
HI,

I still cannot get x2go server working. trying with both ubuntu mate img and debian jessie xfce ...

It is problem of your x2go client, try to use another. I'm always using pyhoca-gui as x2go client.

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

Points Rule

Quick reply Top Return list