Mod5270 & MOD5270B with v2.5.3

[seulater]

I could have sworn that prior to compiler v2.5.3, If i had a product with a mix of MOD5270 & MOD5270B's that if i make my project build for a MOD5270 it would work for both units when upgrading.

I just had a customer say he got a popup warning that the build was for a MOD5270 and the board was a 5270B, at first i thought he messed it up, then i just tried this using v2.5.3 built for a MOD5270 and flashing a MOD5270B and sure enough he was correct, it wont let you.

So now the issue is, did this change in v2.5.3 ?

[greengene]

i'm still a command line guy (eclipse for editing) and i've always added
a -PMOD5270B flag to the compcode line of the makefile to remove this
problem. it then workes the same for pre-2.5.3 and 2.5.3 for me.

[tod]

If you want to user greengene's solution with the Eclipse automated build you can add a flag to CompCode using the General tab and then typing the desired value in the Other flags text box. Adding -PMMOD5270B won't remove or replace the board flag already there. Moving up to the NetBurner Compcode level will show you the final command line being used for compcode. (I tested adding the flag but not actually doing a build to see if it works with both boards).

CompCodeFlag.png (83.91 KiB) Viewed 3040 times