主题:[讨论] 共有69608人关注过本帖 |
---|
客人 |
1楼 |
[讨论] Post By:2018-1-3 19:30:00 [只看该作者]
请问ETA927连接3354主板使屏幕白屏是怎么回事? |
|
单帖管理 | 引用 | 回复 |
hzc |
2楼 信息 | 搜索 | 邮箱 |
加好友 发短信 员工 |
Post By:2018-1-4 9:28:00 [只看该作者]
你好,请问你是使用的系统是Linux还是WinCE呢?可以连接超级终端检查一下板卡的系统有没有启动,还有带线的连接是不是有接触不好的地方。 |
单帖管理 | 引用 | 回复 |
客人 |
3楼 |
Post By:2018-1-4 9:33:00 [只看该作者]
PID:00400002 TID:0 Texas Instruments Windows CE NAND X-Loader for SubArctic 335X Built Nov 30 2017 at 09:47:22 AM335x PG2.0 ZCZ Package 1G Hz. DRAM: 256MB DDR3 This XLDR BEFORE FMD_Init succeeded Retrieving EBOOT from flash memory ... Reading block 0x00000004 vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv. Reading block 0x00000005 vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv. Jumping to bootloader EBOOT @ 0x8FE00000 Microsoft Windows CE Bootloader Common Library Version 1.4 Built Nov 30 2017 09:45:56 INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0x8409 Texas Instruments Windows CE EBOOT for AM33x, Built Nov 30 2017 at 09:47:18 EBOOT Version 0.0.1, BSP BSP_WINCE_ARM_A8 02.30.00.01 ecc type:4 System ready! Preparing for download... INFO: Predownload.... FMD_Init: V2, Nov 30 2017 09:46:12 Checking bootloader blocks(0 - 1023) are marked as reserved FMD_Init: V2, Nov 30 2017 09:46:12 BLReadBootCfg done BOOT_CFG_SIGNATURE is different, read -1, expect 1111705159 WARN: Boot config wasn't found, using defaults INFO: SW3 boot setting: 0x13 IT IS A ESM3354 BOARD >>> Forcing cold boot (non-persistent registry and other data will be wiped) <<< +FindBMP FMD_Init: V2, Nov 30 2017 09:46:12 -FindBMP::800x480, BitCount=8, bfOffBits=1070, bfSize=385072 ShowBmp: Generic TFT LcdPdd_LCD_Initialize: 800*480 32bpp INFO: ESM335x is running in debug mode 5fab5ef4 ac8 -> f4 5e ab 5f c8 a 5fab5ef4 cc8 -> f4 5e ab 5f c8 c Hit [ENTER] to launch image or [SPACE] to enter configuration menu. Initiating image launch in 1 seconds... ->ReadFlashNK FMD_Init: V2, Nov 30 2017 09:46:12 Partition[0] is a A PART_RAMIMAGE: StartBlock=0x30, BlockSize=0x4e NK Image Loaded Launch Windows CE image by jumping to 0x80200000... Windows CE Kernel for ARM (Thumb Enabled) +OEMInit CPU CP15 Control Register = 0xc5387f CPU CP15 Auxiliary Control Register = 0x42 OEMInit: booting from power on reset OEMInit: BootReg=0x90a10040, content = 0x00410393 +OALTimerInit(1, 24000, 200) --- High Performance Frequecy is 24 MHz--- OALWatchdogInit is about to be called -OEMInit: NKForceCleanBoot OEMInit: NAND ECC Type = 4 -OEMInit PID:00400002 TID:00410002 ->OALCustomerSpecifiedPostInit PID:00400002 TID:00410002 InitializeCriticalSection(&g_oalNfcMutex) PID:00400002 TID:00410002 <-OALCustomerSpecifiedPostInit PID:00400002 TID:00510002 NANDDISK: DSK_Init Nov 30 2017 09:47:06 PID:00400002 TID:00510002 FMD_Init: V2, Nov 30 2017 09:46:12 PID:00400002 TID:00510002 GetNandDiskInfo: MBR => d_StartBlock = 0x24, d_TotalSize = 0x4720000 bytes, found at Block[0x24]. PID:00400002 TID:00510002 NANDDISK: di_total_sectors = 0x8e40, di_bytes_per_sect = 0x800 PID:00400002 TID:00510002 NANDDisk: Registry block status in Nand Reserved Partition PID:00400002 TID:00510002 NANDDisk: BootReserved = 1024 blocks, Available = 1024 blocks PID:00400002 TID:00510002 NANDDISK: DSK_Init returning 0xa2470480 PID:00400002 TID:00C60006 ->FlashPdd_Init PID:00400002 TID:00C60006 <-FlashPdd_Init: done 0xa2438190. PID:00400002 TID:00C60006 Rev 2.1, skip download CortexM3 PID:00400002 TID:00C60006 +WDT_Init PID:00400002 TID:00C60006 -WDT_Init: hDev = 0x1 PID:00400002 TID:00C60006 ->ISA_Init PID:00400002 TID:00C60006 ISAClass: GPMC registers map PA=0x50000000, UA=0x94a00000 PID:00400002 TID:00C60006 ISAClass: ISA memory map PA=0x09000000, UA=0x94b00000 PID:00400002 TID:00C60006 <-ISA_Init: done(0xaad41300) PID:00400002 TID:00C60006 +IOCTL_HAL_GET_MAC_ADDRESS PID:00400002 TID:00C60006 -IOCTL_HAL_GET_MAC_ADDRESS 1 PID:00400002 TID:00C60006 READ mac address from Boot args port 1 = 0xF4:0x5E:0xAB:0x5F:0xC8:0x0A PID:00400002 TID:00C60006 Cpsw3g_MiniportRegisterOneInterrupt 40 PID:00400002 TID:00C60006 Cpsw3g_MiniportRegisterOneInterrupt 93 PID:00400002 TID:00C60006 Cpsw3g_MiniportRegisterOneInterrupt 94 PID:00400002 TID:00C60006 Cpsw3g_MiniportRegisterOneInterrupt 43 PID:00400002 TID:00C60006 Cpsw3g_InitializeAdapter: mode=1, port=1, txCh=0, rxChMask=0x101, ActiveCpgmac=1 PID:00400002 TID:00C60006 START PORT 1 PID:00400002 TID:00C60006 +IOCTL_HAL_GET_MAC_ADDRESS PID:00400002 TID:00C60006 -IOCTL_HAL_GET_MAC_ADDRESS 1 PID:00400002 TID:00C60006 READ mac address from Boot args port 2 = 0xF4:0x5E:0xAB:0x5F:0xC8:0x0C PID:00400002 TID:00C60006 Cpsw3g_MiniportRegisterOneInterrupt 40 PID:00400002 TID:00C60006 Cpsw3g_MiniportRegisterOneInterrupt 93 PID:00400002 TID:00C60006 Cpsw3g_MiniportRegisterOneInterrupt 94 PID:00400002 TID:00C60006 Cpsw3g_MiniportRegisterOneInterrupt 43 PID:00400002 TID:00C60006 Cpsw3g_InitializeAdapter: mode=1, port=2, txCh=1, rxChMask=0x202, ActiveCpgmac=2 PID:00400002 TID:00C60006 START PORT 2 PID:00400002 TID:00C60006 +PIO_Init PID:00400002 TID:00C60006 -Audio_Init::Quit audio driver installation PID:00400002 TID:00C60006 SDHC +Init PID:00400002 TID:00C60006 SDHC host controller initialize: m_fastPathSDIO:1 m_fastPathSDMEM:0 PID:00400002 TID:03500002 _cpsw3g_find_phy_driver: phy_id = 508144 PID:00400002 TID:03500002 _cpsw3g_find_phy_driver: phy_id = 508144 PID:00400002 TID:00C60006 TchPdd_Init+ PID:00400002 TID:00C60006 BSPTouchHwInit: GT911_1060 PID:00400002 TID:00C60006 BSPTouchHwInit: GT911 config => 1024x600, 10-point, int_trigger_type 1 PID:00400002 TID:00C60006 TchPdd_Init- PID:00400002 TID:00C60006 +GPIO_Backlight::Initialize(Drivers\Active\34) PID:00400002 TID:00C60006 +SPI_Init V2.0(Drivers\Active\41, 0x00000000) PID:00400002 TID:00C60006 +HWInit: COM2 Initialization succeeded PID:00400002 TID:00C60006 +HWInit: COM3 Initialization succeeded PID:00400002 TID:00C60006 +HWInit: COM4 Initialization succeeded PID:00400002 TID:00C60006 +HWInit: COM5 Initialization succeeded PID:00400002 TID:00C60006 +HWInit: COM6 Initialization succeeded PID:00400002 TID:00C60006 CAN_Init + PID:00400002 TID:00C60006 GetCanHWObj: d_can1 PhyAddr=0x481d0000 Irq=55 PID:00400002 TID:00C60006 DCan_Init: CAN clock = 24000000 Hz, default bit-rate = 500000 PID:00400002 TID:00C60006 DcanSetBittiming: setting BRPE=0x0000 BTR=0x0545 PID:00400002 TID:00C60006 AM335x D_CAN v1.0 CAN1 hardware initialization done PID:00400002 TID:00C60006 CAN_Init - hDev=0xaba00000 PID:00400002 TID:00C60006 CAN_Init + PID:00400002 TID:00C60006 GetCanHWObj: d_can0 PhyAddr=0x481cc000 Irq=52 PID:00400002 TID:00C60006 DCan_Init: CAN clock = 24000000 Hz, default bit-rate = 500000 PID:00400002 TID:00C60006 DcanSetBittiming: setting BRPE=0x0000 BTR=0x0545 PID:00400002 TID:00C60006 AM335x D_CAN v1.0 CAN2 hardware initialization done PID:00400002 TID:00C60006 CAN_Init - hDev=0xaba40000 PID:00400002 TID:00C60006 CAM3xxOTG::Init DEVCTL 80 PID:00400002 TID:00C60006 UsbPowerModule: 2 DEVCTL = 0x00000099 PID:00400002 TID:00C60006 Hold on usb host reset... PID:00400002 TID:00C60006 +PWM1_Init v2.0(Drivers\Active\54) PID:00400002 TID:00C60006 +PWM2_Init v2.0(Drivers\Active\55) PID:00400002 TID:00C60006 +PWM3_Init v2.0(Drivers\Active\56) PID:00400002 TID:00C60006 +PWM4_Init v2.0(Drivers\Active\57) PID:00400002 TID:00C60006 +PWM5_Init v2.0(Drivers\Active\58) PID:00400002 TID:00C60006 +I2C_Init(rc = 0xa2457b40) PID:00400002 TID:00C60006 +IRQ1_Init: GpioId=19, SysIntr=42 PID:00400002 TID:00C60006 +IRQ2_Init: GpioId=20, SysIntr=43 PID:00400002 TID:00C60006 +IRIG-B Init PID:00400002 TID:01E10016 LcdPdd_LCD_Initialize: 800*480 32bpp PID:00400002 TID:01E10016 KeybdDriverInitializeEx: Layout Manager successfully initialized to 1 PID:00400002 TID:053500FE Release usb host reset PID:00400002 TID:05BC0006 UsbInterruptThread:Device connected IntrUsbValue = 0x10 PID:00400002 TID:05C50006 CHW::AllocateHostEndPoint: allocated EP0_BIDIR, TYEP_CONTROL, FIFO 64 PID:00400002 TID:06B70012 CHW::AllocateHostEndPoint: allocated EP2_IN, TYPE_INTERRUPT, FIFO 512, MaxSize 1 PID:050C004A TID:07DA000E Explorer(V2.0) taskbar thread started. PID:00400002 TID:05900002 NDISPWR:: Found adapter [CPSW3G2] PID:00400002 TID:05900002 NDISPWR:: Found adapter [CPSW3G1] PID:054C00FE TID:053500FE ESM335x Emtronix Built at Nov 30 2017 09:47:24 Adaptation performed by Emtronix (c) PID:054C00FE TID:053500FE eth0: CPSW3G1 PID:054C00FE TID:053500FE eth1: CPSW3G2 PID:054C00FE TID:053500FE ESM335x Debug Mode PID:054C00FE TID:053500FE eth0: CPSW3G1 PID:054C00FE TID:053500FE IPAddr: 192.168.201.220 PID:054C00FE TID:053500FE SunnetMask: 255.255.255.0 PID:054C00FE TID:053500FE Gateway: 192.168.201.19 PID:054C00FE TID:053500FE DHCP Disable PID:054C00FE TID:053500FE IP Parameters aren't changed, need not set CPSW3G1 PID:054C00FE TID:053500FE eth1: CPSW3G2 PID:054C00FE TID:053500FE IPAddr: 192.168.202.220 PID:054C00FE TID:053500FE SunnetMask: 255.255.255.0 PID:054C00FE TID:053500FE Gateway: 192.168.202.19 PID:054C00FE TID:053500FE DHCP Disable PID:054C00FE TID:053500FE IP Parameters aren't changed, need not set CPSW3G2 PID:054C00FE TID:053500FE SetMemoryDivision : 12 PID:00400002 TID:053500FE IOCTL_HAL_WSTARTUP_END: wstartup is ended! WINce系统,上面是打印信息。线连接正常。 |
|
单帖管理 | 引用 | 回复 |
lqk |
4楼 信息 | 搜索 | 邮箱 |
加好友 发短信 |
Post By:2018-1-4 9:48:00 [只看该作者]
从系统启动信息来看,一切设置正常。 请问还有没有其它屏或主板,交叉测试一下,以判断问题。 |
单帖管理 | 引用 | 回复 |
客人 |
5楼 |
Post By:2018-1-4 10:33:00 [只看该作者]
我现在的核心板是按RGB接口,电容触摸,屏配的是ETA927拿的货。拿其他的核心板试了,但是我这里有好几块的3354的主板,其中有支持电容触摸的,也有支持电阻触摸的,有LVDS接口的,也有rgb接口的。 问题一:我该如何从核心板外观区分哪块是能够配型号为ETA927RGB接口电容触摸屏? 问题二:我刚刚试了其中一块核心板,用的底板是ESMARC V2.3 ,屏幕是可以用的,但是触摸没反应,但是我不确定此核心板是否支持电容触摸。 (之前听说是看核心板上的U10和u4,请英创工程们帮忙,谢谢) |
|
单帖管理 | 引用 | 回复 |
客人 |
6楼 |
Post By:2018-1-4 10:56:00 [只看该作者]
刚刚又测试了一下,板子在我以前买的底板ESMARC V2.3上测试OK,触摸也没问题,但是在底板ESMARC EVB V7.0上就是白屏,没反应,请问是底板的上某个跳线的问题吗?我现在要用到的是V7.0底板上测试通过才行?还麻烦解答一下,谢谢,包括刚刚的两个问题,谢谢了 |
|
单帖管理 | 引用 | 回复 |
cx |
7楼 |
Post By:2018-1-4 13:32:00 [只看该作者]
若在底板ESMARC V2.3上测试OK,在底板ESMARC EVB V7.0上白屏怀疑是显示屏带线与底板之间没有插好,麻烦再检查一下。 接电容触摸屏没有跳线器的选择。 |
|
单帖管理 | 引用 | 回复 |
lqk |
8楼 信息 | 搜索 | 邮箱 |
加好友 发短信 |
Post By:2018-1-4 14:33:00 [只看该作者]
ESM335x型号区分方法请参考文章:http://www.emtronix.com/article/article20181104.html [此贴子已经被作者于2018-1-4 14:34:00编辑过]
|
单帖管理 | 引用 | 回复 |
客人 |
9楼 |
Post By:2018-1-4 15:40:00 [只看该作者]
已经检查过了,更换了屏线,在底板V7.0上测试还是白屏,怀疑是不是CN16座子出现了问题 |
|
单帖管理 | 引用 | 回复 |
客人 |
10楼 |
Post By:2018-1-4 15:41:00 [只看该作者]
行,谢谢刘工。现在知道怎么区分了。 |
|
单帖管理 | 引用 | 回复 |
客人 |
11楼 |
Post By:2018-1-4 17:19:00 [只看该作者]
看看底板背面,LCD接口下,有没有器件烧坏的情况,再看看扁平线是否有损坏 |
|
单帖管理 | 引用 | 回复 |
gmh1314 |
12楼 信息 | 搜索 | 邮箱 |
加好友 发短信 |
回复:(客人(182.139.*.*))看看底板背面,LCD接口下... Post By:2018-1-5 10:22:00 [只看该作者]
图1 图2 图3 图1是底板型号ESMARC V2.3 的CN16背面,图2、3是底板型号ESMARC EVB V7.0的CN16背面。现在用3354主板分别连接三块底板与显示屏ETA927电容触摸屏时,图一可以正常使用,图2是白屏,图2 是黑屏。图1 是L1、L2焊接了,图2 L1、L2是0欧姆电阻,图3L1、L2是未焊接。谢谢。 |
单帖管理 | 引用 | 回复 |
zxw |
13楼 |
Post By:2018-1-5 10:36:00 [只看该作者]
你好!图3的底板,是没有使用RGB接口,而是LVDS/HDMI显示接口的配置,所以这张板子不能连接RGB接口的屏了。 要接RGB接口,需要使用图1、图2的板子。 |
|
单帖管理 | 引用 | 回复 |
客人 |
14楼 |
回复:(zxw(182.139.*.*))你好!图3的底板,是没有使... Post By:2018-1-5 10:40:00 [只看该作者]
但是图2是白屏,只有图1才是有用 |
|
单帖管理 | 引用 | 回复 |
zxw |
15楼 |
Post By:2018-1-5 11:03:00 [只看该作者]
如果是图2白屏,最大可能则是没有RGB信号。你看看底板的版本,同时再看看底板背面的白框内“TTL_RGB”相关的电阻是否都焊接。 |
|
单帖管理 | 引用 | 回复 |
gmh1314 |
16楼 信息 | 搜索 | 邮箱 |
加好友 发短信 |
回复:(zxw(182.139.*.*))如果是图2白屏,最大可能则... Post By:2018-1-5 11:48:00 [只看该作者]
未焊接 |
单帖管理 | 引用 | 回复 |