NetBurner Community Forum

Hello guys,

we have been using the MOD5272 for some years now to make machine-controls. A few weeks ago we started with a new project which is based on the MOD54415 and the excisting software.
After changing a few addresses all look fine, BUT we couldn't program the MOD54415. After some trial on error we found out that there is a 'nativeboot' function.
So now we have to 'abort' the application under MTTTY, catch with 'A', do 'nativeboot', catch again with 'A' and then use 'fla' or 'dl'

FYI, we don't make webapplications but machine controls and most of software is in assembly (we control 13 servo loops with 0.01mm accuracy realtime) as we need the speed.

I hope someone can help to make my life easier i.e. not having to 'abort' twice before I can re-program the MOD54415.

Awaiting your reaction and with regards,

Hans

I am confused. why cant you use the network cable to program it ?

Hi seulater,

maybe in the future, but for now I'm 'talking' to an PC-MMI through a UTP connection which runs in C (Rx & Tx functions), but is fed in assembly. Also we are communicating with a Siemens S7-300 through UTP on a second port.
Problem is, I can't program the MOD54415 not like the MOD5272 unless I perform a 'nativeboot'.

I would like to have the 'nativeboot' as standard and the 'alternateboot' as option

tnx for your reply & with regards, Hans

Hans, can you explain a little more succinctly what exactly is the issue and what you want to be able to do? I'm not sure why you're going through two rounds of booting to the monitor, just to use the serial download. You should be able to simply go through that once; as in 'A'->'FLA', and then transmit the file.

-Dan

Hi Dan,

if I use FLA to flash my application it just fails with "Download failed"

The make things maybe more clear (or complicated), we have a small C-application which gives us an slightly more comfertable monitor e.g. I can type "md a5+x1240", which dumps 256 bytes starting at the contents of the a5-register with an additional offset of 0x1240.
On top of this C-application we run a huge assembly application to make a kind of CNC-machine.

We run the normal Eclipse, not NBEclispe, to make our S19-file, and it will just not flash in 'AlternateBoot' but it does in 'NativeBoot'.
Maybe we are missing something in our S19-file, but on the other hand if we 'fla' in Native all works fine.

To cut things short, is there a possibility to instruct the MOD54415 to use NativeBoot by default instead of AlternateBoot?

With regards, Hans