Cheers, yes I'm going to be making/selling them. I'm currently waiting on my first prototype PCBs (x2) to come back from manufacturing. Once I'm happy with them, I'll get a batch made up.

There's also a Serial eeProm in the Display Controller as well - I think close to identical to the chip in the Instrument Cluster. We've been wondering what it does for ages, and now I suspect it is feeding data to the Overlay controller somehow, or else it contains the data for the test screens.

Is it worthwhile firing up a new thread for reverse engineering the ICC? I made a few little extra discoveries with the ICC the other day too - I managed to locate the OBD2 commands to generate the test display modes. Pics are at the end of the BA Scantool Fun thread.


Lukeyson

Hello Luke,
Yes, I saw the serial eeprom - it might contain the test-screen data as per your other thread - great discovery btw

It might be worthwhile starting a reverse-engineering thread of the ICC and/or LCD controller - I need to start going on a little pet-project to eventually replace the ICC with a microcontroller, and utilize the existing space for a big carputer touchpanel, maybe 15" in portrait mode.

Acres of wasted space.......wich Ford would stick to standalone double-din stereo systems......damn.

edit: Added serial eprom datasheet.

edit2: There's also a 2134SL microcontroller, and in hindsight, I guess this microcontroller, with the serial eprom will be controlling the graphics for the overlay. In essence, there are 2 "seperate" graphical controllers on this controller board, one for the main graphics, being simply a passthrough from the external source, such as satnav or carputer, and then the internal controller, handling the CAN-data from the ICC, and using the 2134SL micro/eeprom/overlay controller to display to the TFT.

All conjecture on my part, but I think pretty accurate anyway.

I purchased a very nice little AVR CAN-controller kit from Dontronics, with the eye on engineering a hardware replacement for the complete ICC, and I think it is pretty do-able - see the AVR-kit datasheet....as well as the usb-jtag programmer.

So, is this the case that I'm all dressed with nowhere to go

Hehe....

 

 

Attachments:

avr-usb-jtag.pdf [15.09 KiB] Downloaded 440 times

Dontronics_AVR-CAN.pdf [51.33 KiB] Downloaded 416 times

93c46w6_serial_eprom_lcd_datasheet.pdf [156.96 KiB] Downloaded 385 times

Oh yeah, if that won't get you over the brink, herewith a simple CAN bootloader application for the aforementioned AVR kit

Comeon Luke/data_mine, you know you want to..... :rofl:

 

 

Attachments:

Slim_CAN_bootloader-rev-1.0.0.pdf [249.55 KiB] Downloaded 426 times

Now if you can find the Ford logo 'boot' screen, and replace it with a FPV logo, you'll have FPV owners beating down your door.

Add infinitum, for XR logos, custom whatevers.

Even though it's a eeprom, is it externally programmable? That'd be great.

Well, I have this...sort of...herewith an idea what my logo looks like on my CentraFuse frontend

Soz for the off-topic, Lukeyson, will reign myself in and wonder back on-topic....

 

 

Attachments:

FPV_CF_Logo.JPG [ 49.77 KiB | Viewed 313 times ]

FPV logo is banned from my car. Only Ford or XR are allowed in....

I don't think there's enough space in that eeprom to map out a whole image - most of that stuff would be programmed in VRAM on the overlay chip itself. But with the night/day mode I wonder if there's a colour map of some sort?

With that negativity on the table, you never really know until you get into it do you - because if you can get to the VRAM, I suspect there'd be people wanting more things than just adding the FPV boot logo. The Clock on current SY Tory's is something a lot of people have been asking for too. But then what other dependencies are there on turning the clock on? Given the control over the clock from the menu, I suspect the clock itself would have to be in the main controller unit itself as well as the overlay unit.


Lukeyson

There's a thread over on FordForums about it, and I got a few peoples hopes up with this chop.

You're a naughty man, Data_mine You had me there for a moment....

Oh, and just to go off topic for a bit, my M2-ATX power supply has apparently been held up in customs.

Pfft. I should have bought that clone off eBay....


Lukeyson

It will be worth the wait

Yeah I found the datasheet for the LCD controller and also the RGB out. Im more interested in the CAN AVR. Wouldnt mind setting up a unit to simulate a way to test the clusters etc and then going further.

I would doubt that the 93c46 would have enough room for anything. Seeing as its a serial eeprom I'd say its used to store some sort of programming data , maybe BEM Keys?

Matt

???

BEM keys in the colour display controller of the ICC? As opposed to in the BEM itself?

There is admittedly some sort of key that needs to be 'written' into the ICC in order to code it to the PCM smartshield broadcasts. But even then it's a function that still works on Non-Colour ICCs.

I'm going to stick with it having some sort of display function still.


Lukeyson

I realise that, but the memory is quite small and why would you have a serial eeprom that only stores static data, doesnt make sense.

I think we chatted about that ages ago didn't we?

The volume, fade, balance, limiter, dsp etc settings are all saved between restarts - but are lost between battery disconnects. So those settings won't be in the eeprom, rather whatever the ICC has a KAM.

Maybe that's where the screen gamma and brightness stuff is kept - it gets tuned for each screen during component assembly?

We're both clutching at straws here....

Maybe it's just the test-screen parameters? Or the settings of Video or IR input that we see listed in one of those test screens....


Lukeyson