Autoupdate not working on MOD54415

[nicobari]

Hi,
I was able to use Autoupdate before to load ode onto my MOD54415. It used to stop working between but powering off and on the module used to fix that problem but last time it stopped working I haven't been able to make Autoupdate work again. Did anyone face similar problem? I could use serial port to load the code if I change the IP address of the module to 0.0.0.0. Is anyone else facing similar problems with Autoupdate?

Regards,
TM

[Forrest]

Hello,
Are you sure that the devices are an application that supports auto update. Can you see the device and IPSetup? Is it possible that DHCP assigned new IP address to the device, but NBEclipse is still pointed at the old IP?

[nicobari]

hI,
Sorry I forgot to mention that I am using MOD54415 which support autoupdate, and on start up I see the device and IPsetup. I am not updating the IP in my code and I am also not using DHCP in my code. However how can I know whether DHCP is assigning a new IP address or not to my module?

Thank you.

Regards,
Tanmay

[rnixon]

Use IPsetup. If you set the IP to 0.0.0.0, then DHCP should assign one.
A very important note here that I'm not sure you understood from the previous poster is that *your* application code must make the dhcp or autoupdate function calls or they will not be active.

[nicobari]

Hi,
Thanks rnixon for the reply. I am calling Autoupdate from my application code but I don't understand the use of calling DHCP function as I am assigning static ip (not 0.0.0.0). I changed to 0.0.0.0 because serial upload won't work if I had anything else setup. Although I don't have any explanation as to why ipsetup should effect serial update. Thanks again.

Regards,
TM

[dciliske]

I'm not entirely sure what you're saying the issue with serial setup was, but I should clarify the comments made about IPSetup.

IPSetup will only show an address of 0.0.0.0 if the device has no configured address at all. This is relevant because as of 2.6.0, the standard system stack (i.e. not the L2Es') creates an AutoIP interface that will only show up in IPSetup if the main interface is not configured. So, if you see an address of 169.254.XXX.XXX, that's an AutoIP address. That means if your computer has an actual local LAN IP, it's probably on a different subnet, which brings me to my next point...

Often times when you can't communicate with a device over the network when you've given it a static address, it's because you've given it an address outside your computers subnet. For example, if your computer's IP is 192.168.0.104, and you give the Netburner an IP of 10.0.0.4, you probably won't be able to talk to it. This is because most of the time your netmask is something like 255.255.255.0. This will even prevent you from talking to a device at 192.168.1.XXX.

Any of this help? Did you get AutoUpdate to work?

[nicobari]

Hi,
My computer network configuration is
IP-157.182.196.98
Mask-255.255.255.0
Default Gateway-157.182.196.1

For my MOD54415 it is
IP-157.182.196.85
Mask-255.255.255.0
Default Gateway-157.182.196.1

I was able to work with this configuration and also with an IP address of 157.182.196.80 in the past but now its not working. I guess this configurations are similar to what you explained earlier.

Now coming to serial update when I hit "A" after start up and type "FLA" and send my code to my Netburner module I see asterisk flying through my screen only to show download failed at the end. This happens when my IP is set up as 157.182.196.85.

But when I delete this IP and its set back to 0.0.0.0 the serial update starts working. So this is currently the only way I have been able to upload code now. Thanks for your help and I hope I have been able to clear some confusion.

Regards,
TM

[nicobari]

Hi,
I changed my IP to 157.182.196.75 and now it started working again!!!! It seems like some IP conflict?

Regards,
TM

[Ridgeglider]

The 1st step is to configure the IP to either a fixed static IP, or to use DHCP using IPSetup.

Next, when you create a project you can (but don't have to) specify the IP for your target. This configuration should match what you set using IPSetup, or perhaps in the case of using DHCP, you can search for what IP has been assigned to your target.

Finally, and this is where you may be having trouble, to download code to your target, you create a "Run Configuration" for the project that tells Eclipse how, and where to download the code. You create a Run Configuration initially by selecting (in the Project Explorer) a project that has compiled and linked successfully, then right clicking to "Run As", then "NB Application".

Typically, this Run Configuration uses the IP assigned in the previous step, but note that if the target IP changes for any of several reasons, a Run Configuration created for an earlier IP will fail. To examine these settings, select the project in the Project Explorer, right click, select Properties and then look at BOTH the IP setup spec'd under the "NetBurner Options" and the "Run/Debug Settings" items.

[nicobari]

Hi,
That was helpful. Thank you.

Regards,
TM