View Single Post
Old 06-12-2019, 05:48 PM   #222
JasonACT
Away on leave
 
Join Date: Apr 2019
Location: ACT
Posts: 1,732
Tech Writer: Recognition for the technical writers of AFF - Issue reason: Outstanding work on the FG ICC issues. Technical Contributor: For members who share their technical expertise. - Issue reason: The insane amount of work he has put into the Falcon FG ICC is unbelievable. He has shared everything he has done and made a great deal of it available to us all. He has definitely helped a great deal of us with no personal gains to himself. 
Default Re: FORD technical service bulletin : ICC touch screen display

I admit it, and I do feel a bit silly, but I had ignored CN9 near the video input because it's unpopulated and I had assumed (<--that word!) it was for interfacing a DVD player which they never used... Lots of pins there that I don't know what they do (after taking a good look today). Pin 6 though, that's a real eye opener. I'll make 2 posts, this one is what my microcontroller makes of the working board. The next post will be what the broken board is doing...

Working board (Ready and *** is my output, *** happens when 1 second passes without anything coming from pin 6):

Ready

***

***


QNX/Neutrino IPL for MCIMX31 SWSA FDM
NAND ID: 2C B1 80 55 02
Reading startup header from NAND at 1 Mb
Using NAND 4-bit ECC
Copying pages ..4-bit ECC error block:page 0x0008:26 status 0xE8
.4-bit ECC error block:page 0x0008:3A status 0xE8
....4-bit ECC error block:page 0x0009:3C status 0xE8
.4-bit ECC error block:page 0x000A:07 status 0xE8
.4-bit ECC error block:page 0x000A:15 status 0xE8
..4-bit ECC error block:page 0x000A:3B status 0xE8
...4-bit ECC error block:page 0x000B:22 status 0xE8
.4-bit ECC error block:page 0x000B:39 status 0xE8
.4-bit ECC error block:page 0x000C:0F status 0xE8
.4-bit ECC error block:page 0x000C:15 status 0xE8
..4-bit ECC error block:page 0x000C:34 status 0xE8
.4-bit ECC error block:page 0x000D:05 status 0xE8
4-bit ECC error block:page 0x000D:07 status 0xE8
4-bit ECC error block:page 0x000D:09 status 0xE8
.4-bit ECC error block:page 0x000D:13 status 0xE8
4-bit ECC error block:page 0x000D:15 status 0xE8
...4-bit ECC error block:page 0x000E:05 status 0xE8
....4-bit ECC error block:page 0x000F:0B status 0xE8
.4-bit ECC error block:page 0x000F:1C status 0xE8
........4-bit ECC error block:page 0x0011:12 status 0xE8
.4-bit ECC error block:page 0x0011:28 status 0xE8
.4-bit ECC error block:page 0x0011:37 status 0xE8
..4-bit ECC error block:page 0x0012:12 status 0xE8
4-bit ECC error block:page 0x0012:19 status 0xE8
.4-bit ECC error block:page 0x0012:23 status 0xE8
.4-bit ECC error block:page 0x0012:39 status 0xE8
.4-bit ECC error block:page 0x0013:05 status 0xE8
4-bit ECC error block:page 0x0013:08 status 0xE8
.4-bit ECC error block:page 0x0013:1F status 0xE8
.4-bit ECC error block:page 0x0013:24 status 0xE8
.4-bit ECC error block:page 0x0013:3B status 0xE8
.4-bit ECC error block:page 0x0014:07 status 0xE8
....4-bit ECC error block:page 0x0015:0B status 0xE8
.....4-bit ECC error block:page 0x0016:16 status 0xE8
.4-bit ECC error block:page 0x0016:25 status 0xE8
.4-bit ECC error block:page 0x0016:31 status 0xE8
...4-bit ECC error block:page 0x0017:28 status 0xE8
.4-bit ECC error block:page 0x0017:3D status 0xE8
..4-bit ECC error block:page 0x0018:15 status 0xE8
....4-bit ECC error block:page 0x0019:1A status 0xE8
.4-bit ECC error block:page 0x0019:25 status 0xE8
......4-bit ECC error block:page 0x001B:03 status 0xE8
4-bit ECC error block:page 0x001B:08 status 0xE8
...4-bit ECC error block:page 0x001B:3D status 0xE8
.4-bit ECC error block:page 0x001C:0D status 0xE8
........4-bit ECC error block:page 0x001E:0A status 0xE8
..4-bit ECC error block:page 0x001E:21 status 0xE8
4-bit ECC error block:page 0x001E:2C status 0xE8
..4-bit ECC error block:page 0x001F:0C status 0xE8
.4-bit ECC error block:page 0x001F:1F status 0xE8
.4-bit ECC error block:page 0x001F:25 status 0xE8
.4-bit ECC error block:page 0x001F:3D status 0xE8
....4-bit ECC error block:page 0x0020:3A status 0xE8
..4-bit ECC error block:page 0x0021:12 status 0xE8


Peripheral clock source = 400000000 ipg_clk
Peripheral clock = 66666666 PDR0 = 0xff850a50

***

***

[36m Welcome to SWSAs FDM [m


***
Starting etfs driver...
fs-etfs-swsa_2048: NAND ID: 0x2C B1 80 55 82

***

***
chmod: changing permission of /fs : No such file or directory
Starting USB driver on USB OTG...
Interval is set to 2000ms. Board version = 3.500000.

253445
http://subversion.swsa.com.au/repos/...ace_iMX31/core

---- SWSA Binaries and Libraries (Environment) --
------------------- SWSA Media Player -------------------
---- HMI (Environment) --
Starting [32;1mpower[m
Starting [32;1mio[m
Starting [32;1mqnx_binaries_and_libraries[m
CRITICAL pin_iomuxe[ 2]powerManagerThread 0 . 00000000application_power.c0@s184: Ham: :S tPaorwteerd :m a(n5282947170a)g
e0r. 0n13999860osStarting [32;1mswsa_binaries_and_libraries[m
t: rHam: uLnongi ntgi m(e/dev/swsa_pmms)t.a mWpa isttianrgt.e.d.:
1970/01/01 00:00:05:296947030
0.087999120s: Ham: Creating guardian
0.103998960s: Ham: Dumper Died -1
0.105998940s: Ham: New Dumper Pid 372762
0.124998750s: Ham: Attach request from Guardian Pid 372764
Creating SDMA Infrastructure...
CRITICAL usb-fault[ 4]powerManagerThread application_power.c@184 : Power manager not ruCnRnIiTnIgC A(L/dev/swsa_pmm )wm8580a-co.[ W4a]ipowerManagerThreadt i n gapplication_power.c.@.184.
: Power manager not running (/dev/swsa_pmm). Waiting...
# init_usb_fault_interrupt
mo nmiotnoirt odevc-sermxr[ devc-sermx2[] ApiPowerRun2 ] ApiPowerRun application_power.c @ 128application_power.c @ 128: E:n tEenrtienrgi
ng
mo nmiotnoirt odevc-sermxr[ devc-sermx2[] ApiPowerRun2 ] ApiPowerRun application_power.c @ 136application_power.c @ 136: E:x iEtxiintgi
ng
mo nmiotnoirt odevc-sermxr[ devc-sermx3[] drv_pmd_connect3 ] drv_pmd_connect application_power.c @ 483application_power.c @ 483: E:nt eErnitnegr
i n gD
E B UDGE1B Udevc-sermxG[1 3devc-sermx][drv_pmd_connect 3 ] drv_pmd_connectapplication_power.c @ 487 application_power.c @:487 a t:t aactht atcoh Ptoow ePro wMearn aMgaenra gpeart hp a't/dev/swsa_pmm/ser1h'
'/dev/swsa_pmm/ser3'
DE B UDGE2B Udevc-sermxG[2 3devc-sermx][drv_pmd_connect 3 ] drv_pmd_connectapplication_power.c @ 509 application_power.c @:509 ' /dev/swsa_pmm/ser1:' 'i/dev/swsa_pmm/ser3s' niosw noopwe no poennc eo
n cmeo
n imtoonri tdevc-sermxo[r 3devc-sermx][drv_pmd_connect 3 ] drv_pmd_connectapplication_power.c @ 512 application_power.c @:512 E x:i tEixnigt
i nmgo
n imtoonri tdevc-sermxo[r 3devc-sermx][drv_pmd_init 3 ] drv_pmd_initapplication_power.c @ 257 application_power.c @:257 E n:t eErnitnegr
i n g
U S E RU Sdevc-sermxE[R 3devc-sermx][drv_pmd_init 3 ] drv_pmd_initapplication_power.c @ 290 application_power.c @:290 R e:g iRsetgeirsitnegr iwnigt hw iPtohw ePro wMeord eM oMdaen aMgaenra g(erC O(ICDO:I D1073741856:, 1073741831E,v eEnvte:n t0:x 40,x 4t,i mteiomueto:u t10000
10000)
mo nmitoonri tdevc-sermxo[r 3devc-sermx][drv_pmd_init 3 ] drv_pmd_initapplication_power.c @ 310 application_power.c @:310 E x:i tEixnigt
i n gD
E B UDGE2B Udevc-sermxG[2 3devc-sermx][powerManagerThread 3 ] powerManagerThreadapplication_power.c @ 205 application_power.c @:205 I n:i tIinailt iPaolw ePro wMeord eM o-d eA c-t iAvcet
i v eD
E B UDGE2B Udevc-sermxG[2 3devc-sermx][power_init_callback 3 ] power_init_callbackpowerManager.c @ 135 powerManager.c @:135 S t:a rStteadr tiend aicnt iavcet imvoed em.o
de.

***
Starting [32;1mbluetooth[m
monitor devc-sermx[ 2]ApiPowerRun application_power.c@128 : Entering
monitor devc-sermx[ 2]ApiPowerRun application_power.c@136 : Exiting
monitor devc-sermx[Starting [32;1mmedia_player[m
3]drv_pmd_connect application_power.c@483 : Entering
DEBUG1 devc-sermx[ 3]drv_pmd_connect application_power.c@487 : attach to Power Manager path '/dev/swsa_pmm/ser2'
DEBUG2 devc-sermx[ 3]drv_pmd_connect application_power.c@509 : '/dev/swsa_pmm/ser2' is now open once
monitor devc-sermx[ 3]drv_pmd_connect application_power.c@512 : Exiting
monitor devc-sermx[ 3]drv_pmd_init application_power.c@257 : Entering
USER devc-sermx[ 3]drv_pmd_init application_power.c@290 : Registering with Power Mode Manager (COID: 1073741829, Event: 0x4, timeout: 10000)
monitor devc-sermx[ 3]drv_pmd_init application_power.c@310 : Exiting
DEBUG2 devc-sermx[ 3]powerManagerThread application_power.c@205 : Initial Power Mode - Active
DEBUG2 devc-sermx[ 3]power_init_callback powerManager.c@135 : Started in active mode.
ERROR bcsp[ 3]BCSPReceiveMessagesThread ThreadApi.c@109 : Failed sending ABCSP message. Error (9)'Bad file descriptor'

***
Starting [32;1mgraphics[m
Setting up display for 3.50 Mid/High Series (47Hz)
Starting [32;1mhmi[m
Starting [32;1mapplications[m

***
Starting [32;1mdiagnostics[m
You specified the -m option with the parameter: h
Gui configured for high series module
You specified the -l option (dynamic list browsing enabled) with Window Size 120

***

***

***
USB UPDATE -> SUCCESS

Startup completed.

monitor bluetoothp[ 4]BcspStackRestart BcspStreamMessageInt@342 : Attempting reset of BCSP stack...
bluetoothp[ 4]SetPhoneState PhoneApi.c@1282 : Set phone state to 0

***
monitor wm8580a-co[ 1]MUTE_DP_ACK Wm8580aControl.c@314 : Wrote: HMI_ D P _ A U D I O _vehicle_seS[T E1R]EhmiUpdateHandlerO _ MvehicleSettingsHmiHaU@T101E _ A:C TwIrVoEt e1
ignition state 1 to HmMoIn
itor wm8580a-co[ 1]MONO_ATT_DP_WR Wm8580aControl.c@402 : Wrote: HMI_DP_AUDIO_MONO_ATTENUATION_VALUESET 225
monitor wm8580a-co[ 1]MONO_ATT_DP_WR Wm8580aControl.c@402 : Wrote: HMI_DP_AUDIO_MONO_ATTENUATION_VALUESET 225
m obluetoothpn[i t5o]rHandleHMIEvent wm8580a-co [ HmiApi.c1@]285MONO_ATT_DP_WR : Wm8580aControl.cH@a402n d l:i nWgr oHtMeI:- >HBMlIu_eDtPo_oAtUhD IeOv_eMnOtN O(_1110A)T
TENUATION_VALUESET 225
bluetoothp[ 5]HandleHMIEvent HmiApi.c@285 : Handling HMI->Bluetooth event (1425)

***

***
bluetoothp[ 5]HandleHMIEvent HmiApi.c@285 : Handling HMI->Bluetooth event (1110)
bluetoothp[ 8]SetPhoneState PhoneApi.c@1282 : Set phone state to 0
bluetoothp[ 8]SetPhoneState PhoneApi.c@1282 : Set phone state to 0

***

***

***
JasonACT is offline   Reply With Quote