Author Topic: Is support missing for M5225X in SP9 types.h ?  (Read 8147 times)

Offline syakovlev

  • Newbie
  • *
  • Posts: 20
    • View Profile
Is support missing for M5225X in SP9 types.h ?
« on: April 21, 2010, 03:03:01 AM »
If _M52259 is defined, then MAX_FILE_LENGTH defaults to unsigned short.
It seems strange. I would expect an unsigned long.
Thx.

Offline mark

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 3236
    • View Profile
    • uTasker
Re: Is support missing for M5225X in SP9 types.h ?
« Reply #1 on: April 21, 2010, 09:41:23 AM »
Hi

All Coldfire devices default to unsigned long for MAX_FILE_LENGTH

In types.h:
#if defined (_M5223X) ...
    typedef unsigned long   MAX_FILE_LENGTH;                             // over 64k file lengths



In config.h:
#ifdef _M5223X
  //#define _M521X                                                       // basic CAN MCU
  //#define _M521XX                                                      // basic MCU
  //#define _M5221X                                                      // USB family
  //#define _M5222X                                                      // USB family
    #define _M5225X                                                      // Kirin3


Note that _M5223X is is used to basically control the Coldfire target - then the _M5225X for the Kirin3.

This means that it is not normal that you are getting unsigned short for the type. Ensure that the config.h setting is as above and command a rebuild of the project to be sure that all is being compiled.

Regards

Mark