NetBurner Community Forum

Any guidance on how we should proceed?

So there is nothing we can do to correct the problem. Yes, these are brand new modules. We bought these through a distributor, Mouser. Should we go through Mouser to return them, who is fighting us tooth and nail about returning these, or send them direct to Netburner?

Yes, we used the Alternate Boot Monitor to successfully download MOD5441x_FactoryApp_APP.s19 to both modules using the FLA command with MTTTY serial terminal. But the app never ran. The same error messages I put in my previous posts were issued.

Neither module was able to get an IP Address when ...

The modules are plugged into our hardware. Tens of modules are programmed in these test fixtures each week. It's only these two modules that won't program. It is rare that modules fail to program.
In one module it appears that the Alternate Monitor is not entered, based on the terminal output. The ...

Yes, I tried the shorting jumper. It didn't help. I have two modules in this state. Both are new. The serial output of the first one is what I put in my first post. Shorting jumper TP1 during bootup produces the same messages as above. It doesn't appear that the Alternate Boot Monitor is started ...

On a brand new MOD54415-200IR module, when I power it up the serial port spits out:

App Header Failed
No Valid app

App Header Failed

NetBurner MCF5441x SPI Boot Monitor V1.06 Feb 28 2020 18:20:21
HELP for help

Using the serial terminal MTTTY, I uploaded MOD5441x-FactoryApp_APP.s19 (from v2.9.5 ...

It appears that Outlook adds formatting characters to code that's pasted into an email, and copying code from the email and pasting it into a source file includes those extra characters, and the file won't compile. We had to replace all white-space with spaces.

In v2.9.5, when I click "Rebuild Modified System Files" in Eclipse I get the following error message: The build console is blank.

I only found these because I rebuilt the system libs, and that always generates a lot of compiler warnings. And warnings make me nervous. So I go through every warning to see if I can do something to remove it without changing how the code works.

The following snippets are from v3.5.2.
In File SslSocket.cpp, beginning at line 274, It appears that local variable 'ret' can be used uninitialized at line 298.

uint16_t SslSocket::InitSocket(int tcpFd, WOLFSSL_CTX *ctx, const char *commonName, uint32_t sockFlags /* = 0 */, int verifyPeer ...