NetBurner Community Forum

Information found.

Where can I find the changes made to the MOD54417 module - it is now at Rev 1.5, we're using anywhere from 1.2 to 1.5, I'd like to know what the differences are.

Thanks!

Ron

A few questions on setting up multiple interfaces on the MOD54417 Ethernet ports: When I do the ShowNetworkInterfaces( ) on my current system, I get 4 interfaces showing up (as documented on page 121 of the NNDKProgMan document, Multiple Network Interfaces). Interfaces 1 and 2 show up with the stati...

Has any further work proceeded on implementing VLAN (Dot 1Q), for Ip4. We have a customer for which VLAN support has snuck into the specs. You mentioned a workaround, this would be most helpful. We are running our application on the MOD54417. As none of us are networking experts, any help would be a...

We are observing something very similar. We are using NNDK Ver 2.7.5, with patch (multicast.cpp) to correctly register a FIFO queue with the desired interface. Identical software (instantiated as two separate tasks, with different parameters for the two ports) receiving multicast broadcasts, at 239....

Using NNDK 2.7.5 - Our application requires dedicating each of the 2 MOD54417 Network interfaces to a specific multicast address. I have created 2 separate tasks, one to service interface 1 and the other to service interface 2, each with a dedicated Fifo queue. The setup is as follows: Connection to...

To echo the previous post, could you let us know what version number of the MOD54417 module will be able to have J2[17] and J2[18] configurable for I2C use?

Thanks,

Ron

I was looking into using J2[17] or J2[18] as in input-only GPIO, so went to pinconstant.h to see what the defined parameter to use for configuring one of these pins appropriately (i.e., PINJ2_nn_<USAGE> parameter) - obviously, I hadn't gotten to the point of finding and reading through this thread, ...

Thanks rnixon for your reply. It does appear that I've managed to clobber the module's device ID - looking for it with IPSetup or AutoUpdate shows the 54417 module with the correct IP addresses, but with garbage (or no) characters in the device ID field for the module. What I need is a way to restor...

Hi - Not quite '"bricked", but *somehow* I've managed to wipe out my MOD54417 notion of what it is :shock: , as shown from AutoUpdate when I try to download a new version of the app I'm working on: NetBurner Device Platform..JPG If I use the "magic" jumper, AutoUpdate will see it...