NetBurner Community Forum

If you have a mod5270B board that was flashed with a project defined as MOD5270 it of course runs fine.
But if later the project grew and was later changed to a MOD5270B and you try to update the firmware you get a popup saying that the board is a MOD5270 and your trying to update it with a MOD5270B firmware and wont let you update it.

The only way i found to correct this is to upload the new firmware manually via the serial port. Once this is done then you can update it via Ethernet.

Is there a way around this so i can do this via Ethernet? My customers are going to have no idea how to do this serially.

One way to do this is to modify the platform name in your source environment. in your makefile there may or may not be a PLATFORM=MOD5270B callout.
And in your ldflag.mak file in make subdirectory there probably is MOD5270B callout.

you would change callouts to PLATFORM=MOD5270 and rebuild your system files and then your application file

****There may be a better way to do this, and it might come back to bite you later if you try to load MOD5270B code into a legacy MOD5270.

Possibly someone here knows of a workaround? Possibly editing the .s19 file?

Chris

The platform is detected with the first line (S0) of the S19 file. For example, the MOD5270 .s19 first line should be: S0MOD5270. If you remove the S0 line from the .s19 file then AutoUpdate will not check the platform before updating. This will work for swapping between MOD5270 and MOD5270B modules. Make sure not to AutoUpdate to an incompatible module as it will likely result in a trap loop.

-Larry Gitlitz

Thanks, glad it was a super easy fix.