[U-Boot] LVDS dual channel support on A10,A20,A31s mods.

[far5893]

Hi,
i make a little changes to
lcdc.h and sunxi_diplay.h to make dual channel LVDS interface working :

-lcdc.h

#define SUNXI_LCDC_TCON0_LVDS_INTF_CH(n)    ((n) << 30) /* LVDS Dual channel 
0=single 1=dual*/

and in

-sunxi_diplay.h (line 830).

#ifdef CONFIG_VIDEO_LCD_IF_LVDS
    if (mode->yres <= 768) ch=0; /*Single channel*/
    if ((mode->yres <= 800) & (sunxi_display.depth == 18)) ch=0; /*Single 
channel*/
    if ((mode->yres > 768) & (sunxi_display.depth == 24)) ch=1; /*Dual channel*/

    if(ch) printf ("Dual Channel Mode\n");
    else   printf ("Single Channel Mode\n");


    writel(SUNXI_LCDC_TCON0_LVDS_INTF_BITWIDTH(val) |
       SUNXI_LCDC_TCON0_LVDS_CLK_SEL_TCON0 |
   SUNXI_LCDC_TCON0_LVDS_INTF_CH(ch), >tcon0_lvds_intf);
#endif

there are another patch from plaes sended but nothing happen.

https://lists.denx.de/pipermail/u-boot/2017-March/284805.html

These mods are  tested  on cubieboard1 and 2 , banana pi M2 (A31s) and dual 
channel lcd  displays
i'm not a software developer so patching tree and submit is out from my 
knowledge


Thank
Miky




___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot

[U-Boot] [LVDS dual channel] TCON0_LVDS_IF_REG seem have undocumented bit 30 ?

[far5893]

I try to read BSP code  for enabling dual channel LVDS (for more than 768 
Vertical lines),in BSP code :



#define LCDC_LVDS_OFF (0x084) /* LVDS registers offset */


LCDC_WUINT32(sel, LCDC_LVDS_OFF,(info->lcd_lvds_ch << 30)
| (0 << 29) | (0 << 28)
| (info->lcd_lvds_mode << 27)
|(info->lcd_lvds_bitwidth << 26) | (0 << 23));


there is a lcd_lvds_ch parameter from fex file that set bit30

but in documentation only bit 31 28 27 26 23  of TCON0_LVDS_IF_REG(0x084) are 
documented,

i'm reading wrong documentation or is really undocumented ?

I'm trying to enable lvds dual channel on A10/A20 SOC.




Thanks

___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot

[U-Boot] Someone expert in lvds timings ?

[far5893]

I'm trying to generate u-boot timings for 
http://www.notebook-lcd.ru/pdf/QD17EL07_REV_11.pdf page 11.

i try 
(x:640,y:1024,depth:24,pclk_khz:54000,le:45,ri:200,up:22,lo:22,hs:1,vs:1,sync:3,vmode:0)
 LCD panel timing details

does someone have experience in writing such timings ?

The panel is dual channel but i create an Y cable to feed two channels from only one supported by u-boot(but i try one channel 
only cable).


My scope is to validate my setup for try to add dual lvds channel support on 
u-boot on A10(cubieboard1).


Thanks
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/listinfo/u-boot

[U-Boot] Allwinner A33 MIPI DSI Support.

[far5893]

I have a new  fresh Q8 A33  tablet but different from previous two it
have native MIPI DSI interface, there is working in progress to support MIPI 
DSI interface in
u-boot ?

lcd_fex

[lcd0_para]
lcd_used = 1
lcd_driver_name = "tm1280X800"
lcd_if = 4
lcd_x = 800
lcd_y = 1280
lcd_width = 120
lcd_height = 160
lcd_dclk_freq = 78
lcd_pwm_used = 1
lcd_pwm_ch = 0
lcd_pwm_freq = 5
lcd_pwm_pol = 1
lcd_hbp = 96
lcd_ht = 961
lcd_hspw = 48
lcd_vbp = 12
lcd_vt = 1322
lcd_vspw = 4
lcd_dsi_if = 0
lcd_dsi_lane = 4
lcd_dsi_format = 0
lcd_dsi_te = 0
lcd_lvds_if = 0
lcd_lvds_colordepth = 0
lcd_lvds_mode = 0
lcd_frm = 1
lcd_hv_clk_phase = 0
lcd_hv_sync_polarity = 0
lcd_gamma_en = 0
lcd_bright_curve_en = 0
lcd_cmap_en = 0
deu_mode = 0
lcdgamma4iep = 22
smart_color = 90
lcd_bl_en = port:PH06<1><0><1>
lcd_power = port:power2<1><0><1>
lcd_power_1 = "axp22_eldo1"
lcd_gpio_0 = port:PH07<1><0><1>



Thank
silviop

___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

[U-Boot] arch/arm/mach-sunxi/dram_sun8i_a33.c and 1Gb detect as 512Mb on A33.

[far5893]

I have a tablet with 1Gb of ram (two chips),but not u-boot neither kernel 
detect it (only 512Mb).

Does i need to change something in arch/arm/mach-sunxi/dram_sun8i_a33.c ?

i posta alettronica found this struct in sunxi_dram_init(void) function:

struct dram_para para = {
.cs1 = 0,
.bank = 1,
.rank = 1,
.rows = 15,
.bus_width = 16,
.page_size = 2048,
};



Thanks
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

[U-Boot] A33 tablet u-boot not boot (fel +sdbreakout).

[far5893]

Hi,
I'm trying to boot an A33 tablet , i buy sdcard breakout and enable sd card 
uart in .config
using (UART0 on MicroSD breakout board).

I used q8_a33_tablet_1024x600_defconfig as base.

I read  serial port output from BOOT0 and   finally "eraly jump fel" message so 
i'm sure sdcard breakout work.

and from my linux 16.04 command line


u-boot-2016.09# sunxi-fel -v ver
AWUSBFEX soc=1667(A33) 0001 ver=0001 44 08 scratchpad=7e00  


u-boot-2016.09# sunxi-fel -v uboot u-boot-sunxi-with-spl.bin
Stack pointers: sp_irq=0x2000, sp=0x5E08
MMU is not enabled by BROM
=> Executing the SPL... done.
libusb usb_bulk_send error -7

u-boot-2016.09#

Nothing happen!!

My tablet not boot direct from  sdcard obviously(only installed android work), 
what can do for deeper debug  ?

I see that there is a early uart debug option in .config but ask parameters 
that i don't know.

Thanks




___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Re: [U-Boot] Sdcard boot for a generic allwinner q8 clone A33 tablet not work.

[far5893]

Hans de Goede wrote:

Hi,

On 09-09-16 14:10, far5893 wrote:

Hi,
i'm trying to boot a classic A33 q8 clone with uboot copied in sdcard
but nothing happen (not backlight on)

dd if=u-boot-sunxi-with-spl.bin of=/dev/sdb bs=1024 seek=8 on the partitioned 
sdcard for reference


In my experience the A33 can be a bit picky wrt which sdcards
it will boot from. Sometimes simply doing the dd again will
help, sometimes using a different sdcard will help.


I try Sandisk ultra 32Gb,Samsung EVO 32Gb, adata 16GB no difference but ok with A13 (and on a33 original android they are 
correctly detected), i suppose that i can only wait developers make more test with more hardware, if i can help  i'm here.


Now i'm on 2016.09-rc2.

Thanks

___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

[U-Boot] Sdcard boot for a generic allwinner q8 clone A33 tablet not work.

[far5893]

Hi,
i'm trying to boot a classic A33 q8 clone with uboot copied in sdcard
but nothing happen (not backlight on)

dd if=u-boot-sunxi-with-spl.bin of=/dev/sdb bs=1024 seek=8 on the partitioned 
sdcard for reference

if i compile with configuration for  A13 based tablet   on A13 based tablet  it 
work like charm,
so i suppose i'm not in wrong in my setup, how can i debug  ?

I dont have sd/usart adapter so i cannot boot from fel, there is a way
to make blink backlight to understand if it is working and is an lcd problem ?

On original android it work perfectly.

I attach original fex and .configure for your references.

Thank



#
# Automatically generated file; DO NOT EDIT.
# U-Boot 2016.09-rc2 Configuration
#
CONFIG_CREATE_ARCH_SYMLINK=y
# CONFIG_ARC is not set
CONFIG_ARM=y
# CONFIG_AVR32 is not set
# CONFIG_BLACKFIN is not set
# CONFIG_M68K is not set
# CONFIG_MICROBLAZE is not set
# CONFIG_MIPS is not set
# CONFIG_NDS32 is not set
# CONFIG_NIOS2 is not set
# CONFIG_OPENRISC is not set
# CONFIG_PPC is not set
# CONFIG_SANDBOX is not set
# CONFIG_SH is not set
# CONFIG_SPARC is not set
# CONFIG_X86 is not set
# CONFIG_XTENSA is not set
CONFIG_SYS_ARCH="arm"
CONFIG_SYS_CPU="armv7"
CONFIG_SYS_SOC="sunxi"
CONFIG_SYS_BOARD="sunxi"
CONFIG_SYS_CONFIG_NAME="sun8i"

#
# ARM architecture
#
CONFIG_HAS_VBAR=y
CONFIG_HAS_THUMB2=y
CONFIG_CPU_V7=y
CONFIG_SYS_ARM_ARCH=7
# CONFIG_SEMIHOSTING is not set
# CONFIG_SYS_L2CACHE_OFF is not set
# CONFIG_ENABLE_ARM_SOC_BOOT0_HOOK is not set
# CONFIG_ARCH_AT91 is not set
# CONFIG_TARGET_EDB93XX is not set
# CONFIG_TARGET_VCMA9 is not set
# CONFIG_TARGET_SMDK2410 is not set
# CONFIG_TARGET_ASPENITE is not set
# CONFIG_TARGET_GPLUGD is not set
# CONFIG_ARCH_DAVINCI is not set
# CONFIG_KIRKWOOD is not set
# CONFIG_ARCH_MVEBU is not set
# CONFIG_TARGET_DEVKIT3250 is not set
# CONFIG_TARGET_WORK_92105 is not set
# CONFIG_TARGET_MX25PDK is not set
# CONFIG_TARGET_ZMX25 is not set
# CONFIG_TARGET_APF27 is not set
# CONFIG_TARGET_APX4DEVKIT is not set
# CONFIG_TARGET_XFI3 is not set
# CONFIG_TARGET_M28EVK is not set
# CONFIG_TARGET_MX23EVK is not set
# CONFIG_TARGET_MX28EVK is not set
# CONFIG_TARGET_MX23_OLINUXINO is not set
# CONFIG_TARGET_BG0900 is not set
# CONFIG_TARGET_SANSA_FUZE_PLUS is not set
# CONFIG_TARGET_SC_SPS_1 is not set
# CONFIG_ORION5X is not set
# CONFIG_TARGET_SPEAR300 is not set
# CONFIG_TARGET_SPEAR310 is not set
# CONFIG_TARGET_SPEAR320 is not set
# CONFIG_TARGET_SPEAR600 is not set
# CONFIG_TARGET_STV0991 is not set
# CONFIG_TARGET_X600 is not set
# CONFIG_TARGET_IMX31_PHYCORE is not set
# CONFIG_TARGET_MX31ADS is not set
# CONFIG_TARGET_MX31PDK is not set
# CONFIG_TARGET_WOODBURN is not set
# CONFIG_TARGET_WOODBURN_SD is not set
# CONFIG_TARGET_FLEA3 is not set
# CONFIG_TARGET_MX35PDK is not set
# CONFIG_ARCH_BCM283X is not set
# CONFIG_TARGET_VEXPRESS_CA15_TC2 is not set
# CONFIG_TARGET_VEXPRESS_CA5X2 is not set
# CONFIG_TARGET_VEXPRESS_CA9X4 is not set
# CONFIG_TARGET_BRXRE1 is not set
# CONFIG_TARGET_BRPPT1 is not set
# CONFIG_TARGET_CM_T335 is not set
# CONFIG_TARGET_PEPPER is not set
# CONFIG_TARGET_AM335X_IGEP0033 is not set
# CONFIG_TARGET_PCM051 is not set
# CONFIG_TARGET_DRACO is not set
# CONFIG_TARGET_THUBAN is not set
# CONFIG_TARGET_RASTABAN is not set
# CONFIG_TARGET_ETAMIN is not set
# CONFIG_TARGET_PXM2 is not set
# CONFIG_TARGET_RUT is not set
# CONFIG_TARGET_PENGWYN is not set
# CONFIG_TARGET_AM335X_BALTOS is not set
# CONFIG_TARGET_AM335X_EVM is not set
# CONFIG_TARGET_AM335X_SHC is not set
# CONFIG_TARGET_AM335X_SL50 is not set
# CONFIG_TARGET_BAV335X is not set
# CONFIG_TARGET_TI814X_EVM is not set
# CONFIG_TARGET_TI816X_EVM is not set
# CONFIG_TARGET_BCM23550_W1D is not set
# CONFIG_TARGET_BCM28155_AP is not set
# CONFIG_TARGET_BCMCYGNUS is not set
# CONFIG_TARGET_BCMNSP is not set
# CONFIG_ARCH_EXYNOS is not set
# CONFIG_ARCH_S5PC1XX is not set
# CONFIG_ARCH_HIGHBANK is not set
# CONFIG_ARCH_INTEGRATOR is not set
# CONFIG_ARCH_KEYSTONE is not set
# CONFIG_ARCH_MESON is not set
# CONFIG_ARCH_MX7 is not set
# CONFIG_ARCH_MX6 is not set
# CONFIG_ARCH_MX5 is not set
# CONFIG_TARGET_M53EVK is not set
# CONFIG_TARGET_MX51EVK is not set
# CONFIG_TARGET_MX53ARD is not set
# CONFIG_TARGET_MX53EVK is not set
# CONFIG_TARGET_MX53LOCO is not set
# CONFIG_TARGET_MX53SMD is not set
# CONFIG_OMAP34XX is not set
# CONFIG_OMAP44XX is not set
# CONFIG_OMAP54XX is not set
# CONFIG_AM43XX is not set
# CONFIG_ARCH_RMOBILE is not set
# CONFIG_TARGET_S32V234EVB is not set
# CONFIG_ARCH_SNAPDRAGON is not set
# CONFIG_ARCH_SOCFPGA is not set
# CONFIG_TARGET_CM_T43 is not set
CONFIG_ARCH_SUNXI=y
# CONFIG_TARGET_TS4800 is not set
# CONFIG_TARGET_VF610TWR is not set
# CONFIG_TARGET_COLIBRI_VF is not set
# CONFIG_TARGET_PCM052 is not set
# CONFIG_ARCH_ZYNQ is not set
# CONFIG_ARCH_ZYNQMP is not set
# CONFIG_TEGRA is not set
# CONFIG_TARGET_VEXPRESS64_AEMV8A is not set
# CONFIG_TARGET_VEXPRESS64_BASE_FVP is not set
# CONFIG_TARGET_VEXPRESS64_BASE_FVP_DRAM is not set
# 

[U-Boot] U boot 2016 rc2 in a Q8 A13 tablet not recognize keyboard.

[far5893]

2016 rc2 version compiled against q8 A13 tablet configuration.

SD boot.


Usb detect give: failed,-96

error when a keyboard is connected.

But recognize mass storage (an empty key memory).


IBM Usb Keyboard model SK-8809-2D full working with original android.



Silviop
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot