Jump to content

CSC Armbian for RK3318/RK3328 TV box boards

jock

By jock
in Rockchip CPU Boxes

 Share

Recommended Posts

jock

jock

Posted
  • Author
Posted
  On 5/2/2022 at 7:11 PM, MBB said:

I have flashed an X88 Pro 10 box and run rk3318-config.  Wifi is identified as BCM4334 correctly and works.  Bluetooth is found but using XFCE 'devices' option, finds none.  I tried a second model (H96 Max) and it behaves the same.  If I plug in a TP Link bluetooth adapter, devices are found and work fine.  Anyone else running into this?

Expand  

That's strange bluetooth does not work, AP6334/BCM4334 should be well supported. My box has the same chip and works fine.

dmesg may give some hints about, also a photo of the board and the original dtb may help.

0
MR01

MR01

Posted
Posted
  On 5/2/2022 at 9:41 PM, jock said:

I guess that you have the bcm43342 wifi part; dmesg will tell what firmware is actually needed for bluetooth.

It may be that

Probably here the led has the polarity inverted (active low vs. active high) in the device tree.

Grazie a te, gentilissimo ;)

 

 

Expand  

i have the same board of @markst precisely a X88-PRO-B-RK3318-D4-V1.2, but selled with a different name (QPLOVE Q9 4/128 [ram/emmc]) so maybe something is different, wifi works bth not.
And as the others guys with 4gb ram i can only use 2gb of ram.
image.thumb.png.e7232e08558b38a2eb81a5fbbb4e5f64.pngimage.thumb.png.b213be745e6bbdef98a3fb75a225f816.png

 

Firmware: BCM4330/4 wl0

0
jock

jock

Posted
  • Author
Posted

@MR01 looking at the dmesg screenshot you have a BCM4330 and not BCM43342 as @markst has, so they are totally different chips.

You probably have an AP6330 "package" on the board, which comprises of both wifi and bluetooth. BCM4330 is the wifi part, the bluetooth part is another completely different chip.

From that screenshot I can't say anything: those red lines are just for the wifi part. The seem errors, but are actually "information" messages (the guy who wrote the driver just used the wrong function call dev_err() instead of dev_info() probably)

Full dmesg is required because errors and messages about bluetooth may be scattered among the log.

0
MR01

MR01

Posted
Posted
  On 5/3/2022 at 9:03 AM, jock said:

 

You probably have an AP6330 "package" on the board

Expand  

AP6330 with a metal plate.

 

  Quote

root@rk3318-box:~# dmesg | grep -i blue
[    8.009535] Bluetooth: Core ver 2.22
[    8.009740] NET: Registered PF_BLUETOOTH protocol family
[    8.009753] Bluetooth: HCI device and connection manager initialized
[    8.009783] Bluetooth: HCI socket layer initialized
[    8.009795] Bluetooth: L2CAP socket layer initialized
[    8.009840] Bluetooth: SCO socket layer initialized
[    8.161276] Bluetooth: HCI UART driver ver 2.3
[    8.161321] Bluetooth: HCI UART protocol H4 registered
[    8.161329] Bluetooth: HCI UART protocol BCSP registered
[    8.161498] Bluetooth: HCI UART protocol LL registered
[    8.161513] Bluetooth: HCI UART protocol ATH3K registered
[    8.161608] Bluetooth: HCI UART protocol Three-wire (H5) registered
[    8.162107] Bluetooth: HCI UART protocol Intel registered
[    8.162679] Bluetooth: HCI UART protocol Broadcom registered
[    8.162847] Bluetooth: HCI UART protocol QCA registered
[    8.162864] Bluetooth: HCI UART protocol AG6XX registered
[    8.162956] Bluetooth: HCI UART protocol Marvell registered
[    8.551727] Bluetooth: hci0: BCM: chip id 62
[    8.552567] Bluetooth: hci0: BCM: features 0x0f
[    8.554381] Bluetooth: hci0: BCM4330B1
[    8.554418] Bluetooth: hci0: BCM4330B1 (002.001.003) build 0000
[    8.563141] Bluetooth: hci0: BCM4330B1 'brcm/BCM4330B1.hcd' Patch
[    9.345127] Bluetooth: hci0: BCM4330B1 37.4 MHz Class 1 Ampak
[    9.345172] Bluetooth: hci0: BCM4330B1 (002.001.003) build 0000
[    9.345903] Bluetooth: hci0: BCM: Using default device address (43:30:b1:00:00:00)
[    9.358938] systemd[1]: Reached target Bluetooth.

Expand  


Seems recognized and working NOW, yesterday didnt and i tried many times with many reboots, the only thing i did in late night (so right before now dmesg) was set in rc.local "ifconfig wlan0 down" because im using a powerfull external usb dongle.

So maybe when wifi is off bth works? Im not fond of kernel/drivers in general so maybe is no-sense.

I dont plan to use bth anyway.

Ps: im using this box as a powerfull switch WIFI>ETH because my house is on 2 plans and my only telephone port is in the plan down my actual pc and there must be the router....plus every plan is electrically "indipendent" with 2 different save-life (so i dont even try to use powerline), so for better signal i will put the box in a better position with a ethernet cable running side-wall from the box to my pc

dmesg.txtFetching info...

0
MBB

MBB

Posted
Posted
  On 5/2/2022 at 9:45 PM, jock said:

That's strange bluetooth does not work, AP6334/BCM4334 should be well supported. My box has the same chip and works fine.

dmesg may give some hints about, also a photo of the board and the original dtb may help.

Expand  

Board photo and dmesg attached.  Note this model is called "H96 max v11" which I gather is due to it shipping with Android 11.  It doesn't matter which LED overlay is selected, with either, bluetooth is detected but can't find any devices.  RK3318-config identifies WiFi as "BCM334/AmPak AP6334".  The markings on the chip itself, however, don't seem helpful.  Note the marking on the board is "KX 1943...".

PXL_20220504_193858652.jpg

dmesg_h96_max_v11Fetching info...

0
jock

jock

Posted
  • Author
Posted

@MBB these lines in dmesg are pretty clear: 

[   13.024841] Bluetooth: hci0: BCM: chip id 83
[   13.025663] Bluetooth: hci0: BCM: features 0x0f
[   13.027568] Bluetooth: hci0: BCM43342A
[   13.027624] Bluetooth: hci0: BCM (001.002.003) build 0000
[   13.036065] Bluetooth: hci0: BCM: firmware Patch file not found, tried:
[   13.036111] Bluetooth: hci0: BCM: 'brcm/BCM.hcd'

 

There is no firmware for your bluetooth chip. The problem has been seen in the past, but has not been solved because we could not guess what is the filename the bluetooth driver is looking for.

It finally tries to look to /lib/firmware/brcm/BCM.hcd file and you should try to do a symbolic link to some of the bcm4334*.hcd firmware file to see if any of them works.

Now I don't remember which one works, but surely there is a discussion with a forum member that had this working, maybe the forum search tool can help you.

 

0
MBB

MBB

Posted
Posted
  On 5/5/2022 at 9:25 PM, jock said:

@MBB these lines in dmesg are pretty clear: 

[   13.024841] Bluetooth: hci0: BCM: chip id 83
[   13.025663] Bluetooth: hci0: BCM: features 0x0f
[   13.027568] Bluetooth: hci0: BCM43342A
[   13.027624] Bluetooth: hci0: BCM (001.002.003) build 0000
[   13.036065] Bluetooth: hci0: BCM: firmware Patch file not found, tried:
[   13.036111] Bluetooth: hci0: BCM: 'brcm/BCM.hcd'

 

There is no firmware for your bluetooth chip. The problem has been seen in the past, but has not been solved because we could not guess what is the filename the bluetooth driver is looking for.

It finally tries to look to /lib/firmware/brcm/BCM.hcd file and you should try to do a symbolic link to some of the bcm4334*.hcd firmware file to see if any of them works.

Now I don't remember which one works, but surely there is a discussion with a forum member that had this working, maybe the forum search tool can help you.

 

Expand  

@jock, Thanks for the tip.  Now I understand how this is supposed to work.  I was able to get it working, but only using a symbolic link from BCM.hcd to BCM43342.hcd.  It looked like the filename would be BCM43342A1 (see dmesg below), but no such luck with that link.  In reading the previous posts, it seems @awawahad the same issue, but I may be reading it wrong.  So I am not sure how to cleanly fix this.  At least we know BCM43342.hcd works.  Happy to test anything you'd recommend.  But thank you for helping me get it at least working!

testFetching info...

0
jock

jock

Posted
  • Author
Posted
  On 5/6/2022 at 6:57 AM, MR01 said:


The user @hannah had the same AP6330 and bth BCM4330B1 in a s905x3 box and fixed with meson-sm1-sei610-x96maxplus.dtb
Im adding this info for future reference and fixing/implementation @jock

meson-sm1-sei610-x96maxplus.dtb 46.07 kB · 1 download

Expand  

Understand, but AP6330 should work both for wireless and bluetooth parts right now on rk3318/3328 - everything is already in place and implementation is right since, as you see, it works.

The issue you had must be investigated with more tests to get into the real cause (rfkill? wrong dtb? ...)

 

I have AP6330 in a rk3288 box and both wifi and bluetooth works well.

There are issue though when you do a lot of traffic at the same time with both devices, because co-existance is difficult on 2.4ghz channel and I never really digged into the issue.

 

0
Andre B

Andre B

Posted
Posted

hi @jock, about rk3318-config , i'm using H96 Max rk3318 4/64 (Black PCB)

1. should i choose emmc DDR Mode or emmc HS200 Mode ? currently i don't choose any of these options since i'm not sure which one suits my device

2. there are LED Presets, but not H96Max, is one of them support my board ? currently i choose the last option (generic/unlisted)

 

kindly let me know if you need a photo of my device board to help me choose the right options

 

Thanks !

0
Andre B

Andre B

Posted
Posted

and also, is it ok to re-run rk3318-config and change some options/parameters after some days usage ?

will it cause any problem/conflicts with system ?

0
jock

jock

Posted
  • Author
Posted
  On 5/6/2022 at 1:15 PM, Buqan Kaleng Kaleng said:

hi @jock, about rk3318-config , i'm using H96 Max rk3318 4/64 (Black PCB)

1. should i choose emmc DDR Mode or emmc HS200 Mode ? currently i don't choose any of these options since i'm not sure which one suits my device

2. there are LED Presets, but not H96Max, is one of them support my board ? currently i choose the last option (generic/unlisted)

 

kindly let me know if you need a photo of my device board to help me choose the right options

 

Thanks !

Expand  

Hello @Buqan Kaleng Kaleng

1. you should try and see which one works for your board. You can enable both of them: and a valid board, the kernel will choose the best option and it will just work. On a so-so board it may happen that the kernel choice does not really work and the board may have issues to detect the internal eMMC; then you need to use to use multitool to manually tinker with /etc/armbianEnv.txt and do trial and error to find which one works for you. If you are not skilled enough or are afraid to lose the installed system, keep both of them disabled so the safest (but slowest) capability will be used

2. H96Max is the tv box market name; we don't use the market name because the same tvbox can contain many different boards: you have to open the case and see the signature printed on the board PCB

0
jock

jock

Posted
  • Author
Posted
  On 5/6/2022 at 1:31 PM, Buqan Kaleng Kaleng said:

and also, is it ok to re-run rk3318-config and change some options/parameters after some days usage ?

will it cause any problem/conflicts with system ?

Expand  

It is perfectly ok and safe to do: you may want to change and test other parameters, it will not cause any conflict of any kind, at least if you don't modify manually the overlays line in /etc/armbianEnv.txt

 

0
MBB

MBB

Posted
Posted
  On 5/6/2022 at 10:27 AM, jock said:

Understand, but AP6330 should work both for wireless and bluetooth parts right now on rk3318/3328 - everything is already in place and implementation is right since, as you see, it works.

The issue you had must be investigated with more tests to get into the real cause (rfkill? wrong dtb? ...)

 

I have AP6330 in a rk3288 box and both wifi and bluetooth works well.

There are issue though when you do a lot of traffic at the same time with both devices, because co-existance is difficult on 2.4ghz channel and I never really digged into the issue.

 

Expand  

Yeah, I already though of some co-existance issues so previously tried turning WiFi off completely.  That didn't help.  And with WiFi on, it works just fine with the BCM.hcd symlink to BCM43342.hcd .  I agree everything is there, but it seems it is looking for a different filename so doesn't find the working BCM43342.hcd file and only works via the fallback symlink I added. Since it can't find what it is looking for, seems it can't be any other existing file.  So how to guess the right name to symlink?  For now, the fallback works for me, but I agree, not a very universal solution.

0
MX10.AC2N

MX10.AC2N

Posted
Posted

Hi everyone,
I'm looking to set up a minimal gui under wayland but it's not easy for a beginner.
I found https://github.com/arcbjorn/arc-arch-linux-installation-guide#for-full-desktop-gui
But it's based on arch linux and I struggle a bit to adapt..
So I'm trying to post here to see if some of us can manage a script for installing a minimal gui under wayland.. or if you think it's a waste of time to try this experiment (for the instant..)
Thanks again and again armbian is great..!

0
MR01

MR01

Posted
Posted
  On 5/9/2022 at 10:12 AM, MX10.AC2N said:

Hi everyone,
I'm looking to set up a minimal gui under wayland but it's not easy for a beginner.
I found https://github.com/arcbjorn/arc-arch-linux-installation-guide#for-full-desktop-gui
But it's based on arch linux and I struggle a bit to adapt..
So I'm trying to post here to see if some of us can manage a script for installing a minimal gui under wayland.. or if you think it's a waste of time to try this experiment (for the instant..)
Thanks again and again armbian is great..!

Expand  


I did install lightdm+lxde[core-minimal] on debian minimal without big problems.
But i removed all after finding out that hw accelleration didnt work on 5.15 kernel, so chrome will not run at all for example, and i old kernel was not running my usb dongle by default.

0
jock

jock

Posted
  • Author
Posted
  On 5/9/2022 at 12:17 PM, MR01 said:


I did install lightdm+lxde[core-minimal] on debian minimal without big problems.
But i removed all after finding out that hw accelleration didnt work on 5.15 kernel, so chrome will not run at all for example, and i old kernel was not running my usb dongle by default.

Expand  

I guess lightdm+lxde are not under wayland but rather regular X.org.

About hw acceleration, what do you mean? Both 3D acceleration via GPU and hw video decoding through VPU works on all recent mainline kernels, Chrome is just not able to deal with them: that's a long way to get there.

0
MR01

MR01

Posted
Posted
  On 5/10/2022 at 8:14 AM, jock said:

I guess lightdm+lxde are not under wayland but rather regular X.org.

About hw acceleration, what do you mean? Both 3D acceleration via GPU and hw video decoding through VPU works on all recent mainline kernels, Chrome is just not able to deal with them: that's a long way to get there.

Expand  


Chrome probably is missing OpenGL/OpenGL ES features that mainline kernel miss.
My bad on 3D with Lima driver.

0
Sigma7

Sigma7

Posted
Posted

This subject is precisely my question: so 3D video acceleration is already enabled by default? In some post the developer had said that he had disabled it. Sorry if I didn't pay attention to some previous explanation, but I'm confused about this topic, even if I can disable/enable it through some command via Terminal.

0
jock

jock

Posted
  • Author
Posted
  On 5/10/2022 at 8:41 PM, Sigma7 said:

This subject is precisely my question: so 3D video acceleration is already enabled by default? In some post the developer had said that he had disabled it. Sorry if I didn't pay attention to some previous explanation, but I'm confused about this topic, even if I can disable/enable it through some command via Terminal.

Expand  

I may remember not so well because rk3318 received little attention lately, but it should be enable and provided via opensource Lima driver.

You can check if AccelMethod is set to "glamor" (enabled) or "none" (disabled) in /etc/X11/xorg.conf.d/40-serverflags.conf

As usual, it is wise to disable compositing for a bit better performance in a typical desktop usage.

2
MR01

MR01

Posted
Posted
  On 5/10/2022 at 9:42 PM, jock said:

I may remember not so well because rk3318 received little attention lately, but it should be enable and provided via opensource Lima driver.

You can check if AccelMethod is set to "glamor" (enabled) or "none" (disabled) in /etc/X11/xorg.conf.d/40-serverflags.conf

As usual, it is wise to disable compositing for a bit better performance in a typical desktop usage.

Expand  

i only have /etc/X11/xorg.conf.d/01-armbian-defaults.conf
I dont think i removed or deleted it by accident because i never installed DE in this installation of minimal.

0
cmuki

cmuki

Posted
Posted

Hello, guys!

 

This would be my first post in the forum and I want to thank everyone contributing to the Armbian effort - I haven't had that much fun tinkering since forever!

 

My question is related to the RAM detection - I've scoured this thread as well as the possible other places for information, but couldn't find quite the same case, even though it's referenced at least 3 times inside this thread:

 

Multitool and Armbian only pick up 2 GB of ram; I've opened the box and there are 8 total K4B4G0446C chips on it (4 on each side). According to other posts, the data in the datasheet is shown in Gb instead of GB and, if my calcualtions are correct, it has 4 x 4 Gb, two on each side = 32 Gb = 4 GB RAM.

 

Is it possible that only one half is operational? If these are binned chips, is it possible for them to be halved? In all other cases regarding the RAM capacity that I've read about here the TV box already came with the wrong RAM size. In another forum users reported halving of the RAM after an Android firmware update, but there was an (Android) image that fixed the issue (I wouldn't know if it was fake or fixed a software bug).

 

The board is X88 PRO-B-RK3318-D4-V1.2 4 GB RAM (allegedly)/ 32GB ROM model (even though 64 ROM was ordered). As you can probably guess, before installing Armbian, Android reported 4 GB RAM/64 GB ROM, but all apps for filling up the RAM couldn't be installed.

 

Images of the board can be found here - https://imgur.com/a/wTQqXO5; armbian hardware log - http://ix.io/3XvN;

 

dmesg:

  Reveal hidden contents

 

I tried extracting the device tree file, but was able to get 11 different files; if they would be of help, I can also provide them here. Unfortunately, I do not have a UART module, but am willing to search for one locally.

 

Thank you in advance and have a nice day!

0
jock

jock

Posted
  • Author
Posted

@cmuki Well, the ways of the chinese cheap tv boxes are infinite... we have seen fake Androids that show more hardware or different hardware; in a case we have also seen a fake amlogic s905x chip which in reality was a rockchip rk322x chip: they altered both the serigraphy printed on the chip itself and the Android software to make it appear as an amlogic. The guy was not able to let armbian run until he finally tried rk322x image and voilà... it worked!

 

So it could be quite possible that your box is advertised with a fake specs (and indeed the eMMC is detected as a 32Gb part and not 64 as advertised), and even the chips are somehow fake, disconnected or broken.

There could obviously be a bug in the code, that even won't surprise me. To be really sure of the amount of RAM you have available you need the serial UART: at the very beginning, the boot process will show the amount of memory banks you have and their size. That's the source of truth, because it is a binary provided by rockchip itself.

 

If you still have Android installed (or did a backup), you can read that info during boot and that will provide a reliable info.

0
cmuki

cmuki

Posted
Posted

@jock, thank you for you swift reply! I'll try to get my hands on a UART module in the next couple of weeks and report back.

 

Hopefully the information will be helpful for other members of the forum as well!

1
MR01

MR01

Posted
Posted
  On 5/11/2022 at 10:39 AM, MR01 said:

i only have /etc/X11/xorg.conf.d/01-armbian-defaults.conf
I dont think i removed or deleted it by accident because i never installed DE in this installation of minimal.

Expand  

To update the Lima driver question ON or OFF
dmesg | grep lima 

[    7.913523] lima ff300000.gpu: gp - mali450 version major 0 minor 0
[    7.913612] lima ff300000.gpu: pp0 - mali450 version major 0 minor 0
[    7.913675] lima ff300000.gpu: pp1 - mali450 version major 0 minor 0
[    7.913731] lima ff300000.gpu: l2 cache 8K, 4-way, 64byte cache line, 128bit                                                                                                              external bus
[    7.913746] lima ff300000.gpu: l2 cache 64K, 4-way, 64byte cache line, 128bit                                                                                                              external bus
[    7.915008] lima ff300000.gpu: bus rate = 491520000
[    7.915046] lima ff300000.gpu: mod rate = 491520000
[    7.917641] [drm] Initialized lima 1.1.0 20191231 for ff300000.gpu on minor 1

 

0
jock

jock

Posted
  • Author
Posted
  On 5/12/2022 at 7:02 AM, MR01 said:

To update the Lima driver question ON or OFF
dmesg | grep lima 

[    7.913523] lima ff300000.gpu: gp - mali450 version major 0 minor 0
[    7.913612] lima ff300000.gpu: pp0 - mali450 version major 0 minor 0
[    7.913675] lima ff300000.gpu: pp1 - mali450 version major 0 minor 0
[    7.913731] lima ff300000.gpu: l2 cache 8K, 4-way, 64byte cache line, 128bit                                                                                                              external bus
[    7.913746] lima ff300000.gpu: l2 cache 64K, 4-way, 64byte cache line, 128bit                                                                                                              external bus
[    7.915008] lima ff300000.gpu: bus rate = 491520000
[    7.915046] lima ff300000.gpu: mod rate = 491520000
[    7.917641] [drm] Initialized lima 1.1.0 20191231 for ff300000.gpu on minor 1

 

Expand  

 

Lima driver for 3D is active and working pretty fine since a long time, the only reason it was disabled for X.org was the slower performances in desktop usage due to missing "optimizations" in modesetting X.org driver.

This causes buffers being moved back and forth and thus degraded performance but, as you confirm, 3D is enabled for X.org too.

 

For any other usage unrelated to X.org (including Wayland/Weston, Kodi, OpenGL games, ...) Lima driver and 3D acceleration have always been available.

 

1
cmuki

cmuki

Posted
Posted (edited)

Dear @jock,

 

Today I managed to buy a UART converter - sadly, these are the first rows of the boot log (copy-pasted the output from Putty window to a txt file):

DDR version 1.16 20190713
ID:0xFFF
In
DDR3
333MHz
Bus Width=32 Col=11 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=2048MB
ddrconfig:2
OUT

 

It seems that the RAM is, as Armbian was able to detect, 2 GB. Only this ddrconfig: 2 value is peculiar.

 

I've attached the whole output, but don't know if there is something else relevant, which is missing from it

 

Thank you once again for your support! If I can provide any further information, I'm available.

 

Best regards!

 

EDIT: Using the DDR Version I was able to find this comment from chess12 and there are three differences between our outputs :

1. Row=16 instead of 15

2. Size=4096

3. ddrconfig:3

 

 

boot log.txtFetching info...

Edited by cmuki
new information
0
jock

jock

Posted
  • Author
Posted

@cmuki

Assuming the boot you provided is from the original image, I think there is no extra questions to ask: if the ddrbin says that you have 2048 megabytes, that is so.

The ddrbin, which is the first piece of code that is executed at all and initializes the board DDR memory, is the most reliable source from this point of view.

 

Going on with the bootstrap phase, u-boot says the same: 

U-Boot 2017.09-gaa00306-201224-dirty #foxluo (Jan 19 2021 - 14:31:53 +0800)

PreSerial: 2, raw, 0xff130000
DRAM:  2 GiB

 

And obviously even the linux android kernel also detects 2 gigabytes of total RAM: 

[    0.000000] Memory: 1955884K/2064384K available (14910K kernel code, 2056K rwdata, 8884K rodata, 3968K init, 2806K bss, 75732K reserved, 32768K cma-reserved)

 

That's it, fake hardware specs; the manufacturer altered the Android image somehow to show fake specs and maybe something is wrong with the DDR chips too (are they have been reprinted? are they just fake chips or not really connected to the board? who knows...)

2
paradigman

paradigman

Posted
Posted

I had a problem with this wireless chip. Is this familiar to anyone? In one of the system messages I saw this as BCM 4334B1 / 6334. It can scan networks with the minimal image but cannot connect. Is there an overlay?

 

  Reveal hidden contents

 

0
MBB

MBB

Posted
Posted

I can't help answer this question directly as I haven't encountered this module before, nor the problem of one being discovered but not connecting.  That said, there are many different part numbers for what is essentially the same module.  As a general rule of thumb, look at the last two digits and compare to the Broadcom part numbers.  In this case, it would likely be a brcm4334 as discovered.  If it ends in 30, it would likely be a brcm4330.  Of course, that doesn't explain why it doesn't connect.  I'll defer to @jock or others that have more experience with these things...

0

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
 Share
Go to topic listing
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept