NetBurner Community Forum

Hi,

That makes sense to be backwards compatible. Please not the 5282 went EOL a year ago, so if that is the only other platform of concern it might be ok to got to 3.x.

You can run 2.x or 3.x tools on your MOD54415, so you can move your code over to 3.x and then have a linux release. Are you trying to automate a build, or is it that you prefer to develop on your own linux machine?

I've been told that if you open a support ticket we should be able to add that for you, as long as your not looking for the router config to go with it.

Hello,

What platform and tools rev are you using?

Thanks for letting us know AlokD. One more note since the MOD5441X and NANO54415 products can run both 2.x and 3.x tool sets: because those platforms came out prior to 3.x, all units ship with a 2.x factory application so people in situations like yours are not affected. For those using 3.x, once ...

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?