Welcome, Guest. Please login or register.

Author Topic: Freescale Coldfire V4s  (Read 6234 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline Zac67

  • Hero Member
  • *****
  • Join Date: Nov 2004
  • Posts: 2890
    • Show all replies
Re: Freescale Coldfire V4s
« on: April 07, 2012, 02:25:25 PM »
Just wondering - what'll you use the Coldfires for?
 

Offline Zac67

  • Hero Member
  • *****
  • Join Date: Nov 2004
  • Posts: 2890
    • Show all replies
Re: Freescale Coldfire V4s
« Reply #1 on: April 07, 2012, 06:06:32 PM »
A 266 MHz CPU would severly starve on motherboard RAM. There's no way you can avoid a local memory subsystem. While you're at it, don't forget to provide means to use the PCI bus (at minimum, a connector enabling you to route the bus to a replacement daughter board).

Coldfires have several software compatibility issues, so it'll be quite a feat to make present software run without problems.
 

Offline Zac67

  • Hero Member
  • *****
  • Join Date: Nov 2004
  • Posts: 2890
    • Show all replies
Re: Freescale Coldfire V4s
« Reply #2 on: April 07, 2012, 11:03:35 PM »
In theory, you could modify the binary loader to patch everything it loads by means of a database.

While this wouldn't catch anything loaded by other methods or self-modifying code it would probably work on 95% of the software. However, we'd have a very hard time building the patch database (which would require automated code search and visual inspection of candidates).
 

Offline Zac67

  • Hero Member
  • *****
  • Join Date: Nov 2004
  • Posts: 2890
    • Show all replies
Re: Freescale Coldfire V4s
« Reply #3 on: April 08, 2012, 05:43:33 PM »
Recompiling source code will be fine - you 'just' require the source. However, some instructions behave differently, so without code analysis you will never know if the code at hand works OK.
 

Offline Zac67

  • Hero Member
  • *****
  • Join Date: Nov 2004
  • Posts: 2890
    • Show all replies
Re: Freescale Coldfire V4s
« Reply #4 on: April 09, 2012, 02:32:18 PM »
Quote
What you do know is that the program entry is code. You can start from there and put traps in sections where you are not sure (e.g jmp tables etc.).


This is what I was referring to - you should be aware that this is a manual task as exhaustively doing this in software is not possible (except for trivial programs). Someone has to check/patch the 68k code and (hopefully) share his findings with others through a database on the 'net which the binary loader uses in turn to patch code while it's being loaded. Not likely to happen.