NetBurner Community Forum

Hello Alok,

Thank you for the update. You are correct, ARM processors require the 3.x tools. Can you provide any more details on why going from 2.9.7 to 3.x would require a lot of change? So far in my experience, other than the web processing, not much change has been necessary. Although I have not ...

Hello AlokD,

1. Yes, those pin functions all match. Mechanically, the headers, mounting holes and Ethernet jacks are the same across the MODxxxx product line. The length of the MOD5441x is about 0.25 inches longer than the MOD5282. This is the dimension opposite the RJ-45 jack. So it does not ...

Hello,

Yes. On March 11 I posted:

Re: App Header Failed
Post by TomNB » Tue Mar 11, 2025 5:30 pm

You can send them to us. Send an email to sales@netburner.com and ask for the RMA link.

You can send them to us. Send an email to sales@netburner.com and ask for the RMA link.

It acts like something is driving the address or data bus. But if they are new units and your sure it's not your h/w, then the next step would be to RMA them. Just to confirm, these are new units out of the package?

Thanks for the information. The recovery jumper boots the device to the alternate monitor, which uses defaults such as DHCP. It does not support AutoIP.

Once in the alternate monitor, you would need a PC and the MOD54417 to be on a network with a DHCP server so the MOD54417 can get IP settings ...

The purpose of the recovery jumper is to put you in the Alternate Monitor as you have in your last post. Are you saying you cannot interact with the Alternate Monitor?

The other issue could be if something is interfering with the address or data bus. Are these plugged into your own h/w? If so, does any other module work in the same h/w?

Yes, have you tried the shorting jumper recovery procedure? https://www.netburner.com/NBDocs/Develo ... overy.html

Hello. I think they should be the same.