Go Back   Australian Ford Forums > General Topics > The Pub

The Pub For General Automotive Related Talk

Reply
 
Thread Tools Display Modes
Old 02-12-2019, 08:10 AM   #211
hellrc5
Regular Member
 
Join Date: Sep 2011
Posts: 155
Default Re: FORD technical service bulletin : ICC touch screen display

Quote:
Originally Posted by XRPete View Post
Hi JasonACT,


These boards could heating up enough to de-solder some points off the board slightly?


image
It is not because of the heat, that would require a few hundred celsius but because of the 'environment friendly' soldering material which contains no lead. Over the years plus vibration the solder joints become 'dry' and eventually they crack and intermittently or permanently stop conducting power, this broken solder is also known as a 'cold joint'.

Sometimes the crack is invisible or very hard to detect especially if is is sitting on the bottom side of a BGA chip (it is sitting on a number of tiny solder blobs) an often affects more than one components.

Not so surprisingly old equipment from pre 2000 era almost never fails this way.

Sent from my Note7 FE - Flames Extinguished edition
hellrc5 is offline   Reply With Quote Multi-Quote with this Post
3 users like this post:
Old 02-12-2019, 09:14 AM   #212
JasonACT
Away on leave
 
Join Date: Apr 2019
Location: ACT
Posts: 1,735
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

Quote:
Originally Posted by XRPete View Post
Hi JasonACT,

So, are you saying that the Bluetooth chip is causing this?
if so, Ive taken a picture of my chip from the side, as i noticed it sits rather high.

Maybe its just a matter of getting these re-flowed?

These boards could heating up enough to de-solder some points off the board slightly?

Correct me if I'm wrong here..

image
The broken screen I have had both the USB and Bluetooth chips die. This was due to jumpstarting another car. I don't think this one has become de-soldered. You are in a different situation as yours just died on its own, but I've seen that happen on plenty of computer dongles (WiFi and Bluetooth).

You should be using a logic analyser to tell if the chips are not working - or giving instructions to just replace both chips to a tech... If you are going to pay for a professional reflow of a chip without testing it, better to just replace them.

The thing with the Bluetooth in my case though is, it's got enough working bits inside to do the comms (you can see a link is established) but the Bluetooth chip isn't initializing to the point where it will talk first - which is what the main CPU is waiting for.
JasonACT is offline   Reply With Quote Multi-Quote with this Post
This user likes this post:
Old 02-12-2019, 09:20 PM   #213
JasonACT
Away on leave
 
Join Date: Apr 2019
Location: ACT
Posts: 1,735
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

Quote:
Originally Posted by Ansith View Post
Awesome work! Looks like you've finally go the answer on what actually fails on these.
Thanks. But while I'm sure both USB and Bluetooth chips stopped working properly, I'm not sure that is the end of it...

Yesterday and tonight, I worked on programming up a microcontroller to simulate the Bluetooth chip (because, while the brand I need were very popular 10 years ago, they don't seem to be in favour anymore - so I can't get one in a module I can use - I can get a 2.0 version but it initialises at 9600 baud - the 2.1 versions I need do 115200 on startup). The simulation will perform the initial connection, and respond with recorded data from the working unit, but while I can get it to connect ok - the main CPU never requests anything more than when the broken chip was still installed.

Importantly, the "break" signal (which I've also simulated, but was definitely not working with the real chip) isn't responded to in the same way as the working unit. But if I restart the connection routine from the "Bluetooth side" in the simulation, using a short timer, then the main CPU does go through the connection process again to completion.

From what I can tell, the iThing authentication chip is the next item on the list to be accessed when Bluetooth starts up, but it never gets accessed after the BT initialisation - and in fact the working unit has two "glitches" showing on the analyser (I posted a picture about the iThing) before a major read happens and I only get one glitch on the broken unit.

I had pulled two level shifting chips off the board (U408 & U1003) because the errata for the chips says "don't use them for new designs" as they have some serious faults. Testing tonight, I still didn't see any activity on the two wire bus they are meant to convert... Except once, when it did start to be very active - but I tried again quite a few times and nothing ever happened again. I've since put the chips back, but still no activity on any other attempts.

I suspect a 3rd casualty in this messy ongoing war. I wonder if the boards that die on their own are simpler to fix? But having said that, I am glad I've got hold of one that has the plethora of issues.
JasonACT is offline   Reply With Quote Multi-Quote with this Post
4 users like this post:
Old 02-12-2019, 09:59 PM   #214
JasonACT
Away on leave
 
Join Date: Apr 2019
Location: ACT
Posts: 1,735
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 did also mean to post this, since I could test where CN8 goes to now:



The 2nd and 3rd pads don't seem to go to the chip, but rather to U402 (which is one of the unknown ones). Perhaps RTS/CTS for the UART though - not sure which is which, I've never saturated the bus to make one of them change signals. Pad 1 didn't change for me on the broken board, but I assume (I really should test it) that when the unit powers down, that will turn off the Bluetooth device to save power. I've never seen the SPI port active.
JasonACT is offline   Reply With Quote Multi-Quote with this Post
2 users like this post:
Old 03-12-2019, 05:02 PM   #215
JasonACT
Away on leave
 
Join Date: Apr 2019
Location: ACT
Posts: 1,735
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

Well, I think the Bluetooth chip might have been ok after all - but I don't feel bad, because without removing it you couldn't tell what some signals were.

I've updated the CN8 image in the post above this one.. Pin 1 is most probably just 3.3v (which also goes to the enable pins for the voltage regulators on the Bluetooth chip). Pin 2 is still a mystery - working board shows a low signal, see the 3rd analyser line in the following image. The 4th analyser line is pin 3 - it's a reset line coming from the main CPU (this I would never have known without removing the BT chip). Top two lines are Tx and Rx (BT chip). You can see it becomes active when reset by the main CPU.



I also found this gem - the B version chip matches what's in this screen - so I finally have a bit more information to use...



So testing the reset lines of the iThing chip (4th output shown) and the video chip (3rd output - this chip is on the same 2 wire bus) - you can see they are resetting the two devices in a very specific way (2 wire busses can get out of sync otherwise).



The broken board never raises the iThing chip's reset line (middle of image) which is meant to happen about 1 second after Bluetooth makes the connection (two top outputs).

Logic would say the video (being enabled at that point) is causing an issue - but with exhaustive testing, video only becomes active on the reset that happens 2/3rds along on the 3rd output.

It's a real mystery what else is happening on the board at this time - audio has already been configured (but also gets more config written after the 2nd BT connection takes place). Touch screen is fairly consistent as shown before. USB is done and dusted way earlier and never generates signals again unless something is plugged in.

Thinking video was the last thing that became active, I changed the flags via the CAN BUS to disable everything (reverse cam, touch screen, park assist). Nothing helped though.

It does just now occur to me - maybe the main unit is attempting to read the flags out of the smaller board and is getting stuck - this is about the point it would want to know if the reverse camera is installed?
JasonACT is offline   Reply With Quote Multi-Quote with this Post
4 users like this post:
Old 03-12-2019, 07:12 PM   #216
JasonACT
Away on leave
 
Join Date: Apr 2019
Location: ACT
Posts: 1,735
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 should have looked sooner, but running the logic analyser over the 50 pins joining the two boards has helped to discover these two UART lines:





Damn it though, my microcontroller with lots of serial ports is the one I was using to emulate the Bluetooth chip - so these dumps are not complete (white wire is 1, black wire is 2):

Working unit:


Ready
*
*
2__00_____________________________________________ ___________________
1__53 0E 0D 00 01 00 00 00 00 0D 00 00 00 00 00 00__ S______________
*
*
*
*
*
1__00 5C______________________________________________\_ _____________
2__53 0C 02 80 00 00 DD______________________________S______________
1__50 00 18 48 53 0C 04 01 02 01 02 00 5B____________P__HS______ [__
2__50 00 18 48 53 0C 52 01 00 01 20 20 20 20 20 20__ P__HS R________
2__20 20 73 68 5B 20 31 3A 31 32 32 38 39 33 20 20____ sh[ 1:122893__
2__5D 74 74 79 5F 69 6E 69 74 20 20 20 20 20 20 20__ ]tty_init______
2__20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20__________________
2__20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 74__________________t
2__74 79 2E 63 40 31 36 32 20 20 45__________________ty.c@162__E____
1__50 00 18 48 53 0C 04 02 02 01 01 AE F5____________P__HS__________
2__50 00 18 48 53 0C 52 01 00 01 20 20 20 20 20 20__ P__HS R________
2__20 20 73 68 5B 20 31 3A 31 32 32 38 39 33 20 20____ sh[ 1:122893__
2__5D 74 74 79 5F 69 6E 69 74 20 20 20 20 20 20 20__ ]tty_init______
2__20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20__________________
2__20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 74__________________t
2__74 79 2E 63 40 31 36 32 20 20 45__________________ty.c@162__E____
1__50 00 18 48______________________________________ P__H____________
2__53 0C 42 02 00 01 7C 20 4E 6F 20 63 6F 6E 74 72__ S B__ | No contr
2__6F 6C 6C 69 6E 67 20 74 74 79 20 28 6F 70 65 6E__ olling tty (open
2__20 2F 64 65 76 2F 74 74 79 3A 20 4E 6F 20 73 75____/dev/tty: No su
2__63 68 20 64 65 76 69 63 65 20 6F 72 20 61 64 64__ ch device or add
2__72 65 73 73 29 0A 25______________________________ress) %________
1__50 00 18 48 53 0C 04 03 02 01 01 6C 36____________P__HS______l6__
2__50 00 18 48 53 0C 42 02 00 01 7C 20 4E 6F 20 63__ P__HS B__ | No c
2__6F 6E 74 72 6F 6C 6C 69 6E 67 20 74 74 79 20 28__ ontrolling tty (
2__6F 70 65 6E 20 2F 64 65 76 2F 74 74 79 3A 20 4E__ open /dev/tty: N
2__6F 20 73 75 63 68 20 64 65 76 69 63 65 20 6F 72__ o such device or
2__20 61 64 64 72 65 73 73 29 0A 25__________________ address) %____
1__50 00 18 48______________________________________ P__H____________
2__53 0C 52 03 00 01 73 68 3A 20 20 20 20 20 20 20__ S R__ sh:______
2__20 20 73 68 5B 20 31 3A 31 32 32 38 39 33 20 20____ sh[ 1:122893__
2__5D 74 74 79 5F 69 6E 69 74 20 20 20 20 20 20 20__ ]tty_init______
2__20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20__________________
2__20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 74__________________t
2__74 79 2E 63 40 31 42______________________________ty.c@1B________
1__50 00 18 48 53 0C 04 04 02 01 01 1A 47____________P__HS______ G__
2__50 00 18 48 53 0C 52 03 00 01 73 68 3A 20 20 20__ P__HS R__ sh:__
2__20 20 20 20 20 20 73 68 5B 20 31 3A 31 32 32 38________ sh[ 1:1228
2__39 33 20 20 5D 74 74 79 5F 69 6E 69 74 20 20 20__ 93__]tty_init__
2__20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20__________________
2__20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20__________________
2__20 20 20 74 74 79 2E 63 40 31 42____________________ tty.c@1B____
1__50 00 18 48______________________________________ P__H____________
2__53 0C 46 04 00 01 36 32 20 20 7C 20 4E 6F 20 63__ S F__ 62__| No c
2__6F 6E 74 72 6F 6C 6C 69 6E 67 20 74 74 79 20 28__ ontrolling tty (
2__6F 70 65 6E 20 2F 64 65 76 2F 74 74 79 3A 20 4E__ open /dev/tty: N
2__6F 20 73 75 63 68 20 64 65 76 69 63 65 20 6F 72__ o such device or
2__20 61 64 64 72 65 73 73 29 0A 23__________________ address) #____
1__50 00 18 48 53 0C 04 05 02 01 00 D4 89____________P__HS__________
2__50 00 18 48 53 0C 46 04 00 01 36 32 20 20 7C 20__ P__HS F__ 62__|
2__4E 6F 20 63 6F 6E 74 72 6F 6C 6C 69 6E 67 20 74__ No controlling t
2__74 79 20 28 6F 70 65 6E 20 2F 64 65 76 2F 74 74__ ty (open /dev/tt
2__79 3A 20 4E 6F 20 73 75 63 68 20 64 65 76 69 63__ y: No such devic
2__65 20 6F 72 20 61 64 64 72 65 73 73 29 0A 23______e or address) #
1__50 00 18 48______________________________________ P__H____________
2__53 0F 06 05 03 04 00 0B 01 48 1A__________________S________H______
1__50 00 18 48______________________________________ P__H____________
2__53 0F 11 06 03 07 00 41 52 37 39 2D 31 34 47 31__ S______AR79-14G1
2__38 30 2D 41 41 29________________________________ 80-AA)__________
1__50 00 18 48______________________________________ P__H____________
2__53 0C 29 07 00 01 7C 20 77 61 72 6E 69 6E 67 3A__ S )__ | warning:
2__20 77 6F 6E 27 74 20 68 61 76 65 20 66 75 6C 6C____won't have full
2__20 6A 6F 62 20 63 6F 6E 74 72 6F 6C 0A 7A__________job control z__
1__50 00 18 48 53 0F 0C 06 03 02 00 00 03 D4 7E 00__ P__HS________ ~
1__00 E3 2B 00 36______________________________________+ 6__________
2__50 00 18 48______________________________________ P__H____________
1__53 0C 04 07 02 01 00 AB F4________________________S______________
2__50 00 18 48______________________________________ P__H____________
1__53 0F 08 08 03 03 00 00 13 4A EC 00 E9____________S________J______
2__50 00 18 48 53 0C 29 07 00 01 7C 20 77 61 72 6E__ P__HS )__ | warn
2__69 6E 67 3A 20 77 6F 6E 27 74 20 68 61 76 65 20__ ing: won't have
2__66 75 6C 6C 20 6A 6F 62 20 63 6F 6E 74 72 6F 6C__ full job control
2__0A 7A______________________________________________z_ _____________
1__50 00 18 48______________________________________ P__H____________
2__53 0C 52 08 00 01 73 68 3A 20 20 20 20 20 20 20__ S R__ sh:______
2__20 20 73 68 5B 20 31 3A 31 32 32 38 39 33 20 20____ sh[ 1:122893__
2__5D 6A 5F 63 68 61 6E 67 65 20 20 20 20 20 20 20__ ]j_change______
2__20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20__________________
2__20 20 20 20 20 20 20 20 20 20 20 20 20 20 6A 6F________________ jo
2__62 73 2E 63 40 34 0E______________________________bs.c@4__________
1__50 00 18 48 53 0C 04 09 02 01 00 59 08____________P__HS______Y____
2__50 00 18 48 53 0C 52 08 00 01 73 68 3A 20 20 20__ P__HS R__ sh:__
2__20 20 20 20 20 20 73 68 5B 20 31 3A 31 32 32 38________ sh[ 1:1228
2__39 33 20 20 5D 6A 5F 63 68 61 6E 67 65 20 20 20__ 93__]j_change__
2__20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20__________________
2__20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20__________________
2__20 20 6A 6F 62 73 2E 63 40 34 0E____________________jobs.c@4______
1__50 00 18 48______________________________________ P__H____________
2__53 0C 02 09 00 00 54______________________________S____ T________
1__50 00 18 48______________________________________ P__H____________
2__53 0C 2D 0A 00 01 30 35 20 20 7C 20 77 61 72 6E__ S -__ 05__| warn
2__69 6E 67 3A 20 77 6F 6E 27 74 20 68 61 76 65 20__ ing: won't have
2__66 75 6C 6C 20 6A 6F 62 20 63 6F 6E 74 72 6F 6C__ full job control
2__0A 76______________________________________________v_ _____________
1__50 00 18 48 53 0C 04 0A 02 01 00 2C 7E____________P__HS______,~__
2__50 00 18 48 53 0C 2D 0A 00 01 30 35 20 20 7C 20__ P__HS -__ 05__|
2__77 61 72 6E 69 6E 67 3A 20 77 6F 6E 27 74 20 68__ warning: won't h
2__61 76 65 20 66 75 6C 6C 20 6A 6F 62 20 63 6F 6E__ ave full job con
2__74 72 6F 6C 0A 76________________________________ trol v__________
1__50 00 18 48______________________________________ P__H____________
2__53 0C 04 0B 00 01 23 20 52________________________S____ # R______
1__50 00 18 48 53 0C 04 0B 02 01 00 28 7B____________P__HS______({__
*
*
*
*
*
*
2__50 00 18 48 53 07 02 0C 01 00 5B__________________P__HS____ [____
1__50 00 18 48 53 07 08 0C 01 02 03 08 00 01 00 00__ P__HS__________
1__59_____________________________________________ ___Y______________
*
*
*
2__50 00 18 48 53 0F 06 0D 03 01 00 02 00 FF A8______P__HS__________
*
*
1__50 00 18 48______________________________________ P__H____________
2__53 03 03 0E 01 01 02 5F__________________________ S_______________
1__50 00 18 48 53 03 0A 0D 00 01 40 00 00 00 00 00__ P__HS____ @____
1__00 00 16________________________________________________ __________
2__50 00 18 48 53 03 03 0F 01 01 02 5E______________ P__HS______^____
1__50 00 18 48 53 03 0A 0E 00 01 40 00 00 00 00 00__ P__HS____ @____
1__00 00 15________________________________________________ __________
2__50 00 18 48______________________________________ P__H____________
1__53 03 0A 0F 00 01 40 00 00 00 00 00 00 00 14______S____ @________
2__50 00 18 48 53 02 0A 10 0D 04 00 00 00 00 00 00__ P__HS__________
2__00 00 42____________________________________________B___ _________
1__50 00 18 48______________________________________ P__H____________
2__53 02 0A 11 0D 04 00 00 00 00 00 00 00 00 43______S____________ C
1__50 00 18 48______________________________________ P__H____________
2__53 02 0A 12 0D 04 00 00 00 00 00 00 00 00 40______S____________ @
1__50 00 18 48______________________________________ P__H____________
2__53 04 03 13 03 02 02 44__________________________ S______D________
1__50 00 18 48______________________________________ P__H____________
2__53 04 0A 14 02 03 00 00__________________________ S______________
1__53 04 07 10______________________________________ S______________
2__00 00 7F F0________________________________________________ ______
1__00 07 00 0D________________________________________________ ______
2__00 00 C7________________________________________________ __________
1__01 1A 00 51__________________________________________Q_____ _______
2__50 00 18 48______________________________________ P__H____________
1__50 00 18 48 53 04 0A 11 01 02 00 00 00 44 00 00__ P__HS________D__
1__00 00 0B________________________________________________ __________
2__50 00 18 48______________________________________ P__H____________
1__53 03 0A 12 00 01 40 00 00 00 00 00 00 00 09______S____ @________
2__50 00 18 48______________________________________ P__H____________
1__53 04 06 13 04 02 00 09 00 0D 40__________________S________ @____
2__50 00 18 48______________________________________ P__H____________
1__53 04 05 14 05 02 00 00 00 41____________________ S________A______
2__50 00 18 48______________________________________ P__H____________
1__53 04 15 15 06 05 31 00 14 0A 0A 05 01 2C 03 E8__ S____ 1______,__
1__40 01 26 43 64 00 00 00 01 F3____________________ @ &Cd__________
2__50 00 18 48______________________________________ P__H____________
1__53 04 07 16 07 01 00 00 00 00 00 40______________ S__________@____
2__50 00 18 48______________________________________ P__H____________
1__53 04 22 17 08 01 46 6F 72 64 20 46 61 6C 63 6F__ S "__ Ford Falco
1__6E 20 42 6C 75 65 74 6F 6F 74 68 00 00 00 00 00__ n Bluetooth____
1__00 00 00 00 00 00 2B____________________________________+________
2__50 00 18 48 53 02 09 15 06 07 00 0B 00 10 00 00__ P__HS__________
2__20 77______________________________________________w_ _____________
1__50 00 18 48______________________________________ P__H____________
2__53 02 03 16 0F 03 02 4A__________________________ S______J________
1__50 00 18 48 53 02 14 18 01 04 00 00 00 00 00 00__ P__HS__________
1__00 00 00 00 00 00 00 00 00 00 00 0C 54________________________T__
2__50 00 18 48______________________________________ P__H____________
1__53 02 09 19 02 03 00 40 00 40 00 00 00 40________ S______@ @__ @__
2__50 00 18 48______________________________________ P__H____________
1__53 02 07 1A 03 03 00 00 00 00 00 4C______________ S__________L____
2__50 00 18 48______________________________________ P__H____________
1__53 02 05 1B 05 03 00 00 00 49____________________ S________I______
2__50 00 18 48______________________________________ P__H____________
1__53 02 0A 1C 08 03 00 00 00 00 00 00 00 00 4C______S____________ L
2__50 00 18 48______________________________________ P__H____________
1__53 02 0A 1D 09 03 00 00 00 00 00 00 00 F8 B4______S______________
2__50 00 18 48______________________________________ P__H____________
1__53 02 05 1E 0A 03 00 00 00 43____________________ S________C______
2__50 00 18 48______________________________________ P__H____________
1__53 02 07 1F 0B 03 00 00 00 00 00 41______________ S__________A____
2__50 00 18 48______________________________________ P__H____________
1__53 02 08 20 0C 03 00 00 00 00 00 01 77____________S__________ w__
2__50 00 18 48______________________________________ P__H____________
1__53 02 06 21 11 04 0C 00 00 00 6F__________________S__!______o____
2__50 00 18 48______________________________________ P__H____________
1__53 02 0A 22 12 02 00 00 00 00 00 00 00 00 69______S__"__________i
2__50 00 18 48______________________________________ P__H____________
1__53 02 08 23 13 01 00 00 00 00 00 00 68____________S__#________h__
2__50 00 18 48______________________________________ P__H____________
1__53 02 03 24 00 03 10 65__________________________ S__$__ e________
2__50 00 18 48______________________________________ P__H____________
1__53 03 0A 25 00 01 40 00 00 00 00 00 00 00 3E______S__%__@______ >
2__50 00 18 48______________________________________ P__H____________
1__53 03 0A 26 00 01 40 00 00 00 00 00 00 00 3D______S__&__@______ =
*
2__50 00 18 48______________________________________ P__H____________
1__53 03 0A 27 00 01 40 00 00 00 00 00 00 00 3C______S__'__@______ <
2__50 00 18 48______________________________________ P__H____________
1__53 03 0A 28 00 01 40 00 00 00 00 00 00 00 33______S__(__@______ 3
2__50 00 18 48______________________________________ P__H____________
1__53 03 0A 29 00 01 40 00 00 00 00 00 00 00 32______S__)__@______ 2
2__50 00 18 48______________________________________ P__H____________
1__53 07 08 2A 01 04 10 08 00 01 00 00 6A____________S__*________j__
2__50 00 18 48______________________________________ P__H____________
1__53 03 0A 2B 00 01 40 00 00 00 00 00 00 00 30______S__+__@______ 0
2__50 00 18 48______________________________________ P__H____________
1__53 03 0A 2C 00 01 40 00 00 00 00 00 00 00 37______S__,__@______ 7
2__50 00 18 48______________________________________ P__H____________
1__53 03 0A 2D 00 01 40 00 00 00 00 00 00 00 36______S__-__@______ 6
*
2__50 00 18 48______________________________________ P__H____________
1__53 03 0A 2E 00 01 40 00 00 00 00 00 00 00 35______S__.__@______ 5
2__50 00 18 48______________________________________ P__H____________
1__53 03 0A 2F 00 01 40 00 00 00 00 00 00 00 34______S__/__@______ 4
2__50 00 18 48______________________________________ P__H____________
1__53 03 0A 30 00 01 40 00 00 00 00 00 00 00 2B______S__0__@______ +
*
2__50 00 18 48______________________________________ P__H____________
1__53 03 0A 31 00 01 40 00 00 00 00 00 00 00 2A______S__1__@______ *
2__50 00 18 48______________________________________ P__H____________
1__53 03 0A 32 00 01 40 00 00 00 00 00 00 00 29______S__2__@______ )
2__50 00 18 48______________________________________ P__H____________
1__53 03 0A 33 00 01 40 00 00 00 00 00 00 00 28______S__3__@______ (
*
2__50 00 18 48______________________________________ P__H____________
1__53 03 0A 34 00 01 40 00 00 00 00 00 00 00 2F______S__4__@______ /
2__50 00 18 48______________________________________ P__H____________
1__53 03 0A 35 00 01 40 00 00 00 00 00 00 00 2E______S__5__@______ .
2__50 00 18 48______________________________________ P__H____________
1__53 03 0A 36 00 01 40 00 00 00 00 00 00 00 2D______S__6__@______ -
*
2__50 00 18 48______________________________________ P__H____________
1__53 03 0A 37 00 01 40 00 00 00 00 00 00 00 2C______S__7__@______ ,
2__50 00 18 48______________________________________ P__H____________
1__53 03 0A 38 00 01 40 00 00 00 00 00 00 00 23______S__8__@______ #
2__50 00 18 48______________________________________ P__H____________
1__53 03 0A 39 00 01 40 00 00 00 00 00 00 00 22______S__9__@______ "
*
2__50 00 18 48______________________________________ P__H____________
1__53 03 0A 3A 00 01 40 00 00 00 00 00 00 00 21______S__:__@______ !
2__50 00 18 48______________________________________ P__H____________
1__53 03 0A 3B 00 01 40 00 00 00 00 00 00 00 20______S__;__@________
2__50 00 18 48______________________________________ P__H____________
1__53 03 0A 3C 00 01 40 00 00 00 00 00 00 00 27______S__<__@______ '
*
2__50 00 18 48______________________________________ P__H____________
1__53 03 0A 3D 00 01 40 00 00 00 00 00 00 00 26______S__=__@______ &


Broken unit:


*
*
2__F0_____________________________________________ ___________________
1__00_____________________________________________ ___________________
2__00 00________________________________________________ ____________
1__53 0E 0D 00 01 00 00 00 00 0D 00 00 00 00 00 00__ S______________
*
*
*
*
*
1__00 5C______________________________________________\_ _____________
2__53 0C 02 80 00 00 DD______________________________S______________
1__50 00 18 48 53 0C 04 01 02 01 02 00 5B____________P__HS______ [__
2__50 00 18 48 53 0C 52 01 00 01 20 20 20 20 20 20__ P__HS R________
2__20 20 73 68 5B 20 31 3A 31 32 32 38 39 33 20 20____ sh[ 1:122893__
2__5D 74 74 79 5F 69 6E 69 74 20 20 20 20 20 20 20__ ]tty_init______
2__20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20__________________
2__20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 74__________________t
2__74 79 2E 63 40 31 36 32 20 20 45__________________ty.c@162__E____
1__50 00 18 48 53 0C 04 02 02 01 01 AE F5____________P__HS__________
2__50 00 18 48 53 0C 52 01 00 01 20 20 20 20 20 20__ P__HS R________
2__20 20 73 68 5B 20 31 3A 31 32 32 38 39 33 20 20____ sh[ 1:122893__
2__5D 74 74 79 5F 69 6E 69 74 20 20 20 20 20 20 20__ ]tty_init______
2__20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20__________________
2__20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 74__________________t
2__74 79 2E 63 40 31 36 32 20 20 45__________________ty.c@162__E____
1__50 00 18 48______________________________________ P__H____________
2__53 0C 42 02 00 01 7C 20 4E 6F 20 63 6F 6E 74 72__ S B__ | No contr
2__6F 6C 6C 69 6E 67 20 74 74 79 20 28 6F 70 65 6E__ olling tty (open
2__20 2F 64 65 76 2F 74 74 79 3A 20 4E 6F 20 73 75____/dev/tty: No su
2__63 68 20 64 65 76 69 63 65 20 6F 72 20 61 64 64__ ch device or add
2__72 65 73 73 29 0A 25______________________________ress) %________
1__50 00 18 48 53 0C 04 03 02 01 01 6C 36____________P__HS______l6__
2__50 00 18 48 53 0C 42 02 00 01 7C 20 4E 6F 20 63__ P__HS B__ | No c
2__6F 6E 74 72 6F 6C 6C 69 6E 67 20 74 74 79 20 28__ ontrolling tty (
2__6F 70 65 6E 20 2F 64 65 76 2F 74 74 79 3A 20 4E__ open /dev/tty: N
2__6F 20 73 75 63 68 20 64 65 76 69 63 65 20 6F 72__ o such device or
2__20 61 64 64 72 65 73 73 29 0A 25__________________ address) %____
1__50 00 18 48______________________________________ P__H____________
2__53 0C 52 03 00 01 73 68 3A 20 20 20 20 20 20 20__ S R__ sh:______
2__20 20 73 68 5B 20 31 3A 31 32 32 38 39 33 20 20____ sh[ 1:122893__
2__5D 74 74 79 5F 69 6E 69 74 20 20 20 20 20 20 20__ ]tty_init______
2__20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20__________________
2__20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 74__________________t
2__74 79 2E 63 40 31 42______________________________ty.c@1B________
1__50 00 18 48 53 0C 04 04 02 01 01 1A 47____________P__HS______ G__
2__50 00 18 48 53 0C 52 03 00 01 73 68 3A 20 20 20__ P__HS R__ sh:__
2__20 20 20 20 20 20 73 68 5B 20 31 3A 31 32 32 38________ sh[ 1:1228
2__39 33 20 20 5D 74 74 79 5F 69 6E 69 74 20 20 20__ 93__]tty_init__
2__20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20__________________
2__20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20__________________
2__20 20 20 74 74 79 2E 63 40 31 42____________________ tty.c@1B____
1__50 00 18 48______________________________________ P__H____________
2__53 0C 46 04 00 01 36 32 20 20 7C 20 4E 6F 20 63__ S F__ 62__| No c
2__6F 6E 74 72 6F 6C 6C 69 6E 67 20 74 74 79 20 28__ ontrolling tty (
2__6F 70 65 6E 20 2F 64 65 76 2F 74 74 79 3A 20 4E__ open /dev/tty: N
2__6F 20 73 75 63 68 20 64 65 76 69 63 65 20 6F 72__ o such device or
2__20 61 64 64 72 65 73 73 29 0A 23__________________ address) #____
1__50 00 18 48 53 0C 04 05 02 01 00 D4 89____________P__HS__________
2__50 00 18 48 53 0C 46 04 00 01 36 32 20 20 7C 20__ P__HS F__ 62__|
2__4E 6F 20 63 6F 6E 74 72 6F 6C 6C 69 6E 67 20 74__ No controlling t
2__74 79 20 28 6F 70 65 6E 20 2F 64 65 76 2F 74 74__ ty (open /dev/tt
2__79 3A 20 4E 6F 20 73 75 63 68 20 64 65 76 69 63__ y: No such devic
2__65 20 6F 72 20 61 64 64 72 65 73 73 29 0A 23______e or address) #
1__50 00 18 48______________________________________ P__H____________
2__53 0F 06 05 03 04 00 0B 03 4A 1A__________________S________J______
1__50 00 18 48______________________________________ P__H____________
2__53 0F 11 06 03 07 00 41 52 37 39 2D 31 34 47 31__ S______AR79-14G1
2__38 30 2D 41 41 29________________________________ 80-AA)__________
1__50 00 18 48______________________________________ P__H____________
2__53 0C 29 07 00 01 7C 20 77 61 72 6E 69 6E 67 3A__ S )__ | warning:
2__20 77 6F 6E 27 74 20 68 61 76 65 20 66 75 6C 6C____won't have full
2__20 6A 6F 62 20 63 6F 6E 74 72 6F 6C 0A 7A__________job control z__
1__50 00 18 48 53 0F 0C 06 03 02 00 00 04 23 35 00__ P__HS________#5
1__00 E3 2B 00 8D______________________________________+_________ ___
2__50 00 18 48______________________________________ P__H____________
1__53 0C 04 07 02 01 00 AB F4________________________S______________
2__50 00 18 48______________________________________ P__H____________
1__53 0F 08 08 03 03 00 00 14 47 6A 00 65____________S________Gj e__
2__50 00 18 48 53 0C 29 07 00 01 7C 20 77 61 72 6E__ P__HS )__ | warn
2__69 6E 67 3A 20 77 6F 6E 27 74 20 68 61 76 65 20__ ing: won't have
2__66 75 6C 6C 20 6A 6F 62 20 63 6F 6E 74 72 6F 6C__ full job control
2__0A 7A______________________________________________z_ _____________
1__50 00 18 48______________________________________ P__H____________
2__53 0C 52 08 00 01 73 68 3A 20 20 20 20 20 20 20__ S R__ sh:______
2__20 20 73 68 5B 20 31 3A 31 32 32 38 39 33 20 20____ sh[ 1:122893__
2__5D 6A 5F 63 68 61 6E 67 65 20 20 20 20 20 20 20__ ]j_change______
2__20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20__________________
2__20 20 20 20 20 20 20 20 20 20 20 20 20 20 6A 6F________________ jo
2__62 73 2E 63 40 34 0E______________________________bs.c@4__________
1__50 00 18 48 53 0C 04 09 02 01 00 59 08____________P__HS______Y____
2__50 00 18 48 53 0C 52 08 00 01 73 68 3A 20 20 20__ P__HS R__ sh:__
2__20 20 20 20 20 20 73 68 5B 20 31 3A 31 32 32 38________ sh[ 1:1228
2__39 33 20 20 5D 6A 5F 63 68 61 6E 67 65 20 20 20__ 93__]j_change__
2__20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20__________________
2__20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20__________________
2__20 20 6A 6F 62 73 2E 63 40 34 0E____________________jobs.c@4______
1__50 00 18 48______________________________________ P__H____________
2__53 0C 02 09 00 00 54______________________________S____ T________
1__50 00 18 48______________________________________ P__H____________
2__53 0C 2D 0A 00 01 30 35 20 20 7C 20 77 61 72 6E__ S -__ 05__| warn
2__69 6E 67 3A______________________________________ ing:____________
1__53 0C 04 0A______________________________________ S______________
2__20 77 6F 6E________________________________________won_____ _______
1__02 01 00 59 0B______________________________________ Y____________
2__27 74 20 68 61 76 65 20 66 75 6C 6C 20 6A 6F 62__ 't have full job
2__20 63 6F 6E 74 72 6F 6C 0A 76 50 00 18 48__________control vP__H__
1__50 00 18 48______________________________________ P__H____________
2__53 0C 2D 0A 00 01 30 35 20 20 7C 20 77 61 72 6E__ S -__ 05__| warn
2__69 6E 67 3A 20 77 6F 6E 27 74 20 68 61 76 65 20__ ing: won't have
2__66 75 6C 6C 20 6A 6F 62 20 63 6F 6E 74 72 6F 6C__ full job control
2__0A 76______________________________________________v_ _____________
1__50 00 18 48______________________________________ P__H____________
2__53 0C 04 0B 00 01 23 20 52________________________S____ # R______
1__50 00 18 48 53 0C 04 0B 02 01 00 28 7B____________P__HS______({__
*
*
*
*
*
*
2__50 00 18 48 53 07 02 0C 01 00 5B__________________P__HS____ [____
1__50 00 18 48 53 07 08 0C 01 02 11 00 00 01 00 00__ P__HS__________
1__43_____________________________________________ ___C______________
*
*
2__50 00 18 48 53 0F 06 0D 03 01 00 02 00 FF A8______P__HS__________
*
*
*
*
*
*
*
*
*
*
1__50 00 18 48 53 07 08 0D 01 04 1E 00 00 01 00 00__ P__HS__________
1__4B_____________________________________________ ___K______________
*
*
*
*
*
2__50 00 18 48 53 05 06 0E 01 00 00 17 00 00 48______P__HS________ H
*
*
*
*
*
*
*
*
*
*
1__50 00 18 48______________________________________ P__H____________
2__53 05 06 0F 01 00 00 17 00 00 49__________________S________ I____
*
*
*
*
*
*
*
*
1__50 00 18 48______________________________________ P__H____________
*
*
*
*
*
JasonACT is offline   Reply With Quote Multi-Quote with this Post
3 users like this post:
Old 04-12-2019, 05:22 PM   #217
JasonACT
Away on leave
 
Join Date: Apr 2019
Location: ACT
Posts: 1,735
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

So, I've decoded the packet style being used... I see two packet types:

50 00 18 48 :- is an Acknowledgement signal
53 0X LN SQ :- is data, X=?, LN=Length of data, SQ=Sequence (the sequence allows re-transmission of data - which happens a lot here, so more bad programming!)

53 is followed by data, with a 2 byte prefix (destination register?) and whatever data goes into it. After the data is a 1 byte checksum.

I've now used a 4th serial port in the microcontroller to simulate the BT chip:



Output 3 & 4 is the BT link establishment to completion, right hand side. Left hand side is the working board (both these were generated with my original smaller board - to remove any potential differences). 3 & 4 are finished at that point, it's happy at least for now.

The BT chip is linked in the middle of a 6 second pause, then output 2 says something, 1 replies (there's a difference, but I don't quite know why - but I'm not too concerned). Then there's a 2 or 3 second pause, 2 says something and normally 2 will say something else after a couple of seconds... 9 seconds pass on the broken board and 1 gets impatient, probably saying "what gives?".

The data that's expected from 2 is "01 01 02" - so register 0101=02 if my guess is correct. You can see the bottom left says 0801=Ford Falcon Bluetooth for example.

Still no closer, except I know it's meant to happen within about 5 seconds of starting the BT chip. Maybe the chip was broken, and one of its I/O data lines is meant to signal it's ready - I didn't see anything in the datasheet though :(
JasonACT is offline   Reply With Quote Multi-Quote with this Post
2 users like this post:
Old 04-12-2019, 06:58 PM   #218
raceteam
FF.Com.Au Hardcore
 
Join Date: Nov 2013
Posts: 2,037
Default Re: FORD technical service bulletin : ICC touch screen display

I don't think the bluetooth module will fully boot unless the VIN in the FDIM matches the rest of the vehicle. If you try to connect to it, it will show a generic handsfree name rather than Ford Falcon Bluetooth if it hasn't been programmed to the vehicle.
raceteam is offline   Reply With Quote Multi-Quote with this Post
This user likes this post:
Old 04-12-2019, 07:17 PM   #219
JasonACT
Away on leave
 
Join Date: Apr 2019
Location: ACT
Posts: 1,735
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

Ah, but I've already booted my working large board on the bench with the broken unit's smaller board (it reprogrammed my unit to Territory profile). Had no issues booting though

In fact, the small-board, LCD-backlight, LCD-screen & touch-screen units I'm currently using are all from known good units... The 2nd SAT NAV unit I bought (as a spare) had a small scratch on the touch-screen - so I put the worst part on this unit (knowing it's never going back in a car). This broken unit had a really nice touch-screen panel, once cleaned with LCD cleaner solution.
JasonACT is offline   Reply With Quote Multi-Quote with this Post
This user likes this post:
Old 04-12-2019, 09:18 PM   #220
JasonACT
Away on leave
 
Join Date: Apr 2019
Location: ACT
Posts: 1,735
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

Running out of ideas, I ask myself some tough questions, mostly based on my decision to use the best parts (as I mentioned above) for another purpose...

It's quite possible I've got a broken unit that can't "easily" be fixed... Eg. A chip failure on one you wouldn't be able to easily replace - the main CPU for example, having a single I/O line completely die which is used as a gateway to a successful boot.

I always wondered, with reconditioned units, when the touch screen (which IS a single component on its own) is cracked - what do they do with the other parts? Maybe not all broken units are readily fixable, but many of the parts can be recycled?

Site sponsors are welcome to respond.. (Or at least, anyone buying a reconditioned unit should always ask, before a purchase - tell me what is the likely problem! Or, specifically, what did you fix on the reconditioned unit?)
JasonACT is offline   Reply With Quote Multi-Quote with this Post
Old 05-12-2019, 10:32 PM   #221
JasonACT
Away on leave
 
Join Date: Apr 2019
Location: ACT
Posts: 1,735
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

Concentrating on the working unit, I'm looking for something/anything that happens in the "red-zone" I've highlighted:



1st line is the touch screen.
2 is a spare probe which isn't connected.
3 Video input reset.
4 iThing chip reset.
5 Small board serial transmitter.
6 Large board serial transmitter.
7 Bluetooth Rx (transmitter from main CPU).
8 Bluetooth Tx.
9 Bluetooth reset (from main CPU).

The broken board sees #4 (iThing) never become re-enabled.

The working board has many things that constantly happen (various clocks) but after spending a lot of time testing different things (on both sides of the board) I can't find anything which changes in the red zone other than Bluetooth's 3 identified lines.

I've included the touch screen because it's the closest thing that "happens" but zooming in, it shows the large board talking to the small board before that occurs. It's also well after the iThing reset is released (goes high).

Every other signal of interest I noted from the working unit is doing the same on the broken unit. Clocks and all the other signals from the various subsystems. Interestingly, the LCD screen & backlight power chips don't get enabled until about 24 seconds in (and when they do, it's for a very short period).

I don't think the main CPU has a broken I/O pin - at least, I can't find any candidates to test. I'm going to go back and re-test all the power regulators, I think, over this entire boot period. Not tonight though.
JasonACT is offline   Reply With Quote Multi-Quote with this Post
2 users like this post:
Old 06-12-2019, 04:48 PM   #222
JasonACT
Away on leave
 
Join Date: Apr 2019
Location: ACT
Posts: 1,735
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 Multi-Quote with this Post
Old 06-12-2019, 04:49 PM   #223
JasonACT
Away on leave
 
Join Date: Apr 2019
Location: ACT
Posts: 1,735
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

Broken board:

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:0E status 0xE8
..4-bit ECC error block:page 0x0008:24 status 0xE8
4-bit ECC error block:page 0x0008:2D status 0xE8
.4-bit ECC error block:page 0x0008:34 status 0xE8
...4-bit ECC error block:page 0x0009:24 status 0xE8
.4-bit ECC error block:page 0x0009:39 status 0xE8
..4-bit ECC error block:page 0x000A:1D status 0xE8
.4-bit ECC error block:page 0x000A:2B status 0xE8
...4-bit ECC error block:page 0x000B:1D status 0xE8
.4-bit ECC error block:page 0x000B:23 status 0xE8
...4-bit ECC error block:page 0x000C:19 status 0xE8
..4-bit ECC error block:page 0x000C:32 status 0xE8
.4-bit ECC error block:page 0x000D:08 status 0xE8
.4-bit ECC error block:page 0x000D:16 status 0xE8
......4-bit ECC error block:page 0x000E:3A status 0xE8
..4-bit ECC error block:page 0x000F:1B status 0xE8
...4-bit ECC error block:page 0x0010:0A status 0xE8
4-bit ECC error block:page 0x0010:0F status 0xE8
......4-bit ECC error block:page 0x0011:2B status 0xE8
.4-bit ECC error block:page 0x0011:38 status 0xE8
....4-bit ECC error block:page 0x0012:36 status 0xE8
.4-bit ECC error block:page 0x0013:0D status 0xE8
.4-bit ECC error block:page 0x0013:1E status 0xE8
....4-bit ECC error block:page 0x0014:11 status 0xE8
4-bit ECC error block:page 0x0014:1F status 0xE8
...4-bit ECC error block:page 0x0015:02 status 0xE8
4-bit ECC error block:page 0x0015:0A status 0xE8
.4-bit ECC error block:page 0x0015:16 status 0xE8
4-bit ECC error block:page 0x0015:1A status 0xE8
........4-bit ECC error block:page 0x0017:20 status 0xE8
..4-bit ECC error block:page 0x0017:39 status 0xE8
4-bit ECC error block:page 0x0017:3C status 0xE8
.......4-bit ECC error block:page 0x0019:23 status 0xE8
4-bit ECC error block:page 0x0019:2B status 0xE8
.4-bit ECC error block:page 0x0019:3D status 0xE8
..4-bit ECC error block:page 0x001A:19 status 0xE8
.....4-bit ECC error block:page 0x001B:2C status 0xE8
....4-bit ECC error block:page 0x001C:2B status 0xE8
4-bit ECC error block:page 0x001C:2C status 0xE8
.4-bit ECC error block:page 0x001C:3D status 0xE8
....4-bit ECC error block:page 0x001D:33 status 0xE8
4-bit ECC error block:page 0x001D:37 status 0xE8
....4-bit ECC error block:page 0x001E:37 status 0xE8
..4-bit ECC error block:page 0x001F:15 status 0xE8
.4-bit ECC error block:page 0x001F:22 status 0xE8
4-bit ECC error block:page 0x001F:2B status 0xE8
.4-bit ECC error block:page 0x001F:39 status 0xE8
.4-bit ECC error block:page 0x0020:07 status 0xE8
4-bit ECC error block:page 0x0020:0B status 0xE8
....4-bit ECC error block:page 0x0021:0A status 0xE8
4-bit ECC error block:page 0x0021:0F 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

***
fs-etfs-swsa_2048: Validating duplicate sequence 1208.
fs-etfs-swsa_2048: Validating duplicate sequence 1208.

***
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.

265106
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 application_power.c@1840 . 00000000:0 sP:o wHam: eSrt amratneadg:e r( 5252947470n)o
t0 .rStarting [32;1mswsa_binaries_and_libraries[m
0u15999840nsn:i nHam: gL o(g/dev/swsa_pmm )t.i mWeasittaimnpg .s.t.a
rted:1970/01/01 00:00:05:266947330
0.090999090s: Ham: Creating guardian
0.104998950s: Ham: Dumper Died -1
0.106998930s: Ham: New Dumper Pid 372762
0.125998740s: Ham: Attach request from Guardian Pid 372764
DEBUG1 devc-sermx[ 3]ham_startup_thread ham_framework.c@85 : Attached 'ser3' to ham
DEBUG1 devc-sermx[ 3]ham_startup_thread ham_framework.c@99 : Added condition 'DEATH'
DEBUG1 devc-sermx[ 3]ham_startup_thread Creating SDMA Infrastructure...
ham_framework.c@132 : Added action 'RESTART'
CRITICAL wm8580a-co[ 4]powerManagerThread application_power.c@184 : Power manager not running (/dev/swsa_pmm). Waiting...
# monitor devc-sermx[ 2]ApiPowerRun application_power.c@128 : Entering
monitor devc-sermx[ 2]ApiPowerRun application_power.c@136 : Exiting
monitor devc-sermx[ 4]drv_pmd_connect application_power.c@483 : Entering
DEBUG1 devc-sermx[ 4]drv_pmd_connect application_power.c@487 : attach to Power Manager path '/dev/swsa_pmm/ser1'
mon i tDoErB Udevc-sermxG[2 2devc-sermx][ApiPowerRun 4 ] drv_pmd_connectapplication_power.c @ 128 application_power.c @:509 E n:t e'r/dev/swsa_pmm/ser1i'n gi
s n omwo noipteonr odevc-sermxn[c e2
] ApiPowerRunm o n iapplication_power.ct@o136r devc-sermx:[ E4x]idrv_pmd_connectt i n gapplication_power.c
@ 512m o n:i tEoxri tdevc-sermxi[n g3
] drv_pmd_connectm o n iapplication_power.ct@o483r devc-sermx:[ E4n]tdrv_pmd_inite r i napplication_power.cg@
257 D:E BEUnGt1e rdevc-sermxi[n g3
] drv_pmd_connect Uapplication_power.cS@E487R devc-sermx:[ a4t]tdrv_pmd_inita c h application_power.ct@o290 P o:w eRre gMiasntaegreirn gp awtiht h' /dev/swsa_pmm/ser3P'o
wer MDoEdBeU GM2a ndevc-sermxa[g e3r] drv_pmd_connect( C O Iapplication_power.cD@:509 1073741851 ,: E'v/dev/swsa_pmm/ser3e'n ti:s 0nxo4w, otpiemne oountc:e
10000 )m
on i tDoErB Udevc-sermxG[1 3devc-sermx][drv_pmd_connect 3 ] ham_startup_threadapplication_power.c @ 512 ham_framework.c @:85 E x:i tAitntga
c hmeodn i'tser1o'r tdevc-sermxo[ ha3m]
drv_pmd_init m oapplication_power.cn@i257t o r: devc-sermxE[n t4e]rdrv_pmd_initi n g
application_power.c @ 310 U:S EERx idevc-sermxt[i n3g]
drv_pmd_init D Eapplication_power.cB@U290G 2 :devc-sermx [R e4g]ipowerManagerThreads t e rapplication_power.ci@n205g w:i tIhn iPtoiwaelr PMoowdeer MMaondaeg e-r A(cCtOiIvDe:
1073741834 ,D EEBvUeGn2t :devc-sermx [0 x44],power_init_callback t i mpowerManager.ce@o136u t :: 10000S)t
ar tmeodn iitno ra cdevc-sermxt[i v3e] drv_pmd_initm o d eapplication_power.c.@
310 EEBxUiGt1i ndevc-sermxg[
3 ]Dham_startup_threadE B U Gham_framework.c2@ 99devc-sermx [ :3 ]ApowerManagerThreadd d e dapplication_power.c @c205o n d:i tIinoint i a'lD EPAoTwHe'r
M o dDeE B-U GA1c tdevc-sermxi[v e3
] ham_startup_thread D E Bham_framework.cU@G1322 devc-sermx:[ A3d]dpower_init_callbacke d apowerManager.cc@t136i o n: S'tRaErStTeAdR Ti'n
active mode.

***
Starting [32;1mbluetooth[m
monitor devc-sermx[ 2]ApiPowerRun application_power.c@128 : Entering
DEBUG1 devc-sermx[ 3]ham_startup_thread ham_framework.c@85 : Attached 'ser2' to ham
moniStarting [32;1mmedia_player[m
tor devc-sermx[ 2]ApiPowerRun application_power.c@136 : Exiting
monitor devc-sermx[ 5]drv_pmd_connect application_power.c@483 : Entering
DEBUG1 devc-sermx[ 3]ham_startup_thread ham_framework.c@99 : Added condition 'DEATH'
DEBUG1 devc-sermx[ 5]drv_pmd_connect application_power.c@487 : attach to Power Manager path '/dev/swsa_pmm/ser2'
DEBUG1 devc-sermx[ 3]ham_startup_thread ham_framework.c@132 : Added actunknown symbol: iPtUnrealizeWadgeto
n 'unknown symbol: RPtGetRe3ourcesE
Sunknown symbol: Tpthread_-utex_lockA
RTunknown symbol: '3trncpy

unknown symbol: pSetCanvas
Dunknown symbol: Epp_d_freeB
UG2 devc-sermxunknown symbol: [PgCreatESurface
5unknown symbol: ]pthread[mutex_unlockdrv_pmd_connect
unknown symbol: P$LockCurrentDC
application_power.c@509 : '/dev/swsa_pmm/ser2ldd:FATAL: 'Could not resolve all symbols
is now open once
monitor devc-sermx[ 5]drv_pmd_connect application_power.c@512 : Exiting
monitor devc-sermx[ 5]drv_pmd_init application_power.c@257 : Entering
USER devc-sermx[ 5]drv_pmd_init application_power.c@290 : Registering with Power Mode Manager (COID: 1073741829, Event: 0x4, timeout: 10000)
monitor devc-sermx[ 5]drv_pmd_init application_power.c@310 : Exiting
DEBUG2 devc-sermx[ 5]powerManagerThread application_power.c@205 : Initial Power Mode - Active
DEBUG2 devc-sermx[ 5]power_init_callback powerManager.c@136 : Started in active mode.

***

***
unknown symbol: PtUnrealizeWadget
unknown symbol: PtGetRe3ources
unknown symbol: pthread_-utex_lock
unknown symbol: 3trncpy
unknown symbol: pSetCanvas
unknown symbol: pp_d_free
unknown symbol: PgCreatESurface
unknown symbol: pthread[mutex_unlock
unknown symbol: P$LockCurrentDC
ldd:FATAL: Could not resolve all symbols
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
unknown symbol: PtUnrealizeWadget
unknown symbol: PtGetRe3ources
unknown symbol: pthread_-utex_lock
unknown symbol: 3trncpy
unknown symbol: pSetCanvas
unknown symbol: pp_d_free
unknown symbol: PgCreatESurface
unknown symbol: pthread[mutex_unlock
unknown symbol: P$LockCurrentDC
ldd:FATAL: Could not resolve all symbols
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

***

***
ERROR hmi[ 3]dp_writeStringValue dp_basic.c@1738 : ERROR :: CLASS_DP :: COMPONENT_DP_SERVER :: dp_writeStringValue - id:6 is not a string property, string:USB UPDATE -> SUCCESS

Startup completed.


***

***

***

***

***
Trying to connect to the HMI application ...

***

***

***
JasonACT is offline   Reply With Quote Multi-Quote with this Post
Old 06-12-2019, 04:52 PM   #224
JasonACT
Away on leave
 
Join Date: Apr 2019
Location: ACT
Posts: 1,735
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

Looks like the flash chip isn't connected properly or has become corrupt. It actually had this output before I pressed down really hard on the chip and tried again.. This specifically says error reading the flash:

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:0E status 0xE8
..4-bit ECC error block:page 0x0008:24 status 0xE8
4-bit ECC error block:page 0x0008:2D status 0xE8
.4-bit ECC error block:page 0x0008:34 status 0xE8
...4-bit ECC error block:page 0x0009:24 status 0xE8
.4-bit ECC error block:page 0x0009:39 status 0xE8
..4-bit ECC error block:page 0x000A:1D status 0xE8
.4-bit ECC error block:page 0x000A:2B status 0xE8
...4-bit ECC error block:page 0x000B:1D status 0xE8
.4-bit ECC error block:page 0x000B:23 status 0xE8
...4-bit ECC error block:page 0x000C:19 status 0xE8
..4-bit ECC error block:page 0x000C:32 status 0xE8
.4-bit ECC error block:page 0x000D:08 status 0xE8
.4-bit ECC error block:page 0x000D:16 status 0xE8
......4-bit ECC error block:page 0x000E:3A status 0xE8
..4-bit ECC error block:page 0x000F:1B status 0xE8
...4-bit ECC error block:page 0x0010:0A status 0xE8
4-bit ECC error block:page 0x0010:0F status 0xE8
......4-bit ECC error block:page 0x0011:2B status 0xE8
.4-bit ECC error block:page 0x0011:38 status 0xE8
....4-bit ECC error block:page 0x0012:36 status 0xE8
.4-bit ECC error block:page 0x0013:0D status 0xE8
.4-bit ECC error block:page 0x0013:1E status 0xE8
....4-bit ECC error block:page 0x0014:11 status 0xE8
4-bit ECC error block:page 0x0014:1F status 0xE8
...4-bit ECC error block:page 0x0015:02 status 0xE8
.4-bit ECC error block:page 0x0015:16 status 0xE8
4-bit ECC error block:page 0x0015:1A status 0xE8
........4-bit ECC error block:page 0x0017:20 status 0xE8
..4-bit ECC error block:page 0x0017:39 status 0xE8
4-bit ECC error block:page 0x0017:3C status 0xE8
.......4-bit ECC error block:page 0x0019:23 status 0xE8
4-bit ECC error block:page 0x0019:2B status 0xE8
.4-bit ECC error block:page 0x0019:3D status 0xE8
..4-bit ECC error block:page 0x001A:19 status 0xE8
.....4-bit ECC error block:page 0x001B:2C status 0xE8
....4-bit ECC error block:page 0x001C:2B status 0xE8
4-bit ECC error block:page 0x001C:2C status 0xE8
.4-bit ECC error block:page 0x001C:3D status 0xE8
....4-bit ECC error block:page 0x001D:33 status 0xE8
4-bit ECC error block:page 0x001D:37 status 0xE8
....4-bit ECC error block:page 0x001E:37 status 0xE8
..4-bit ECC error block:page 0x001F:15 status 0xE8
.4-bit ECC error block:page 0x001F:22 status 0xE8
4-bit ECC error block:page 0x001F:2B status 0xE8
.4-bit ECC error block:page 0x001F:39 status 0xE8
.4-bit ECC error block:page 0x0020:07 status 0xE8
4-bit ECC error block:page 0x0020:0B status 0xE8
....4-bit ECC error block:page 0x0021:0A status 0xE8
4-bit ECC error block:page 0x0021:0F 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
fs-etfs-swsa_2048: devio_readtrans: ECCERR ecc cluster 16533 (e8)

***
fs-etfs-swsa_2048: devio_readcluster: ECCERR cluster 16533 (0xe8)
fs-etfs-swsa_2048: devio_readcluster: ECCERR cluster 16562 (0xe8)
fs-etfs-swsa_2048: Validating duplicate sequence 3117.
fs-etfs-swsa_2048: Validating duplicate sequence 3117.

***
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.

265106
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 application_power.c@184 0:. 00000000P0osw:e rHam: Smtaanratgeedr: n(o5277947220t)
r0uStarting [32;1mswsa_binaries_and_libraries[m
.n0n15999840isn:g Ham: (L/dev/swsa_pmmo)g. tWiamietsitnagm.p. .s
tarted:1970/01/01 00:00:05:293947060
0.088999110s: Ham: Creating guardian
0.099999000s: Ham: Dumper Died -1
0.102998970s: Ham: New Dumper Pid 368667
0.123998760s: Ham: Attach request from Guardian Pid 372764
DEBUG1 devc-sermx[ 3]ham_startup_thread ham_framework.c@85 : Attached 'ser3' to ham
DEBUG1 devc-sermx[ 3]ham_startup_thread ham_framework.c@99 : Added condition 'DEATH'
DEBUG1 devc-sermx[ 3]ham_startup_thread Creating SDMA Infrastructure...
ham_framework.c@132 : Added action 'RESTART'
CRITICAL wm8580a-co[ 4]powerManagerThread application_power.c@184 : Power manager not running (/dev/swsa_pmm). Waiting...
# mon imtoonri tdevc-sermxo[r 2devc-sermx][ApiPowerRun 2 ] ApiPowerRunapplication_power.c @ 128 application_power.c @:128 E n:t eErnitnegr
in g
DEB UmGo1n idevc-sermxt[o r3 ]devc-sermxham_startup_thread[ 2 ]ham_framework.cApiPowerRun@ 85 application_power.c:@ 136A t t:ac hEexdi t'iser1n'g
to mhoanmi
to rm odevc-sermxn[i t3o]rdrv_pmd_connect devc-sermx [ application_power.c2@]483ApiPowerRun : application_power.cE@n136t er i:n gE
x i tDiEnBgU
G1 mdevc-sermxo[n i3t]odrv_pmd_connectr devc-sermx [application_power.c @5487] drv_pmd_connect : aapplication_power.ct@t483a c h: tEon tPeorwienrg
Ma n aDgEeBrU Gp1a tdevc-sermxh[ '3/dev/swsa_pmm/ser3]'ham_startup_thread
ham_framework.cD@E99B U G:2 Adevc-sermxd[d e3d] drv_pmd_connectc o n dapplication_power.ci@t509i o n: ''/dev/swsa_pmm/ser3D'E AiTsH 'n
ow oDpEeBnU Go1n cdevc-sermxe[
5m]odrv_pmd_connectn i t oapplication_power.cr@ 487devc-sermx [ :3 ]adrv_pmd_connectt t a capplication_power.ch@ 512t o :P oEwxeirt iMnagn
a gmeorn iptaotrh devc-sermx'[/dev/swsa_pmm/ser1 '3
]drv_pmd_init D Eapplication_power.cB@U257G 1 :devc-sermx [E n3t]eham_startup_threadr i n gham_framework.c
@ 132 :U SAEdRd edevc-sermxd[ a3c]tdrv_pmd_initi o n application_power.c @'290R E S:T ARReTg'i
st e rDiEnBgU Gw2i tdevc-sermxh[ P5o]wdrv_pmd_connecte r Mapplication_power.co@d509e M:a n'a/dev/swsa_pmm/ser1g'e ri s( CnOoIwD :o p1073741834e,n Eovnecnet
: m0oxn4i,t otri mdevc-sermxe[o u5t]:drv_pmd_connect 10000 )
application_power.c@ 512m o n:i tEoxri tdevc-sermxi[n g3
] drv_pmd_initm o n iapplication_power.ct@o310r devc-sermx:[ E5x]idrv_pmd_initt i n gapplication_power.c
@ 257 D E:B UEGn2t edevc-sermxr[i n3g]
powerManagerThread application_power.cU@S205E R :devc-sermx [I n5i]tdrv_pmd_initi a l application_power.cP@o290w e r: RMeogdies t-e rAicntgi vwei
t h DPEoBwUeGr2 Mdevc-sermxo[d e3 ]Mpower_init_callbacka n a gpowerManager.ce@r136 ( C:O ISDt:a r1073741851t,e dE vienn ta:c t0ixv4e, mtoidmee.o
ut: 10000)
monitor devc-sermx[ 5]drv_pmd_init application_power.c@310 : Exiting
DEBUG2 devc-sermx[ 5]powerManagerThread application_power.c@205 : Initial Power Mode - Active
DEBUG2 devc-sermx[ 5]power_init_callback powerManager.c@136 : Started in active mode.

***
Starting [32;1mbluetooth[m
monitor devc-sermx[ 2]ApiPowerRun application_power.c@128 : Entering
DEBUG1 devc-sermx[ 3]ham_startup_thread ham_framework.c@85 : Attached 'ser2' to ham
moStarting [32;1mmedia_player[m
nitor devc-sermx[ 2]ApiPowerRun application_power.c@136 : Exiting
monitor devc-sermx[ 5]drv_pmd_connect application_power.c@483 : Entering
DEBUG1 devc-sermx[ 3]ham_startup_thread ham_framework.c@99 : Added condition 'DEATH'
DEBUG1 devc-sermx[ 5]drv_pmd_connect application_power.c@487 : attach to Power Manager path '/dev/swsa_pmm/ser2'
DEBUG1 devc-sermx[ 3]ham_startup_thread ham_framework.c@132 : Added actunknown symbol: iPtUnrealizeWadgeto
n 'unknown symbol: RPtGetRe3ourcesE
Sunknown symbol: Tpthread_-utex_lockA
RTunknown symbol: '3trncpy

unknown symbol: pSetCanvas
Dunknown symbol: Epp_d_freeB
UG2 devc-sermxunknown symbol: [PgCreatESurface
5unknown symbol: ]pthread[mutex_unlockdrv_pmd_connect
unknown symbol: P$LockCurrentDCapplication_power.c
@509 : ldd:FATAL: 'Could not resolve all symbols /dev/swsa_pmm/ser2
' is now open once
monitor devc-sermx[ 5]drv_pmd_connect application_power.c@512 : Exiting
monitor devc-sermx[ 5]drv_pmd_init application_power.c@257 : Entering
USER devc-sermx[ 5]drv_pmd_init application_power.c@290 : Registering with Power Mode Manager (COID: 1073741829, Event: 0x4, timeout: 10000)
monitor devc-sermx[ 5]drv_pmd_init application_power.c@310 : Exiting
DEBUG2 devc-sermx[ 5]powerManagerThread application_power.c@205 : Initial Power Mode - Active
DEBUG2 devc-sermx[ 5]power_init_callback powerManager.c@136 : Started in active mode.

***

***
unknown symbol: PtUnrealizeWadget
unknown symbol: PtGetRe3ources
unknown symbol: pthread_-utex_lock
unknown symbol: 3trncpy
unknown symbol: pSetCanvas
unknown symbol: pp_d_free
unknown symbol: PgCreatESurface
unknown symbol: pthread[mutex_unlock
unknown symbol: P$LockCurrentDC
ldd:FATAL: Could not resolve all symbols
Starting [32;1mgraphics[m
Setting up display for 3.50 Mid/High Series (47Hz)
Starting [32;1mhmi[m
Starting [32;1mapplications[m
fs-etfs-swsa_2048: devio_readcluster: ECCERR cluster 10757 (0xe8)
Starting [32;1mdiagnostics[m
unknown symbol: PtUnrealizeWadget
unknown symbol: PtGetRe3ources
unknown symbol: pthread_-utex_lock
unknown symbol: 3trncpy
unknown symbol: pSetCanvas
unknown symbol: pp_d_free
unknown symbol: PgCreatESurface
unknown symbol: pthread[mutex_unlock
unknown symbol: P$LockCurrentDC
ldd:FATAL: Could not resolve all symbols
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

***

***
ERROR hmi[ 3]dp_writeStringValue dp_basic.c@1738 : ERROR :: CLASS_DP :: COMPONENT_DP_SERVER :: dp_writeStringValue - id:6 is not a string property, string:USB UPDATE -> SUCCESS

Startup completed.

fs-etfs-swsa_2048: devio_readcluster: ECCERR cluster 10757 (0xe8)

***

***

***

***

***
Trying to connect to the HMI application ...
fs-etfs-swsa_2048: devio_readcluster: ECCERR cluster 16558 (0xe8)
fs-etfs-swsa_2048: devio_readcluster: ECCERR cluster 16551 (0xe8)

***

***

***

***

***
fs-etfs-swsa_2048: devio_readcluster: ECCERR cluster 32859 (0xe8)

***

***

***

***

***

***

***

***

***

***
fs-etfs-swsa_2048: devio_readcluster: ECCERR cluster 33232 (0xe8)

***

***

***

***

***

***

***

***

***

***

***

***

***

***

***
fs-etfs-swsa_2048: devio_readcluster: ECCERR cluster 16551 (0xe8)

***
JasonACT is offline   Reply With Quote Multi-Quote with this Post
Old 06-12-2019, 05:28 PM   #225
ozpacman
FF.Com.Au Hardcore
 
Join Date: May 2011
Location: Trinity Beach FNQ
Posts: 807
Default Re: FORD technical service bulletin : ICC touch screen display

Mmmm.

I think I just realised how dumb I am!
ozpacman is offline   Reply With Quote Multi-Quote with this Post
This user likes this post:
Old 06-12-2019, 05:56 PM   #226
JasonACT
Away on leave
 
Join Date: Apr 2019
Location: ACT
Posts: 1,735
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

Having given it some thought now, my best guess is there's a common DLL being loaded by various programs.. I think that one file has become corrupt..

Starting [32;1mdiagnostics[m
unknown symbol: PtUnrealizeWadget
unknown symbol: PtGetRe3ources
unknown symbol: pthread_-utex_lock
unknown symbol: 3trncpy

The names in the common DLL should be:

PtUnrealizeWidget
PtGetResources
pthread_mutex_lock
strncpy

If I'm right, multiple programs attempted to load the DLL and failed with the same problem. The "program loader" (part of the operating system) can't find the corrupt names in the database of other loaded DLLs and so the programs don't load properly.

Since it's common, it was probably being loaded/read by some other program, perhaps one that is loaded every so often and finishes before it all repeats again a bit later, but at the same time the car was used to jump start another. The power spike may have caused the "flash memory read" to become an unfortunate alteration operation instead.

If enough of the OS is still working (which it seems to be in this case) Ford might be able to re-flash the firmware and make it all better again

There was still the problem of the USB chip being busted, which is important for reflashing the firmware (oh, but not on this unit anymore!)... Ford - where's my firmware file to fix this ICC?!

Last edited by JasonACT; 06-12-2019 at 06:01 PM. Reason: If you're going to jumpstart another car, make sure your FGII is totally off.
JasonACT is offline   Reply With Quote Multi-Quote with this Post
2 users like this post:
Old 06-12-2019, 06:31 PM   #227
raceteam
FF.Com.Au Hardcore
 
Join Date: Nov 2013
Posts: 2,037
Default Re: FORD technical service bulletin : ICC touch screen display

Very interesting. That fits with what I'd been told about them sometimes being recoverable with a firmware flash.
raceteam is offline   Reply With Quote Multi-Quote with this Post
2 users like this post:
Old 06-12-2019, 07:26 PM   #228
JasonACT
Away on leave
 
Join Date: Apr 2019
Location: ACT
Posts: 1,735
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

Anyone who's got a broken ICC unit and wants to get a log out of it (if it's still working enough to do so) from CN9 pin 6 should know.. It's a 3.3v signal and runs at (like all the serial posts on this device) 115200,8,N,1 (8 bit, no parity, 1 stop bit).

I have one of these for programming some microcontrollers, you should resolder the power line from 5.0v to 3.3v (as described in the details on that page) however that's just for the red power wire which you don't need to use here:

https://www.ebay.com.au/itm/USB-to-T...i/201313271004

Since it's only the Rx (white) wire and ground (black) wire that you should connect to pin 6 (a Tx output line) and, say the grounded USB shield, it probably doesn't need to be reconfigured - even though I would still do it.

Then any terminal program for Windows should be able to output a log of what's going on with your ICC.

JasonACT is offline   Reply With Quote Multi-Quote with this Post
2 users like this post:
Old 06-12-2019, 08:58 PM   #229
JasonACT
Away on leave
 
Join Date: Apr 2019
Location: ACT
Posts: 1,735
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

Ha! Sorry, a bit of spam...

Took about 45 minutes to see how my home cinema subwoofer had failed (had replaced the fuse, but it still didn't work - though the new fuse didn't blow)...

Took two weeks for the part to come from China... I've had them (I've got one spare) now for about 3 days... But wasn't going to move onto the "next thing" until I was done here...









Took 45 minutes to cut out, clean up and solder in the new part.

It's now working again. 90 minutes. Happy with that. I have lost count of the minutes spent with this ICC!
JasonACT is offline   Reply With Quote Multi-Quote with this Post
This user likes this post:
Old 07-12-2019, 06:01 AM   #230
raceteam
FF.Com.Au Hardcore
 
Join Date: Nov 2013
Posts: 2,037
Default Re: FORD technical service bulletin : ICC touch screen display

Quote:
Originally Posted by JasonACT View Post
Happy with that. I have lost count of the minutes spent with this ICC!
It's hours of fun filled entertainment for the entire family!
raceteam is offline   Reply With Quote Multi-Quote with this Post
2 users like this post:
Old 21-12-2019, 02:47 PM   #231
JasonACT
Away on leave
 
Join Date: Apr 2019
Location: ACT
Posts: 1,735
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

Been on holiday for a bit, but since I've got a whole lot of things done now, I've come back to the broken unit for another play.

Actually, I had discovered a few things before putting it down. These units only load 1000 mp3s from USB. Previously I had written a script to add a 4 digit random number to my 8000 files on the 32GB stick and tried to play them sequentially rather than in random which I knew didn't work because of all the repeats. Got to song 999 and back to 1 again. Damn.

The 6 dip switches I added are also pretty useless (Version & what I though was the 8bit vs 16bit flash chip). Version does get read at boot time and these are what's reported:

0000 = 1.03 mid/high 30Hz
0001 = 2.01 mid/high 30Hz
0010 = 2.61 mid/high 30Hz
0011 = 3.00 mid/high 30Hz
0100 = 3.50 mid/high 47Hz <--- This is what we have
0101 = Unknown mid/high 30Hz
(All other switch positions say "Unknown")

Switching the other two dip switches didn't seem to do anything, both boards booted as before, I kind of expected mine to go into dual climate mode when changed because that's the other difference - but no.

Time to see if any of these other pins on (what I'm now calling) the service connector are serial input lines... Tested out a couple with a resistor to see if they are power or output lines, seems the two around the green serial log output wire I soldered in can easily be changed state... So inputs with a pull up resistor on the board...

Tried both with the TX serial output of my microcontroller, only this one responded: (pin 5)



I started to type "ls<enter>" over and over (Unix for show me the files!). I got the output below, "cd bin" then, I saw core_log so I typed cat to print it (ELF came up - so it's a compiled binary). I wonder if I can't mod my working unit, copy all the files onto a USB stick and transfer them back over to this broken board? Hmmm...


/Neutrino IPL for MCIMX31 SWSA FDM
NAND ID: 2C B1 80 55 ....4-bit ECC error block:page 0x0011:2B status 0xE8
.4-bit ECC error block:page 0x0011:38 status 0xE8
....4-bit ECC error block:page 0x0012:36 status 0xE8
..4-bit ECC error block:page 0x0013:1E status 0xE8
....4-bit ECC error block:page 0x0014:11 status 0xE8
4-bit ECC error block:page 0x0014:1F status 0xE8
...4-bit ECC error block:page 0x0015:02 status 0xE8
.4-bit ECC error block:page 0x0015:16 status 0xE8
4-bit ECC error block:page 0x0015:1A status 0xE8
........4-bit ECC error block:page 0x0017:20 status 0xE8
..4-bit ECC error block:page 0x0017:39 status 0xE8
4-bit ECC error block:page 0x0017:3C status 0xE8
.......4-bit ECC error block:page 0x0019:23 status 0xE8
4-bit ECC error block:page 0x0019:2B status 0xE8
.4-bit ECC error block:page 0x0019:3D status 0xE8
..4-bit ECC error block:page 0x001A:19 status 0xE8
.....4-bit ECC error block:page 0x001B:2C status 0xE8
....4-bit ECC error block:page 0x001C:2B status 0xE8
4-bit ECC error block:page 0x001C:2C status 0xE8
.4-bit ECC error block:page 0x001C:3D status 0xE8
....4-bit ECC error block:page 0x001D:33 status 0xE8
4-bit ECC error block:page 0x001D:37 status 0xE8
....4-bit ECC error block:page 0x001E:37 status 0xE8
..4-bit ECC error block:page 0x001F:15 status 0xE8
.4-bit ECC error block:page 0x001F:22 status 0xE8
4-bit ECC error block:page 0x001F:2B status 0xE8
.4-bit ECC error block:page 0x001F:39 status 0xE8
.4-bit ECC error block:page 0x0020:07 status 0xE8
4-bit ECC error block:page 0x0020:0B status 0xE8
....4-bit ECC error block:page 0x0021:0A status 0xE8
4-bit ECC error block:page 0x0021:0F 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
fs-etfs-swsa_2048: devio_readtrans: ECCERR ecc cluster 19840 (e8)
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.

265106
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 application_power.c@184 0:. 00000000P0osw:e rHam: Smtaanratgeedr: n(o5237947620t)
r0Starting [32;1mswsa_binaries_and_libraries[m
u.n0n15999840isn:g Ham: (L/dev/swsa_pmmo)g. tWiamietsitnagm.p. .s
tarted:1970/01/01 00:00:05:253947460
0.089999100s: Ham: Creating guardian
0.095999040s: Ham: Dumper Died -1
0.098999010s: Ham: New Dumper Pid 372762
0.124998750s: Ham: Attach request from Guardian Pid 372764
Creating SDMA Infrastructure...
DEBUG1 devc-sermx[ 3]ham_startup_thread ham_framework.c@85 : Attached 'ser3' to ham
DEBUG1 devc-sermx[ 3]ham_startup_thread ham_framework.c@99 : Added condition 'DEATH'
DEBUG1 devc-sermx[ 3]ham_startup_thread ham_framework.c@132 : Added action 'RESTART'
CRITICAL wm8580a-co[ 4]powerManagerThread application_power.c@184 : Power manager not running (/dev/swsa_pmm). Waiting...
# ls

.badblks bin etfsRoot packages tmp
.counts db fs proc usr
.filetable dev info sbin
.reserved etc lib scripts
# ls

.badblks bin etfsRoot packages tmp
.counts db fs proc usr
.filetable dev info sbin
.reserved etc lib scripts
# ls

.badblks bin etfsRoot packages tmp
.counts db fs proc usr
.filetable dev info sbin
.reserved etc lib scripts
# ls

.badblks bin etfsRoot packages tmp
.counts db fs proc usr
.filetable dev info sbin
.reserved etc lib scripts
# ls

.badblks bin etfsRoot packages tmp
.counts db fs proc usr
.filetable dev info sbin
.reserved etc lib scripts
# monitor devc-sermx[ 2]ApiPowerRun mapplication_power.co@n128i t o:r Edevc-sermxn[t e2r]iApiPowerRunn g
application_power.c @ 128D E B:U GE1n tdevc-sermxe[r i3n]gham_startup_thread
ham_framework.cm@o85n i t:o rA tdevc-sermxt[a c2h]eApiPowerRund ' ser1application_power.c'@ 136t o :h aEmx
it imnogn
it omro ndevc-sermxi[t o2r] ApiPowerRundevc-sermx [ 3application_power.c]@drv_pmd_connect136 :application_power.c @E483x i t:i nEgn
te rmionngi
t o rD Edevc-sermxB[U G51] drv_pmd_connectdevc-sermx [ 3application_power.c]@drv_pmd_connect483 :application_power.c @E487n t e:r iantgt
ac h DtEoB UPGo1w edevc-sermxr[ M3a]nham_startup_threada g e rham_framework.c @p99a t h: 'A/dev/swsa_pmm/ser3d'd
ed c oDnEdBiUtGi2o ndevc-sermx [ '3D]Edrv_pmd_connectA T H 'application_power.c
@509 D:E B'U/dev/swsa_pmm/ser3G'1 idevc-sermxs[ n5o]wdrv_pmd_connect o p eapplication_power.cn@ o487n c e:
amtotnaictho rt odevc-sermx [P o3w]edrv_pmd_connectr M aapplication_power.cn@a512g e r: pEaxtiht i'n/dev/swsa_pmm/ser1g'

m o nDiEtBoUrG 1devc-sermx [devc-sermx [3 ]3drv_pmd_init] ham_startup_thread application_power.c @ham_framework.c257@ 132 : :E nAtdedreidn ga
c t i o nU S E'RR Edevc-sermxS[T AR3T]'drv_pmd_init
application_power.cD@E290B U G:2 Rdevc-sermxe[g i5s]tdrv_pmd_connecte r i napplication_power.cg@ 509w i t:h 'P/dev/swsa_pmm/ser1o'w eirs Mnoodwe oMpaenna goencre
( CmOoInDi:t o1073741834r, devc-sermxE[v e5n]tdrv_pmd_connect: 0 xapplication_power.c4@,512 t i:m eEoxuitt:i n10000g)

m omnointiotro rdevc-sermx [devc-sermx [5 ]3drv_pmd_init] drv_pmd_init application_power.c @application_power.c257@ 310 : :E nEtxeirtiinngg

D EUBSUEGR2 devc-sermxdevc-sermx[[ 53]]drv_pmd_initpowerManagerThread application_power.capplication_power.c@@290205 :: RIengiitsitaelr iPnogw ewri tMho dPeo w-e rA cMtoidvee
M a nDaEgBeUrG 2( Cdevc-sermxO[I D3:] power_init_callback1073741851 , EpowerManager.cv@e136n t :: 0Sxt4a,r tteidm eionu ta:c t10000i)v
e mmoodnei.t
or devc-sermx[ 5]drv_pmd_init application_power.c@310 : Exiting
DEBUG2 devc-sermx[ 5]powerManagerThread application_power.c@205 : Initial Power Mode - Active
DEBUG2 devc-sermx[ 5]power_init_callback powerManager.c@136 : Started in active mode.
Starting [32;1mbluetooth[m
ls

.badblks bin etfsRoot packages tmp
.counts db fs proc usr
.filetable dev info sbin
.reserved etc lib scripts
# ls

monitor devc-sermx[ 2]ApiPowerRun application_power.c@128 : Enterin.badblks bin etfsRoot packages tmp
.counts db fs proc usr
.filetable dev info sbin
.reserved etc lib scripts
g
DEBUG1 devc-sermx[ 3]ham_startup_thread# ham_framework.c@85 : Attached 'ser2' to ham
Starting [32;1mmedia_player[m
monitor devc-sermx[ 2]ApiPowerRun application_power.c@136 : Exiting
monitor devc-sermx[ 5]drv_pmd_connect application_power.c@483 : Entering
DEBUG1 devc-sermx[ 3]ham_startup_thread ham_framework.c@99 : Added condition 'DEATH'
DEBUG1 devc-sermx[ 5]drv_pmd_connect application_power.c@487 : attach to Power Manager path '/dev/swsa_pmm/ser2'
DEBUG1 devc-sermx[ 3]ham_startup_thread ham_framework.c@132 : unknown symbol: APtUnrealizeWadgetd
ded unknown symbol: aPtGetRe3ourcesc
tunknown symbol: ipthread_-utex_locko
n unknown symbol: 3trncpy'
Runknown symbol: EpSetCanvasS
Tunknown symbol: App_d_freeR
T'
unknown symbol: PgCreatESurfaceD
Eunknown symbol: Bpthread[mutex_unlockU
G2unknown symbol: P$LockCurrentDCdevc-sermx
[ 5]drv_pmd_connect ldd:FATAL: Could not resolve all symbols
application_power.c@509 : '/dev/swsa_pmm/ser2' is now open once
monitor devc-sermx[ 5]drv_pmd_connect application_power.c@512 : Exiting
monitor devc-sermx[ 5]drv_pmd_init application_power.c@257 : Entering
USER devc-sermx[ 5]drv_pmd_init application_power.c@290 : Registering with Power Mode Manager (COID: 1073741829, Event: 0x4, timeout: 10000)
monitor devc-sermx[ 5]drv_pmd_init application_power.c@310 : Exiting
DEBUG2 devc-sermx[ 5]powerManagerThread application_power.c@205 : Initial Power Mode - Active
DEBUG2 devc-sermx[ 5]power_init_callback powerManager.c@136 : Started in active mode.
unknown symbol: PtUnrealizeWadget
unknown symbol: PtGetRe3ources
unknown symbol: pthread_-utex_lock
unknown symbol: 3trncpy
unknown symbol: pSetCanvas
unknown symbol: pp_d_free
unknown symbol: PgCreatESurface
unknown symbol: pthread[mutex_unlock
unknown symbol: P$LockCurrentDC
ldd:FATAL: Could not resolve all symbols
Starting [32;1mgraphics[m
Setting up display for 3.50 Mid/High Series (47Hz)
fs-etfs-swsa_2048: devio_readcluster: ECCERR cluster 19851 (0xe8)
Starting [32;1mhmi[m
Starting [32;1mapplications[m
Starting [32;1mdiagnostics[m
unknown symbol: PtUnrealizeWadget
unknown symbol: PtGetRe3ources
unknown symbol: pthread_-utex_lock
unknown symbol: 3trncpy
unknown symbol: pSetCanvas
unknown symbol: pp_d_free
unknown symbol: PgCreatESurface
unknown symbol: pthread[mutex_unlock
unknown symbol: P$LockCurrentDC
ldd:FATAL: Could not resolve all symbols
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
ERROR hmi[ 3]dp_writeStringValue dp_basic.c@1738 : ERROR :: CLASS_DP :: COMPONENT_DP_SERVER :: dp_writeStringValue - id:6 is not a string property, string:USB UPDATE -> SUCCESS

Startup completed.

Trying to connect to the HMI application ...
ls

.badblks bin etfsRoot packages tmp
.counts db fs proc usr
.filetable dev info sbin
.reserved etc lib scripts
# fs-etfs-swsa_2048: devio_readcluster: ECCERR cluster 19853 (0xe8)
cd bin

# ls

TMC_test devi-hid img_rotate
USB_RESET devi-hirun img_thn
VBus_ctl devi-tsc2007 pin_iomuxer
VLCDAdjust diagnostics powerScript
acm font-cache reversing-camera
bc5 hamctrl time_manager
bccmd him touch_2_hmi_connector
bcsp hmi usb-fault
bluetoothdfu i2c-imx31_swsa usb_dump_reg
bluetoothdiagnostics img_decode_mem vehicle_settings
bluetoothprofiles img_decode_simple wm8580a-control
buttons img_decode_surface
contrast img_encode
core_log img_resize
# fs-etfs-swsa_2048: devio_readcluster: ECCERR cluster 19853 (0xe8)
fs-etfs-swsa_2048: devio_readcluster: ECCERR cluster 19853 (0xe8)
fs-etfs-swsa_2048: devio_readcluster: ECCERR cluster 19853 (0xe8)
fs-etfs-swsa_2048: devio_readcluster: ECCERR cluster 19853 (0xe8)
fs-etfs-swsa_2048: devio_readcluster: ECCERR cluster 19853 (0xe8)
fs-etfs-swsa_2048: devio_readcluster: ECCERR cluster 19853 (0xe8)
cat core_log

ELFa(D
44 (444%%`%%/usr/lib/ldqnx.so.2QNX%0.$-' /%",*(#+
&
!)h( 1 '7F[jx"$'0$'('<HTh(`lxD

'
ah(j 0'P'h(N&
7
<
C,
'H8
libc.so.3_init_arraystrerroriofunc_attr_initerrno_ preinit_arrayresmgr_context_allocresmgr_handlerres mgr_attach__cxa_finalizeresmgr_blockwritefprintf__ get_errno_ptrdevctlprocmgr_daemon_init_libcmemsetm ain_fini_arrayiofunc_write_verifysprintfatexitdisp atch_create_Stderriofunc_func_initatoistrlenopencl osepthread_mutex_lockMsgSendvpthread_mutex_unlock_ _slog_mux_slogfd__stackavailvsnprintf_btext__data_ start_edata__bss_start__bss_start____bss_end____en d___end_stack'
'$'('0'$&&&&& &&&
&&
&&&&&&&&&&&& &!&"&#&'&(&)&*&+','/@--|tld\TLD<4,$@! 0<@-@P` t d \ ttL h ,0$0
%%8%%%% '
-`@`0@ LR
L0dD00 R
@00 R
-L
-L0MyP;
LAH`KHq [ 0 Q@Dl 0
0p@P p
@P'
2p #N@PD px>@P 0<H1 $,+'''`Qp0'D
-MLMP(KLK@D@D pp
d1` P01BK
HT/
[1@@K0@P101
0 P/O[T
T 1 @K0@PO0_o1T @P@K0 `@P @ |$
-0L@PP0SP0sPp`P0S`pv
XP b0H0TP00~'p
-Lp0M8K4 ,3K0[@P,`PP
0K5p@"0YSS0S
O1U0 P@Cp (K @@('$'
-LM<$1P_aA4P00(K00
c-!q
`
0p
0SPP
00<00 8K0p,
0@E0 00
0p
RP1_#0 0@`
--L 0K
-0-LM P RRAK AK 00 R 0K 8KP00,($@5K0z00
-L$MK 0K($0K
-D0D 0L q
@ 0B0q
-L@-%s: Unable to allocate dispatch handle.
/proc/dumper%s: Couldn't attach as /proc/dumper -- (%d)%s
%s: Couldn't become daemon.
block error
/proc/%d/asrun signal pid %d tid %d signal %d code %d ip %#llx %srun fault pid %d tid %d signal %d code %d ip %#llx %s mmu dfs %#x ifs %#x dfa %#xrun error pid %d tid %d why %d what %d ip %#llx %s/dev/slog
8 ||
|& | (%'%%GCC: (GNU) 4.3.3GCC: (GNU) 4.3.3GCC: (GNU) 4.3.3GCC: (GNU) 4.3.3Aaeabi$URL: http://svn/product/branches/6.4.1/tr...ic/sys/cdefs.h $ $Rev: 220008 $$URL: http://svn/product/branches/6.4.1/tr...b/c/inc/weak.h $ $Rev: 220008 $$URL: http://svn/product/branches/6.4.1/tr...tup/crtbegin.c $ $Rev: 217586 $$URL: http://svn/product/branches/6.4.1/tr...ic/sys/cdefs.h $ $Rev: 220008 $$URL: http://svn/product/branches/6.4.1/tr...b/c/inc/weak.h $ $Rev: 220008 $$URL: http://svn/product/branches/6.4.1/tr...artup/crtend.c $ $Rev: 217586 $.shstrtab.interp.note.hash.dynsym.dynstr.rel.dyn. rel.plt.init.text.fini.rodata.ctors.dtors.dynamic. got.data.bss.comment.ARM.attributes.ident \||'||/| | (8 A<GD
D
M88S2DDx[%b%i%r|&|w'} 'HHpd0tr# fs-etfs-swsa_2048: devio_readcluster: ECCERR cluster 19853 (0xe8)
fs-etfs-swsa_2048: devio_readcluster: ECCERR cluster 19853 (0xe8)
fs-etfs-swsa_2048: devio_readcluster: ECCERR cluster 19853 (0xe8)
fs-etfs-swsa_2048: devio_readcluster: ECCERR cluster 19853 (0xe8)
cd ..

# fs-etfs-swsa_2048: devio_readcluster: ECCERR cluster 19853 (0xe8)
ls

.badblks bin etfsRoot packages tmp
.counts db fs proc usr
.filetable dev info sbin
.reserved etc lib scripts
# fs-etfs-swsa_2048: devio_readcluster: ECCERR cluster 19853 (0xe8)
fs-etfs-swsa_2048: devio_readcluster: ECCERR cluster 19853 (0xe8)
fs-etfs-swsa_2048: devio_readcluster: ECCERR cluster 19853 (0xe8)
cd info

# fs-etfs-swsa_2048: devio_readcluster: ECCERR cluster 34477 (0xe8)
ls

applications io
bluetooth iplspl
core-pkg media_player
diagnostics power
fast_startup qnx_binaries_and_libraries
graphics swsa_binaries_and_libraries
hmi
# fs-etfs-swsa_2048: devio_readcluster: ECCERR cluster 19853 (0xe8)
fs-etfs-swsa_2048: devio_readcluster: ECCERR cluster 19853 (0xe8)
ls -l

total 13
lrwxrwxrwx 1 root 0 35 Jan 01 1970 applications -> /packages/factory/applications/info
lrwxrwxrwx 1 root 0 32 Jan 01 1970 bluetooth -> /packages/factory/bluetooth/info
lrwxrwxrwx 1 root 0 31 Jan 01 1970 core-pkg -> /packages/factory/core-pkg/info
lrwxrwxrwx 1 root 0 34 Jan 01 1970 diagnostics -> /packages/factory/diagnostics/info
lrwxrwxrwx 1 root 0 35 Jan 01 1970 fast_startup -> /packages/factory/fast_startup/info
lrwxrwxrwx 1 root 0 31 Jan 01 1970 graphics -> /packages/factory/graphics/info
lrwxrwxrwx 1 root 0 26 Jan 01 1970 hmi -> /packages/factory/hmi/info
lrwxrwxrwx 1 root 0 25 Jan 01 1970 io -> /packages/factory/io/info
lrwxrwxrwx 1 root 0 29 Jan 01 1970 iplspl -> /packages/factory/iplspl/info
lrwxrwxrwx 1 root 0 35 Jan 01 1970 media_player -> /packages/factory/media_player/info
lrwxrwxrwx 1 root 0 28 Jan 01 1970 power -> /packages/factory/power/info
lrwxrwxrwx 1 root 0 49 Jan 01 1970 qnx_binaries_and_libraries -> /packages/factory/qnx_binaries_and_libraries/info
lrwxrwxrwx 1 root 0 50 Jan 01 1970 swsa_binaries_and_libraries -> /packages/factory/swsa_binaries_and_libraries/info
# fs-etfs-swsa_2048: devio_readcluster: ECCERR cluster 19853 (0xe8)
JasonACT is offline   Reply With Quote Multi-Quote with this Post
3 users like this post:
Old 21-12-2019, 09:21 PM   #232
JasonACT
Away on leave
 
Join Date: Apr 2019
Location: ACT
Posts: 1,735
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

Sadly, the broken unit's USB software is getting the bad flash-chip data problem with loading dlls. So even though the hardware is working, it won't mount a USB stick.

My working unit however is fine, it mounts sticks as readonly though - so you need to "mount -uw /fs/usb0" (had problems with this at first, said it couldn't do it because it may be read only - yeah, that's what I'm trying to fix!) or "mount -uw /dev/hd0" (maybe doing this one helped with that problem? Dunno, I just run both now - same device)...

Got about 8255 files which come to 101MB off my working screen, found these 2 files (largest pictures when I did a search):





I need to remember to "mount -ur ..." to put it back as read only before I pull out the stick, but the "shutdown" command also works - nice, shuts down the unix os at which point it reboots (where I can pull out the stick before it is re-scanned).

I guess I really need to pull apart my spare GPS screen and dump it - see what extras it has.

I was also able to write to files on the screen (I attempted to change the usb_mode.conf file to say "RW" instead of "RO" - which I could do easily enough - but it still didn't mount the stick as read/write even after a reboot).

Gosh it's been smokey here in Canberra.
JasonACT is offline   Reply With Quote Multi-Quote with this Post
2 users like this post:
Old 21-12-2019, 11:02 PM   #233
Citroënbender
DIY Tragic
 
Citroënbender's Avatar
 
Join Date: Apr 2018
Location: Sydney, more than not. I hate it.
Posts: 22,592
Chairman's Award: Chairman's Award - Issue reason: Your outstanding contributions to this community have not gone unnoticed. IN my view you are a worthy recipient of the (rarely used) Chairman's Award. 
Default Re: FORD technical service bulletin : ICC touch screen display

Again, thank you.

I really appreciate the “instalment” format of your investigations. It’s like the old serial publications where you learned how to build a model or instrument over several months.
Citroënbender is online now   Reply With Quote Multi-Quote with this Post
This user likes this post:
Old 22-12-2019, 12:41 AM   #234
JasonACT
Away on leave
 
Join Date: Apr 2019
Location: ACT
Posts: 1,735
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 guess I should document my basic unix knowledge (I'm a DOS guy since I was 16, went to uni and became an expert in unix, went to work and forgot it all except for "man" for manuals)...

mount -uw /fs/usb0
mount -uw /dev/hd0
mount -uw /fs/usb0

cd fs/usb0

cp -LR /etfsRoot .
cp -LR /packages .
cp -LR /proc .

"-LR" is meant to copy symbolic links if needed as well as recursive directories (you get warnings though with the links here - they don't copy - but I kept a record anyway). DOS has no concept of sym links - I would normally just accept a 2nd copy of the file, but this QNX install doesn't seem to want to agree with me.

If the unit mostly boots correctly these 2 too, but you don't get any files, they seem to be inter-process file handles for cross process comms...

cp -LR /hmi .
cp -LR /hmi_ .

(then..)

shutdown

---

The sym link errors I saw were these (so if needed, I can reconstruct the links - though looking in some of the shell scripts I've extracted, there's a file to do it all anyway???) The "as" files are empty - not sure what the issue is there, but I don't think that's a problem - maybe they were "open" at the time.

I've also found the main "boot" script which also says mount USB sticks as read-only, so that's probably the place I need to change to get easier access - but I'd rather not mess with the working unit if I don't need to. New SAT-NAV maps on the other hand... Well, it might be time to start looking for some files on the web.

cp -R: Can't create symbolic link ./etfsRoot/db/qdb_mme.cfg --> /packages/factory/media_player/root/db/qdb_mme.cfg (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/db/mmgui.sql --> /packages/factory/media_player/root/db/mmgui.sql (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/db/mme_temp.sql --> /packages/factory/media_player/root/db/mme_temp.sql (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/db/mme_library.sql --> /packages/factory/media_player/root/db/mme_library.sql (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/db/mme_data.sql --> /packages/factory/media_player/root/db/mme_data.sql (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/db/mme_custom.sql --> /packages/factory/media_player/root/db/mme_custom.sql (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/db/mme_connect.sql --> /packages/factory/media_player/root/db/mme_connect.sql (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/db/mme.sql --> /packages/factory/media_player/root/db/mme.sql (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/db/media-player.sql --> /packages/factory/media_player/root/db/media-player.sql (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/sbin/qdb --> /packages/factory/qnx_binaries_and_libraries/root/usr/sbin/qdb (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/sbin/mme-generic --> /packages/factory/qnx_binaries_and_libraries/root/usr/sbin/mme-generic (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/sbin/mcd --> /packages/factory/qnx_binaries_and_libraries/root/usr/sbin/mcd (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/sbin/io-media-generic --> /packages/factory/qnx_binaries_and_libraries/root/usr/sbin/io-media-generic (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/sbin/io-fs-media --> /packages/factory/qnx_binaries_and_libraries/root/usr/sbin/io-fs-media (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/sbin/fileset --> /packages/factory/qnx_binaries_and_libraries/root/usr/sbin/fileset (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/photon/keyboard/en_US_101.kbd --> /packages/factory/qnx_binaries_and_libraries/root/usr/photon/keyboard/en_US_101.kbd (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/photon/font_repository/tt2011m_.ttf --> /packages/factory/qnx_binaries_and_libraries/root/usr/photon/font_repository/tt2011m_.ttf (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/photon/font_repository/tt2009m_.ttf --> /packages/factory/qnx_binaries_and_libraries/root/usr/photon/font_repository/tt2009m_.ttf (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/photon/font_repository/tt2004m_.ttf --> /packages/factory/qnx_binaries_and_libraries/root/usr/photon/font_repository/tt2004m_.ttf (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/photon/font_repository/tt2003m_.ttf --> /packages/factory/qnx_binaries_and_libraries/root/usr/photon/font_repository/tt2003m_.ttf (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/photon/font_repository/tt2002m_.ttf --> /packages/factory/qnx_binaries_and_libraries/root/usr/photon/font_repository/tt2002m_.ttf (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/photon/font_repository/tt2001m_.ttf --> /packages/factory/qnx_binaries_and_libraries/root/usr/photon/font_repository/tt2001m_.ttf (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/photon/font_repository/tt0582m_.ttf --> /packages/factory/qnx_binaries_and_libraries/root/usr/photon/font_repository/tt0582m_.ttf (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/photon/font_repository/tt0419m_.ttf --> /packages/factory/qnx_binaries_and_libraries/root/usr/photon/font_repository/tt0419m_.ttf (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/photon/font_repository/tt0014m_.ttf --> /packages/factory/qnx_binaries_and_libraries/root/usr/photon/font_repository/tt0014m_.ttf (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/photon/font_repository/tt0013m_.ttf --> /packages/factory/qnx_binaries_and_libraries/root/usr/photon/font_repository/tt0013m_.ttf (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/photon/font_repository/tt0012m_.ttf --> /packages/factory/qnx_binaries_and_libraries/root/usr/photon/font_repository/tt0012m_.ttf (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/photon/font_repository/tt0011m_.ttf --> /packages/factory/qnx_binaries_and_libraries/root/usr/photon/font_repository/tt0011m_.ttf (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/photon/font_repository/tt0006m_.ttf --> /packages/factory/qnx_binaries_and_libraries/root/usr/photon/font_repository/tt0006m_.ttf (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/photon/font_repository/tt0005m_.ttf --> /packages/factory/qnx_binaries_and_libraries/root/usr/photon/font_repository/tt0005m_.ttf (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/photon/font_repository/tt0004m_.ttf --> /packages/factory/qnx_binaries_and_libraries/root/usr/photon/font_repository/tt0004m_.ttf (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/photon/font_repository/tt0003m_.ttf --> /packages/factory/qnx_binaries_and_libraries/root/usr/photon/font_repository/tt0003m_.ttf (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/photon/font_repository/phcursor.phf --> /packages/factory/qnx_binaries_and_libraries/root/usr/photon/font_repository/phcursor.phf (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/photon/font_repository/fontopts --> /packages/factory/qnx_binaries_and_libraries/root/usr/photon/font_repository/fontopts (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/photon/config/pterm.rc --> /packages/factory/qnx_binaries_and_libraries/root/usr/photon/config/pterm.rc (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/photon/bin/phfont --> /packages/factory/qnx_binaries_and_libraries/root/usr/photon/bin/phfont (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/lib/libxml2.so.1 --> /packages/factory/qnx_binaries_and_libraries/root/usr/lib/libxml2.so.1 (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/lib/libusbdi.so.2 --> /packages/factory/qnx_binaries_and_libraries/root/usr/lib/libusbdi.so.2 (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/lib/libsqlite3.so.1 --> /packages/factory/qnx_binaries_and_libraries/root/usr/lib/libsqlite3.so.1 (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/lib/libqdb.so.1 --> /packages/factory/qnx_binaries_and_libraries/root/usr/lib/libqdb.so.1 (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/lib/libmmfilter.so.1 --> /packages/factory/qnx_binaries_and_libraries/root/usr/lib/libmmfilter.so.1 (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/lib/libmmedia.so.1 --> /packages/factory/qnx_binaries_and_libraries/root/usr/lib/libmmedia.so.1 (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/lib/libmme.so.1 --> /packages/factory/qnx_binaries_and_libraries/root/usr/lib/libmme.so.1 (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/lib/libhiddi.so.1 --> /packages/factory/qnx_binaries_and_libraries/root/usr/lib/libhiddi.so.1 (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/lib/libham.so.2 --> /packages/factory/qnx_binaries_and_libraries/root/usr/lib/libham.so.2 (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/lib/libaoi.so.1 --> /packages/factory/qnx_binaries_and_libraries/root/usr/lib/libaoi.so.1 (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/lib/libaoi.so --> /packages/factory/qnx_binaries_and_libraries/root/usr/lib/libaoi.so (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/lib/libWFD.so.1 --> /packages/factory/qnx_binaries_and_libraries/root/usr/lib/libWFD.so.1 (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/lib/libKD.so.1 --> /packages/factory/qnx_binaries_and_libraries/root/usr/lib/libKD.so.1 (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/lib/libGLESv1_CM.so.1 --> /packages/factory/qnx_binaries_and_libraries/root/usr/lib/libGLESv1_CM.so.1 (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/lib/libEGL.so.1 --> /packages/factory/qnx_binaries_and_libraries/root/usr/lib/libEGL.so.1 (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/bin/wave --> /packages/factory/qnx_binaries_and_libraries/root/usr/bin/wave (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/bin/use --> /packages/factory/qnx_binaries_and_libraries/root/usr/bin/use (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/bin/touch --> /packages/factory/qnx_binaries_and_libraries/root/usr/bin/touch (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/bin/time --> /packages/factory/qnx_binaries_and_libraries/root/usr/bin/time (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/bin/testapp-cmdline --> /packages/factory/qnx_binaries_and_libraries/root/usr/bin/testapp-cmdline (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/bin/renice --> /packages/factory/qnx_binaries_and_libraries/root/usr/bin/renice (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/bin/qdbc --> /packages/factory/qnx_binaries_and_libraries/root/usr/bin/qdbc (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/bin/priorityfolder --> /packages/factory/qnx_binaries_and_libraries/root/usr/bin/priorityfolder (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/bin/nice --> /packages/factory/qnx_binaries_and_libraries/root/usr/bin/nice (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/bin/mmplexplore --> /packages/factory/qnx_binaries_and_libraries/root/usr/bin/mmplexplore (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/bin/mmexplore --> /packages/factory/qnx_binaries_and_libraries/root/usr/bin/mmexplore (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/bin/mmecli --> /packages/factory/qnx_binaries_and_libraries/root/usr/bin/mmecli (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/bin/mmebrowse --> /packages/factory/qnx_binaries_and_libraries/root/usr/bin/mmebrowse (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/bin/gf-calib --> /packages/factory/qnx_binaries_and_libraries/root/usr/bin/gf-calib (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/bin/date --> /packages/factory/qnx_binaries_and_libraries/root/usr/bin/date (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/bin/media-player --> /packages/factory/media_player/root/usr/bin/media-player (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/bin/ipod-umass_swsa --> /packages/factory/media_player/root/usr/bin/ipod-umass_swsa (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/bin/aviage_monitor --> /packages/factory/media_player/root/usr/bin/aviage_monitor (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/usr/hmi --> /packages/factory/hmi/root_dir/usr/hmi (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/sbin/wm8580a-control-manager --> /packages/factory/swsa_binaries_and_libraries/root/sbin/wm8580a-control-manager (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/sbin/spi-master --> /packages/factory/swsa_binaries_and_libraries/root/sbin/spi-master (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/sbin/mx31_dma_cfg --> /packages/factory/swsa_binaries_and_libraries/root/sbin/mx31_dma_cfg (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/sbin/mqueue --> /packages/factory/qnx_binaries_and_libraries/root/sbin/mqueue (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/sbin/io-hid --> /packages/factory/qnx_binaries_and_libraries/root/sbin/io-hid (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/sbin/io-display --> /packages/factory/qnx_binaries_and_libraries/root/sbin/io-display (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/sbin/io-audio --> /packages/factory/qnx_binaries_and_libraries/root/sbin/io-audio (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/sbin/fs-etfs-ram --> /packages/factory/qnx_binaries_and_libraries/root/sbin/fs-etfs-ram (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/sbin/enum-devices --> /packages/factory/qnx_binaries_and_libraries/root/sbin/enum-devices (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/sbin/devu-mouse --> /packages/factory/qnx_binaries_and_libraries/root/sbin/devu-mouse (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/sbin/devu-kbd --> /packages/factory/qnx_binaries_and_libraries/root/sbin/devu-kbd (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/sbin/pmm --> /packages/factory/power/root/sbin/pmm (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/sbin/pwm --> /packages/factory/graphics/root/sbin/pwm (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/sbin/lcd_refresh --> /packages/factory/graphics/root/sbin/lcd_refresh (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/sbin/backlight --> /packages/factory/graphics/root/sbin/backlight (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/libdma-imx31v2.so --> /packages/factory/swsa_binaries_and_libraries/root/lib/libdma-imx31v2.so (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/libz.so.2 --> /packages/factory/qnx_binaries_and_libraries/root/lib/libz.so.2 (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/libsocket.so.2 --> /packages/factory/qnx_binaries_and_libraries/root/lib/libsocket.so.2 (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/libph.so.3 --> /packages/factory/qnx_binaries_and_libraries/root/lib/libph.so.3 (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/libm.so.2 --> /packages/factory/qnx_binaries_and_libraries/root/lib/libm.so.2 (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/libm-vfp.so.2 --> /packages/factory/qnx_binaries_and_libraries/root/lib/libm-vfp.so.2 (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/libimg.so.1 --> /packages/factory/qnx_binaries_and_libraries/root/lib/libimg.so.1 (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/libgf.so.1 --> /packages/factory/qnx_binaries_and_libraries/root/lib/libgf.so.1 (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/libfontutils.so.1 --> /packages/factory/qnx_binaries_and_libraries/root/lib/libfontutils.so.1 (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/libfont.so.1 --> /packages/factory/qnx_binaries_and_libraries/root/lib/libfont.so.1 (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/libfont.so --> /packages/factory/qnx_binaries_and_libraries/root/lib/libfont.so (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/libffb.so.2 --> /packages/factory/qnx_binaries_and_libraries/root/lib/libffb.so.2 (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/libcpp.so.4 --> /packages/factory/qnx_binaries_and_libraries/root/lib/libcpp.so.4 (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/libc.so.2 --> /packages/factory/qnx_binaries_and_libraries/root/lib/libc.so.2 (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/libblkcache.so --> /packages/factory/qnx_binaries_and_libraries/root/lib/libblkcache.so (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/libasound.so.2 --> /packages/factory/qnx_binaries_and_libraries/root/lib/libasound.so.2 (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/libasound.so --> /packages/factory/qnx_binaries_and_libraries/root/lib/libasound.so (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/libGLES_CM.so.1 --> /packages/factory/qnx_binaries_and_libraries/root/lib/libGLES_CM.so.1 (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/libGLES_CL.so.1 --> /packages/factory/qnx_binaries_and_libraries/root/lib/libGLES_CL.so.1 (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/dll/spi-imx31_swsa.so --> /packages/factory/swsa_binaries_and_libraries/root/lib/dll/spi-imx31_swsa.so (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/dll/deva-ctrl-stereo.so --> /packages/factory/swsa_binaries_and_libraries/root/lib/dll/deva-ctrl-stereo.so (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/dll/deva-ctrl-mono.so --> /packages/factory/swsa_binaries_and_libraries/root/lib/dll/deva-ctrl-mono.so (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/dll/phfont.so --> /packages/factory/qnx_binaries_and_libraries/root/lib/dll/phfont.so (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/dll/mme-imgprc-gf.so --> /packages/factory/qnx_binaries_and_libraries/root/lib/dll/mme-imgprc-gf.so (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/dll/iofs-usb-ipod.so --> /packages/factory/qnx_binaries_and_libraries/root/lib/dll/iofs-usb-ipod.so (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/dll/iofs-ipod.so --> /packages/factory/qnx_binaries_and_libraries/root/lib/dll/iofs-ipod.so (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/dll/iofs-i2c-ipod.so --> /packages/factory/qnx_binaries_and_libraries/root/lib/dll/iofs-i2c-ipod.so (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/dll/img_codec_tga.so --> /packages/factory/qnx_binaries_and_libraries/root/lib/dll/img_codec_tga.so (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/dll/img_codec_sgi.so --> /packages/factory/qnx_binaries_and_libraries/root/lib/dll/img_codec_sgi.so (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/dll/img_codec_png.so --> /packages/factory/qnx_binaries_and_libraries/root/lib/dll/img_codec_png.so (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/dll/img_codec_pcx.so --> /packages/factory/qnx_binaries_and_libraries/root/lib/dll/img_codec_pcx.so (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/dll/img_codec_jpg.so --> /packages/factory/qnx_binaries_and_libraries/root/lib/dll/img_codec_jpg.so (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/dll/img_codec_gif.so --> /packages/factory/qnx_binaries_and_libraries/root/lib/dll/img_codec_gif.so (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/dll/img_codec_bmp.so --> /packages/factory/qnx_binaries_and_libraries/root/lib/dll/img_codec_bmp.so (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/dll/fs-nt.so --> /packages/factory/qnx_binaries_and_libraries/root/lib/dll/fs-nt.so (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/dll/devh-usb.so --> /packages/factory/qnx_binaries_and_libraries/root/lib/dll/devh-usb.so (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/dll/devg-soft3d.so --> /packages/factory/qnx_binaries_and_libraries/root/lib/dll/devg-soft3d.so (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/dll/devg-soft3d-fixed.so --> /packages/factory/qnx_binaries_and_libraries/root/lib/dll/devg-soft3d-fixed.so (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/dll/deva-ctrl-ipod.so --> /packages/factory/qnx_binaries_and_libraries/root/lib/dll/deva-ctrl-ipod.so (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/dll/mmedia/xing_mpega_decoder-v6.so --> /packages/factory/qnx_binaries_and_libraries/root/lib/dll/mmedia/xing_mpega_decoder-v6.so (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/dll/mmedia/wma9_parser.so --> /packages/factory/qnx_binaries_and_libraries/root/lib/dll/mmedia/wma9_parser.so (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/dll/mmedia/wma9_decoder.so --> /packages/factory/qnx_binaries_and_libraries/root/lib/dll/mmedia/wma9_decoder.so (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/dll/mmedia/wavfile_writer.so --> /packages/factory/qnx_binaries_and_libraries/root/lib/dll/mmedia/wavfile_writer.so (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/dll/mmedia/wav_parser.so --> /packages/factory/qnx_binaries_and_libraries/root/lib/dll/mmedia/wav_parser.so (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/dll/mmedia/tmpfile_streamer.so --> /packages/factory/qnx_binaries_and_libraries/root/lib/dll/mmedia/tmpfile_streamer.so (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/dll/mmedia/stream_reader.so --> /packages/factory/qnx_binaries_and_libraries/root/lib/dll/mmedia/stream_reader.so (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/dll/mmedia/rawfile_writer.so --> /packages/factory/qnx_binaries_and_libraries/root/lib/dll/mmedia/rawfile_writer.so (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/dll/mmedia/queue_filter.so --> /packages/factory/qnx_binaries_and_libraries/root/lib/dll/mmedia/queue_filter.so (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/dll/mmedia/mpega_parser.so --> /packages/factory/qnx_binaries_and_libraries/root/lib/dll/mmedia/mpega_parser.so (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/dll/mmedia/mp4_parser.so --> /packages/factory/qnx_binaries_and_libraries/root/lib/dll/mmedia/mp4_parser.so (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/dll/mmedia/media_streamer.so --> /packages/factory/qnx_binaries_and_libraries/root/lib/dll/mmedia/media_streamer.so (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/dll/mmedia/http_streamer.so --> /packages/factory/qnx_binaries_and_libraries/root/lib/dll/mmedia/http_streamer.so (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/dll/mmedia/fraunhofer_mp3_decoder.so --> /packages/factory/qnx_binaries_and_libraries/root/lib/dll/mmedia/fraunhofer_mp3_decoder.so (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/dll/mmedia/fildes_streamer.so --> /packages/factory/qnx_binaries_and_libraries/root/lib/dll/mmedia/fildes_streamer.so (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/dll/mmedia/damping_audio_writer.so --> /packages/factory/qnx_binaries_and_libraries/root/lib/dll/mmedia/damping_audio_writer.so (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/dll/mmedia/cdda_streamer.so --> /packages/factory/qnx_binaries_and_libraries/root/lib/dll/mmedia/cdda_streamer.so (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/dll/mmedia/cdda_parser.so --> /packages/factory/qnx_binaries_and_libraries/root/lib/dll/mmedia/cdda_parser.so (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/dll/mmedia/audio_writer.so --> /packages/factory/qnx_binaries_and_libraries/root/lib/dll/mmedia/audio_writer.so (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/dll/mmedia/audio_streamer.so --> /packages/factory/qnx_binaries_and_libraries/root/lib/dll/mmedia/audio_streamer.so (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/dll/mmedia/ade3_writer.so --> /packages/factory/qnx_binaries_and_libraries/root/lib/dll/mmedia/ade3_writer.so (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/dll/font/ttfFFcore.so --> /packages/factory/qnx_binaries_and_libraries/root/lib/dll/font/ttfFFcore.so (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/dll/font/PHFcore.so --> /packages/factory/qnx_binaries_and_libraries/root/lib/dll/font/PHFcore.so (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/dll/font/FCcore.so --> /packages/factory/qnx_binaries_and_libraries/root/lib/dll/font/FCcore.so (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/dll/devg-mono-imx31.so --> /packages/factory/graphics/root/lib/dll/devg-mono-imx31.so (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/lib/dll/devg-imx31.so --> /packages/factory/graphics/root/lib/dll/devg-imx31.so (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/bin/wm8580a-control --> /packages/factory/swsa_binaries_and_libraries/root/bin/wm8580a-control (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/bin/usb_dump_reg --> /packages/factory/swsa_binaries_and_libraries/root/bin/usb_dump_reg (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/bin/usb-fault --> /packages/factory/swsa_binaries_and_libraries/root/bin/usb-fault (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/bin/reversing-camera --> /packages/factory/swsa_binaries_and_libraries/root/bin/reversing-camera (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/bin/powerScript --> /packages/factory/swsa_binaries_and_libraries/root/bin/powerScript (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/bin/i2c-imx31_swsa --> /packages/factory/swsa_binaries_and_libraries/root/bin/i2c-imx31_swsa (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/bin/core_log --> /packages/factory/swsa_binaries_and_libraries/root/bin/core_log (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/bin/VBus_ctl --> /packages/factory/swsa_binaries_and_libraries/root/bin/VBus_ctl (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/bin/USB_RESET --> /packages/factory/swsa_binaries_and_libraries/root/bin/USB_RESET (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/bin/TMC_test --> /packages/factory/swsa_binaries_and_libraries/root/bin/TMC_test (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/bin/img_thn --> /packages/factory/qnx_binaries_and_libraries/root/bin/img_thn (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/bin/img_rotate --> /packages/factory/qnx_binaries_and_libraries/root/bin/img_rotate (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/bin/img_resize --> /packages/factory/qnx_binaries_and_libraries/root/bin/img_resize (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/bin/img_encode --> /packages/factory/qnx_binaries_and_libraries/root/bin/img_encode (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/bin/img_decode_surface --> /packages/factory/qnx_binaries_and_libraries/root/bin/img_decode_surface (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/bin/img_decode_simple --> /packages/factory/qnx_binaries_and_libraries/root/bin/img_decode_simple (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/bin/img_decode_mem --> /packages/factory/qnx_binaries_and_libraries/root/bin/img_decode_mem (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/bin/hamctrl --> /packages/factory/qnx_binaries_and_libraries/root/bin/hamctrl (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/bin/font-cache --> /packages/factory/qnx_binaries_and_libraries/root/bin/font-cache (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/bin/devi-hirun --> /packages/factory/qnx_binaries_and_libraries/root/bin/devi-hirun (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/bin/devi-hid --> /packages/factory/qnx_binaries_and_libraries/root/bin/devi-hid (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/bin/pin_iomuxer --> /packages/factory/io/root/bin/pin_iomuxer (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/bin/touch_2_hmi_connector --> /packages/factory/hmi/root/bin/touch_2_hmi_connector (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/bin/hmi --> /packages/factory/hmi/root/bin/hmi (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/bin/buttons --> /packages/factory/hmi/root/bin/buttons (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/bin/devi-tsc2007 --> /packages/factory/graphics/root/bin/devi-tsc2007 (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/bin/contrast --> /packages/factory/graphics/root/bin/contrast (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/bin/VLCDAdjust --> /packages/factory/graphics/root/bin/VLCDAdjust (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/bin/diagnostics --> /packages/factory/diagnostics/root/bin/diagnostics (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/bin/bluetoothprofiles --> /packages/factory/bluetooth/root/bin/bluetoothprofiles (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/bin/bluetoothdiagnostics --> /packages/factory/bluetooth/root/bin/bluetoothdiagnostics (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/bin/bluetoothdfu --> /packages/factory/bluetooth/root/bin/bluetoothdfu (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/bin/bcsp --> /packages/factory/bluetooth/root/bin/bcsp (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/bin/bccmd --> /packages/factory/bluetooth/root/bin/bccmd (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/bin/bc5 --> /packages/factory/bluetooth/root/bin/bc5 (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/bin/vehicle_settings --> /packages/factory/applications/root/bin/vehicle_settings (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/bin/time_manager --> /packages/factory/applications/root/bin/time_manager (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/bin/him --> /packages/factory/applications/root/bin/him (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/bin/acm --> /packages/factory/applications/root/bin/acm (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/etc/clean_fs_usb.sh --> /packages/factory/swsa_binaries_and_libraries/root/etc/clean_fs_usb.sh (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/etc/apsDefaults.sh --> /packages/factory/swsa_binaries_and_libraries/root/etc/apsDefaults.sh (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/etc/shadow --> /packages/factory/qnx_binaries_and_libraries/root/etc/shadow (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/etc/passwd --> /packages/factory/qnx_binaries_and_libraries/root/etc/passwd (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/etc/group --> /packages/factory/qnx_binaries_and_libraries/root/etc/group (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/etc/swsa.ini --> /packages/factory/power/root/etc/swsa.ini (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/etc/mme.conf --> /packages/factory/media_player/root/etc/mme.conf (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/etc/mcd.mnt --> /packages/factory/media_player/root/etc/mcd.mnt (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/etc/mcd.conf --> /packages/factory/media_player/root/etc/mcd.conf (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/etc/ipod.cfg --> /packages/factory/media_player/root/etc/ipod.cfg (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/etc/iom.cfg --> /packages/factory/media_player/root/etc/iom.cfg (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/etc/iofs.fsm --> /packages/factory/media_player/root/etc/iofs.fsm (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/etc/iofs.fsf --> /packages/factory/media_player/root/etc/iofs.fsf (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/etc/iofs.fsd --> /packages/factory/media_player/root/etc/iofs.fsd (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/etc/enum-usb.conf --> /packages/factory/media_player/root/etc/enum-usb.conf (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/etc/FordLogo_Color_310X136.logo --> /packages/factory/media_player/root/etc/FordLogo_Color_310X136.logo (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/etc/FordLogo_Color_166X71.logo --> /packages/factory/media_player/root/etc/FordLogo_Color_166X71.logo (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/etc/test_files/test_tone_1khz.wav --> /packages/factory/diagnostics/root/etc/test_files/test_tone_1khz.wav (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/etc/bluetooth/firmware/stack.dfu --> /packages/factory/bluetooth/root/etc/bluetooth/firmware/stack.dfu (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/etc/bluetooth/firmware/app.dfu --> /packages/factory/bluetooth/root/etc/bluetooth/firmware/app.dfu (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/etc/bluetooth/firmware/parameters/type6Data.dfu --> /packages/factory/bluetooth/root/etc/bluetooth/firmware/parameters/type6Data.dfu (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/etc/bluetooth/firmware/parameters/type5Data.dfu --> /packages/factory/bluetooth/root/etc/bluetooth/firmware/parameters/type5Data.dfu (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/etc/bluetooth/firmware/parameters/type4Data.dfu --> /packages/factory/bluetooth/root/etc/bluetooth/firmware/parameters/type4Data.dfu (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/etc/bluetooth/firmware/parameters/type3Data.dfu --> /packages/factory/bluetooth/root/etc/bluetooth/firmware/parameters/type3Data.dfu (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/etc/bluetooth/firmware/parameters/type2Data.dfu --> /packages/factory/bluetooth/root/etc/bluetooth/firmware/parameters/type2Data.dfu (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/etc/bluetooth/firmware/parameters/type1Data.dfu --> /packages/factory/bluetooth/root/etc/bluetooth/firmware/parameters/type1Data.dfu (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/etc/system/enum/common --> /packages/factory/media_player/root/etc/system/enum/common (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/etc/system/enum/include/usb-class --> /packages/factory/media_player/root/etc/system/enum/include/usb-class (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/etc/system/enum/devices/usb/mass --> /packages/factory/media_player/root/etc/system/enum/devices/usb/mass (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/etc/system/enum/devices/usb/ipod --> /packages/factory/media_player/root/etc/system/enum/devices/usb/ipod (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/etc/system/config/img.conf --> /packages/factory/qnx_binaries_and_libraries/root/etc/system/config/img.conf (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/etc/system/config/winmgr.with_cursor.conf --> /packages/factory/graphics/root/etc/system/config/winmgr.with_cursor.conf (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/etc/system/config/winmgr.conf --> /packages/factory/graphics/root/etc/system/config/winmgr.conf (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/etc/system/config/mono-imx31.conf --> /packages/factory/graphics/root/etc/system/config/mono-imx31.conf (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/etc/system/config/imx31_47hz.conf --> /packages/factory/graphics/root/etc/system/config/imx31_47hz.conf (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/etc/system/config/imx31_30hz.conf --> /packages/factory/graphics/root/etc/system/config/imx31_30hz.conf (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/etc/system/config/display.conf --> /packages/factory/graphics/root/etc/system/config/display.conf (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/etc/system/config/backlight_calibration_3_50.conf --> /packages/factory/graphics/root/etc/system/config/backlight_calibration_3_50.conf (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/etc/system/config/backlight_calibration_3_00.conf --> /packages/factory/graphics/root/etc/system/config/backlight_calibration_3_00.conf (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/etc/system/config/calib.localhost --> /packages/persist/root/etc/system/config/calib.localhost (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/scripts/swsa_binaries_and_libraries --> /packages/factory/swsa_binaries_and_libraries/scripts (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/scripts/qnx_binaries_and_libraries --> /packages/factory/qnx_binaries_and_libraries/scripts (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/scripts/power --> /packages/factory/power/scripts (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/scripts/media_player --> /packages/factory/media_player/scripts (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/scripts/io --> /packages/factory/io/scripts (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/scripts/hmi --> /packages/factory/hmi/scripts (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/scripts/graphics --> /packages/factory/graphics/scripts (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/scripts/diagnostics --> /packages/factory/diagnostics/scripts (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/scripts/core-pkg --> /packages/factory/core-pkg/scripts (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/scripts/bluetooth --> /packages/factory/bluetooth/scripts (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/scripts/applications --> /packages/factory/applications/scripts (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/info/swsa_binaries_and_libraries --> /packages/factory/swsa_binaries_and_libraries/info (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/info/qnx_binaries_and_libraries --> /packages/factory/qnx_binaries_and_libraries/info (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/info/power --> /packages/factory/power/info (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/info/media_player --> /packages/factory/media_player/info (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/info/iplspl --> /packages/factory/iplspl/info (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/info/io --> /packages/factory/io/info (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/info/hmi --> /packages/factory/hmi/info (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/info/graphics --> /packages/factory/graphics/info (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/info/fast_startup --> /packages/factory/fast_startup/info (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/info/diagnostics --> /packages/factory/diagnostics/info (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/info/core-pkg --> /packages/factory/core-pkg/info (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/info/bluetooth --> /packages/factory/bluetooth/info (No such file or directory)
cp -R: Can't create symbolic link ./etfsRoot/info/applications --> /packages/factory/applications/info (No such file or directory)

...

cp -R: Can't create symbolic link ./packages/current --> /fs/etfs/packages/factory (No such file or directory)

...

cp: read (/proc/self/as): Server fault on msg pass
cp: read (/proc/1/as): Server fault on msg pass
cp: read (/proc/5902338/as): Server fault on msg pass
cp: read (/proc/8195/as): Server fault on msg pass
cp: read (/proc/8196/as): Server fault on msg pass
cp: read (/proc/32773/as): Server fault on msg pass
cp: read (/proc/8198/as): Server fault on msg pass
cp: read (/proc/57351/as): Server fault on msg pass
cp: read (/proc/57352/as): Server fault on msg pass
cp: read (/proc/94217/as): Server fault on msg pass
cp: read (/proc/110602/as): Server fault on msg pass
cp: read (/proc/118795/as): Server fault on msg pass
cp: read (/proc/122892/as): Server fault on msg pass
cp: read (/proc/122893/as): Server fault on msg pass
cp: read (/proc/188430/as): Server fault on msg pass
cp: read (/proc/425999/as): Server fault on msg pass
cp: read (/proc/426000/as): Server fault on msg pass
cp: read (/proc/524305/as): Server fault on msg pass
cp: read (/proc/229394/as): Server fault on msg pass
cp: read (/proc/315411/as): Server fault on msg pass
cp: read (/proc/3645460/as): Server fault on msg pass
cp: read (/proc/356373/as): Server fault on msg pass
cp: read (/proc/5906454/as): Server fault on msg pass
cp: read (/proc/364567/as): Server fault on msg pass
cp: read (/proc/356376/as): Server fault on msg pass
cp: read (/proc/368665/as): Server fault on msg pass
cp: read (/proc/372762/as): Server fault on msg pass
cp: read (/proc/385051/as): Server fault on msg pass
cp: read (/proc/372764/as): Server fault on msg pass
cp: read (/proc/385053/as): Server fault on msg pass
cp: read (/proc/434206/as): Server fault on msg pass
cp: read (/proc/385055/as): Server fault on msg pass
cp: read (/proc/438304/as): Server fault on msg pass
cp: read (/proc/385057/as): Server fault on msg pass
cp: read (/proc/385058/as): Server fault on msg pass
cp: read (/proc/438307/as): Server fault on msg pass
cp: read (/proc/536612/as): Server fault on msg pass
cp: read (/proc/385061/as): Server fault on msg pass
cp: read (/proc/438310/as): Server fault on msg pass
cp: read (/proc/438311/as): Server fault on msg pass
cp: read (/proc/548904/as): Server fault on msg pass
cp: read (/proc/561193/as): Server fault on msg pass
cp: read (/proc/438314/as): Server fault on msg pass
cp: read (/proc/438315/as): Server fault on msg pass
cp: read (/proc/565292/as): Server fault on msg pass
cp: read (/proc/577581/as): Server fault on msg pass
cp: read (/proc/577582/as): Server fault on msg pass
cp: read (/proc/577583/as): Server fault on msg pass
cp: read (/proc/593968/as): Server fault on msg pass
cp: read (/proc/606258/as): Server fault on msg pass
cp: read (/proc/610355/as): Server fault on msg pass
cp: read (/proc/610356/as): Server fault on msg pass
cp: read (/proc/630837/as): Server fault on msg pass
cp: read (/proc/610358/as): Server fault on msg pass
cp: read (/proc/630839/as): Server fault on msg pass
cp: read (/proc/639032/as): Server fault on msg pass
cp: read (/proc/630841/as): Server fault on msg pass
cp: read (/proc/659514/as): Server fault on msg pass
cp: read (/proc/651323/as): Server fault on msg pass
cp: read (/proc/643132/as): Server fault on msg pass
cp: read (/proc/651326/as): Server fault on msg pass
cp -R: Can't create symbolic link ./proc/boot/libsocket.so --> libsocket.so.2 (No such file or directory)
cp -R: Can't create symbolic link ./proc/boot/libc.so --> libc.so.3 (No such file or directory)
cp -R: Can't create symbolic link ./proc/boot/libusbdi.so --> libusbdi.so.2 (No such file or directory)
cp -R: Special named file - cannot duplicate. (/proc/dumper)

..

cp -R: Special named file - cannot duplicate. (/hmi/app_events_in)
cp -R: Special named file - cannot duplicate. (/hmi/app_events_out)
cp -R: Special named file - cannot duplicate. (/hmi/dp)
cp -R: Special named file - cannot duplicate. (/hmi/list)

..

cp -R: Special named file - cannot duplicate. (/hmi_/service)
JasonACT is offline   Reply With Quote Multi-Quote with this Post
Old 22-12-2019, 03:12 PM   #235
JasonACT
Away on leave
 
Join Date: Apr 2019
Location: ACT
Posts: 1,735
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

The Sat-Nav unit has 8457 items (489MB). These are the Nav filenames which make up the bulk of space used, but while I know it's NavNGo/NNG/iGo I don't think the latest 2019Q2 files (from my searching) are quite the same as these:


\packages\factory\navi_maps\root_dir\usr\navngo

22/12/2019..01:25PM....<DIR>..........MobileNavigator

\packages\factory\navi_maps\root_dir\usr\navngo\Mo bileNavigator

22/12/2019..01:25PM....<DIR>..........content
22/12/2019..01:25PM....<DIR>..........license

\packages\factory\navi_maps\root_dir\usr\navngo\Mo bileNavigator\content

22/12/2019..01:25PM....<DIR>..........dem
22/12/2019..01:25PM....<DIR>..........global_cfg
22/12/2019..01:25PM....<DIR>..........map
22/12/2019..01:25PM....<DIR>..........poi
22/12/2019..01:25PM....<DIR>..........speedcam
22/12/2019..01:25PM....<DIR>..........tmc
22/12/2019..01:25PM....<DIR>..........version

\packages\factory\navi_maps\root_dir\usr\navngo\Mo bileNavigator\content\dem

01/01/1980..12:00AM.......141,853,835 Australia.dem
01/01/1980..12:00AM........11,878,913 NewZealand.dem

\packages\factory\navi_maps\root_dir\usr\navngo\Mo bileNavigator\content\global_cfg

01/01/1980..12:00AM.........6,944,869 global_cfg.zip

\packages\factory\navi_maps\root_dir\usr\navngo\Mo bileNavigator\content\map

01/01/1980..12:00AM........92,972,048 Australia.fbl
01/01/1980..12:00AM.........1,758,224 Australia.fda
01/01/1980..12:00AM.........5,090,651 Basemap.fbl
01/01/1980..12:00AM........17,007,120 NewZealand.fbl

\packages\factory\navi_maps\root_dir\usr\navngo\Mo bileNavigator\content\poi

01/01/1980..12:00AM........56,210,635 Australia.poi
01/01/1980..12:00AM........12,366,054 NewZealand.poi

\packages\factory\navi_maps\root_dir\usr\navngo\Mo bileNavigator\content\speedcam

01/01/1980..12:00AM...........165,800 Australia.spc
01/01/1980..12:00AM...........362,462 Australia_schoolzones.spc
01/01/1980..12:00AM............36,708 NewZealand.spc
01/01/1980..12:00AM............40,360 NewZealand_schoolzones.spc
01/01/2000..12:56AM.................0 SpeedcamUpdates.spud

\packages\factory\navi_maps\root_dir\usr\navngo\Mo bileNavigator\content\tmc

01/01/1980..12:00AM.............8,374 Australia-SUNA.tmc
01/01/1980..12:00AM.............1,220 NewZealand-SUNA.tmc

\packages\factory\navi_maps\root_dir\usr\navngo\Mo bileNavigator\content\version

01/01/1980..12:00AM................14 map_part_number.txt
01/01/1980..12:00AM................14 tmc_part_number.txt

\packages\factory\navi_maps\root_dir\usr\navngo\Mo bileNavigator\license

01/01/1980..12:00AM.............1,416 SWSA_SER19.lyc

Last edited by JasonACT; 22-12-2019 at 03:19 PM.
JasonACT is offline   Reply With Quote Multi-Quote with this Post
This user likes this post:
Old 22-12-2019, 07:01 PM   #236
raceteam
FF.Com.Au Hardcore
 
Join Date: Nov 2013
Posts: 2,037
Default Re: FORD technical service bulletin : ICC touch screen display

Apparently the latest moved to HERE maps https://fordforums.com.au/vbportal/f...0&postcount=22
raceteam is offline   Reply With Quote Multi-Quote with this Post
This user likes this post:
Old 23-12-2019, 09:56 PM   #237
XD 351 Ute
Excessive Fuel Ingestion
 
XD 351 Ute's Avatar
 
Join Date: Dec 2004
Location: Central Queensland Coast
Posts: 1,586
Default Re: FORD technical service bulletin : ICC touch screen display

Forgive me, but going a touch off subject.
Having followed this thread after hearing about FGII ICC's dying quite a lot,
I have bought a memory minder so that when I change the battery in mine,
hopefully the ICC won't die?

I would appreciate any feedback.

Thanks, Ed
__________________
Recommended Forum Traders: RSGerry, trimmaster, 51OAU, EB-92, adxr8, my67xr, RG, ZA-289, kruptor, gassa, Felony, RNXR, Rhino 351, Anchor, Smoke Pursuit, Mr. FPV (through E-Bay),
XD 351 Ute is offline   Reply With Quote Multi-Quote with this Post
Old 23-12-2019, 11:14 PM   #238
JasonACT
Away on leave
 
Join Date: Apr 2019
Location: ACT
Posts: 1,735
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've got 4 FGII ICC screens (one is in the car, but I've recently done a lot with the other 3)... The flash memory chip in these things seems to be really bad, all 3 report ECC errors (EEC = error correcting code) when reading the file system files. And I mean, an absolute s-load of them, you would not believe it. The ECC software routines fix the errors (apparently up to 4 bits per page - with logic to always tell if 5 bits are wrong - 6 or more and it'll "probably" be able to tell - but over 4 and it can no longer fix the data).

These chips are rated at 10 years data retention. All of the good ones back in 2011 were rated this way. NASA has a pdf (I found) that tests Samsung flash chips (these are some of the best, not that I rate Samsung for anything else), using 125c temperatures and 0, 100 & 500 hour tests - at 100 hours, one bit had failed and the guy noted that's a lot less than 10 years. His recommendation was ECC was very important if they were to use these things.

These units also have a "cold-power-up" counter that I've found, my original unit is now at over 500 due to all the tests I've run. I'm not sure simply disconnecting/reconnecting power is an issue, but maybe a fully charged battery is (I'm using a properly configured 12v supply and a brand new battery can be over 14v).

Personally, I now just think many just end up getting that 5th bit lost and the unit no longer works. Time is a real killer, isn't it.

(Oh, and I'm having real trouble finding V23-V25 .fbl files online to test out the Sat-Nav to see if I can update the maps.)
JasonACT is offline   Reply With Quote Multi-Quote with this Post
Old 24-12-2019, 10:47 AM   #239
JasonACT
Away on leave
 
Join Date: Apr 2019
Location: ACT
Posts: 1,735
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

Thinking about the memory minder thing though, if your boot files on the flash memory have "faded" and are now bad (they only get read once when you connect power) then using the minder device might stop you needing them by avoiding the reboot process. There's actually a whole 16MB partition at the start of the flash memory for the boot process.

Might be why people think these devices die when changing the battery? When it could be that the device has been "dead" for some time, but it's last breath has just been a really long one, with all the boot programs loaded in RAM.

Definitely use the minder, if you've got one.
JasonACT is offline   Reply With Quote Multi-Quote with this Post
This user likes this post:
Old 24-12-2019, 01:53 PM   #240
PHATAL
Donating Member
Donating Member1
 
PHATAL's Avatar
 
Join Date: Feb 2006
Location: Roxby Downs, SA
Posts: 1,439
Default Re: FORD technical service bulletin : ICC touch screen display

I have nothing to input to this thread. Only here to say what you are doing looks awesome. I want to be you when I grow up LOL.
__________________
ZG Fairlane 500 351 - First car - Now restoring! - LOOKING FOR ZG PARTS - BLACK AUTO CONSOLE - BLACK DASH PAD - BLACK SEAT BELTS (WITH THE METAL BUCKLES) -
RIGHT REAR CHROME TRIM

XF Falcon S Update EFI - SOLD
EL2 XR8 - SOLD
BF F6 RSPEC #139 - SOLD
Now rocking the SZ Territory Titanium Petrol Family Beast
PHATAL is offline   Reply With Quote Multi-Quote with this Post
This user likes this post:
Reply


Forum Jump


All times are GMT +11. The time now is 01:57 PM.


Powered by vBulletin® Version 3.8.5
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Other than what is legally copyrighted by the respective owners, this site is copyright www.fordforums.com.au
Positive SSL