AutoUpdate Fails in NNDK 2.5.0

[acreque]

I am running NetBurner Eclipse 2.5.0 on a new Dell Inspiron 1545 laptop with Windows 7 installed. The AutoUpdate suddenly, for no apparent reason, fails to download to the target MOD5272 and terminates with a timeout error. Interestingly, the same thing happened with the previous version of the NNDK (2.4.x). Worked for awhile and then suddenly stopped. I have tried all of the recommended fixes: compatibility settings, run as admin, firewall, etc. The IPSetup tool has no problem finding the MOD5272, and I can ping, and even bring up the web page (per the Tic-Tac-Toe demo program). I also tried uninstalling and reinstalling the NNDK, but that didn't work either.

Anybody know what I can do to get this feature working again?

[tod]

Have you read on the FAQ on Windows 7? Sounds like you may have but you didn't mention if AutoUpdate works outside of Eclipse.

[acreque]

Yes, I had read that FAQ (and tried all the recommended fixes without success). Also, I did try AutoUpdate outside of NBEclipse. I thought it might be an issue with the app shortcut, but working directly with the app icon (properties) did not resolve the problem.

[Ridgeglider]

What code are you running on the the Mod5272 besides AutoUpdate? Is something corrupting the stack, or retaining priority in one task, or using up all the buffers or connections? Does AutoUpdate fail with any of the example programs? Does NBFind still find the module? I would doubt a problem in AutoUpdate, Windows 7, Eclipse, etc until all these other more likely possibilities in your App are ruled out. In my experience, the platform is pretty solid.

[acreque]

I appreciate the input, because I'm starting to run out of ideas here.

I had assumed that code I wrote and downloaded to the MOD5272 had somehow trashed it, so I flashed the Mod5272FactoryDemo_APP.s19 file to the device. That code seems to work okay: IP Setup Tool locates the device, ping works, the web page comes up and the Tic-Tac-Toe demo works okay (all outside of NBEclipse). But the AutoUpdate still fails with timeout error.

So I can use the FLA monitor feature to flash via serial port, but cannot download via the EtherNet.

[rnixon]

If you repeatedly run autoupdate.exe with the Mod5272FactoryDemo_APP.s19 file, does it still fail? That would tell you if it was in your app or not.

[acreque]

Um, not exactly sure what you mean there. The steps I've tried are

1) Use FLA to (successfully) download the Mod5272FactoryDemo_APP.s19
2) Verify success via IPSetup (it finds the MOD5272 device)
3) Verify a valid app running on the device (web page appears to launch correctly)

4) Run AutoUpdate to re-download the Mod5272FactoryDemo_APP.s19

At this point, the AutoUpdate appears unresponsive: no change in the progress bar. Eventually, the timeout error.

[Ridgeglider]

Is there more than one NB on your network? I have seen applications running on the NB modules that seem to be working but that have messed up the UDP packets used by AutoUpdate. This can make all modules act unpredicatably so NBFind and AutoUpdate fail.Therefore, I'd sugget shutting down any other NB modules and using only one that's running the FactoryDemo. If things get really crazy it is not unreasonable to reset your router and to start shutting down other equipment hanging on the network too. On a clean network, can you see your module using the NBFind tool? After a restart of the module, can you AudoUpdate it? You can also try running NBFind and AutoUpdate on a different PC to see if your workstation's setup is the culprit. It is easy to rename your old Nburn directory (to NburnOld), reinstall the basic NB tools, and try AutoUpdate and NBFind. If these utilities fail on two PCs after a clean install, the issue is something in the application code. You can revert to the previous install by deleting the new Nburn directory and renaming the previous NburnOld back to Nburn.

[tod]

I had this same problem with my Dell laptop on Windows 7 when I first got it. I didn't write down exactly what I did but eventually I got it working and here are the steps as near as I can remember them. (BTW, I'm not sure what the differences are between AutoUpdate.exe and TcpUpdate.exe but I did this for both of them. Also I noticed from your wording that it sounds like you are just hitting the Update button once AutoUpdate boots. Instead use the Find... button I've been assuming that it can't find the board.)

1. Reboot your pc (OK you probably don't have to do this but it's a new computer so it should be fast).
2. Turn OFF your firewall. I imagine you got McAfee with your dell so open the Security Center and select the "Resume when I restart my PC" option. Using the control panel make sure that the built-in Windows firewall is off too.
3. Using Windows Explorer go to nburn\pcbin\AutoUpdate.exe and right click and select the "Troubleshoot compatability" mode. Accept the recommended settings.
4. Run AutoUpdate (verify it shows 2.0 in the title bar) Click Find, if it doesn't find the NB board go to step 5
5. Go back to Windows Explorer, right-click AutoUpdate and select "Run as Administrator" try to find the board again.

[acreque]

Only one NB device here and no router. I'm working with a basic laptop-crossover cable-dev kit, just trying to get some prototype code up and running for a new project.

I have tried the NBEclipse rename-and-reinstall trick a few times now, but it doesn't fix the problem.

I disabled the wireless networking junk on the laptop, thinking that might be causing a conflict ...

NBFind (inside NBEclipse) does seem to work: It correctly shows the MOD5272 device, IP address, MAC address, etc.

Note: When I click on the "Find" button from AutoUpdate, it fails to locate or identify the NB device.

My next step is to try a fresh install on another PC or laptop. But here's the rub: I did have this all working on my current setup for a couple weeks, including the AutoUpdate. And then the AutoUpdate suddenly stopped working between one download and the next. Something I wrote? I'd like to purge the NB and get it back to factory default settings. Is the FactoryDemo app sufficient for this?