NBEclipse won't update app; first time user confusion

[ScottM]

I tried to set up my new development kit yesterday, and got nowhere. I'm missing something but I'm not seeing it; help appreciated.

1. I hook up the 5270 to ethernet and USB. It powers up, and from my DHCP server I can see that it's acquired an IP address. From my laptop, I can ping it and it responds. So the ethernet is ok.

2. In IPSetup, all the numbers on the left hand side are 0's, and the only device listed on the right is this new board, reporting the same IP as my DHCP server sees. So clearly the board is ok.

3. I can see it boot in mtty. The output ends with a message about TCP. So the USB connection is good.

4. I create a C++ application called "test", containing the default application code, which apparently just writes a message to stdout and then goes into a sleep loop.

5. I try to Run it. Autoupdate comes up, sits there doing nothing for a time, and then times out.

I'm running Vista. Winders defender is off. I don't think I have any other fancy port blocking. Everything is on the same LAN with no funny firewalls involved.

Anyone know what I'm missing? I have a ticket in, but maybe it's something very simple..

[rnixon]

To make sure everything is at factory default, I would do a serial download using MTTTY of the \nburn\mod5270\original\Mod5270FactoryApp_APP.s19 file. Here is a link to the monitor flash download instructions:
http://www.netburner.com/support/faq.html#mtttydl.

[tod]

What program is in your 5270 right now? If it is the factory default Skip to Step 2. If your simple program has already downloaded once your problem is you probably didn't enable AutoUpdate when you created your program. Follow Rnixon's advice and reinstall with MTTY a factory default program. (IF you need more help with that let us know).

1. Then start over creating your sample app but use the wizard and don't hit the FINISH button too soon. Make sure to choose "Netburner Device Executable" when starting. After the screen that has the search button , use the NEXT button and you willl get to the screen with the checkboxes. Make sure you check the "AutoUpdate" box.

2. One thing that is easy to screw up is when you get your default 5270 it gets an address like 192.168.1.32. Then you run a program with DHCP and your DHCP assigns a different IP. Then when you go back to eclipse, it still thinks your board is at 32 so when it runs AutoUpdate it can never find your board. This is easy to fix. Just hit the cancel button. You see the AutoUpdate normal screen and you can type in the new address and then hit Update. This will happen every time until you update the fun configuration. In eclipse go to the run configurations menu, click on the configuration you are using, and change the value in the Target IP: box. (Again if you need more detail let me know and I'll upload some screen shots).

[ScottM]

It looks like I do need more help.

I've tried to follow the directions at
http://www.netburner.com/support/faq.html#mtttydl.

Ignoring the fact they are written for a serial port+separate power supply, and I have USB, I got as far as running MTTY and trying to transfer the original factory installed application, which in my case is supposed to be at
c:\Nburn\MOD5270\original

Well, there's no *.s19 files in that directory; only a lib directory with .a files. The only file like that is

C:\nburn\SB70\original\SB70App_APP.s19

which makes me wonder if I was shipped the wrong install disk. (Yes, I did a fresh install of everything to be certain)

I'm not going to transfer the SB70 image down unless support says so because I don't want smoke to pour out.

[Chris Ruff]

The odds are very small that you can hurt anything by downloading a netburner-generated 5270 app into a 5270, so don't sweat the smoke.

Your original post reads like the 5270 is working fine, booting fine. There should be no reason to re-download a netburner factory app.

Your original problem appeared to be that AutoUpdate was sending the records to the wrong IP address. Follow Tod's advice:

"2. One thing that is easy to screw up is when you get your default 5270 it gets an address like 192.168.1.32. Then you run a program with DHCP and your DHCP assigns a different IP. Then when you go back to eclipse, it still thinks your board is at 32 so when it runs AutoUpdate it can never find your board. This is easy to fix. Just hit the cancel button. You see the AutoUpdate normal screen and you can type in the new address and then hit Update. ..."

once you have updated your target once it will work every time after that (AutoUpdate, that is, don't know about your altered code)

Chris

[tod]

I'm pretty sure you don't want to download an SB70 app into a MOD5270 board. But you probably did get the right install. I don't have have any prebuilt _APP files for my other boards either. However, you do have all the source code for the example app for your 5270. I'll make you a quick movie on how to build and load the factory default. In the meantime I'm attaching a prebuilt _app file for the Mod5270 factory demo. You can use MTTY to download this over the serial connection. Once it is there, then you can use the TCP/IP download. But make sure the project you download has AutoUpdate capabilities.

[tod]

Make that popcorn and get five free minutes. Here's the link to a movie showing you how to build the factory demo from the example source files.
http://www.youtube.com/watch?v=tSqHhOM_Kvs

The screens are much more readable if you expand the size of the window and increase the video quality to at least 480p.
I did this kind of fast and made the mistake of not putting my 5270 on the network. It does prove that you can download and run a file built for one platform to another. It helps a lot that there is nothing hardware specific going on here so the program runs fine. If on the Search dialog page of the wizard I had told eclipse this was a 5270, then when it went to download over Ethernet it would have failed and told me the board at the target address was the wrong type.

[rnixon]

Sounds like tod has it covered, but you could also look at the nbeclipse getting started guide on how to import an example program. Then use those guidelines to build the Mod5270FactoryApplication; the source code should be in \nburn\examples\mod5270. I would not use the SB70. While there might not be any damage physically, who knows how flash is mapped and you don't want to overwrite anything important.

[ScottM]

And... the light dawns.

Netburner support sent me the default factory application. and using MTTY and the FLA command I got that pushed to the board. On a reset, I saw the nb> prompt, typed BOOT, and saw the factory app run. Awesomeness.

Then I tried to download a project I'd built. All I did was create a new C++ project, look at the default .cpp file is provides, which doesn't do much, built for debug and tried a Run command.

Mtty showed an odd message come up, and not the "Application started\n" I expected from the source code. OK, I did something wrong again... Try the Debug command.

Autoupdate came up... and hung again, just like last time. Huh?!

So then I did what I should have done from the beginning - set the font size in mtty to something I can actually *read*. Then I was able to make out the "Initialized GDP tcp" message the program had printed, and looking at the source code... Hm, under that #ifdef _DEBUG, what's this InitializeNetworkGDB_and_Wait() call?

Well, I don't know what it's waiting for (clearly not a Carriage Return in Mtty), but it's suddenly obvious that 1) my test program was running after all, 2) InitializeNetworkGDB_and_Wait() outputs that message about GDP tcp and waits, 3) I don't know what it's waiting for but 4) as long as it's waiting, you can't upload a new program via autoupdate. (But it responds to ping just fine).

So while I clearly have a great deal to learn about this environment... at least I can reflash the board now, and just maybe, start writing some code.

Netburner: definitely not networking in one day, but now I think I have a shot at networking Real Soon Now.

Thanks for the effort, folk.

[tod]

It's waiting for you connect with the debugger.

In Eclipse there are two buttons to download an app. One downloads the debug version (it has an icon of a bug) and the other downloads the release version (it is the green play icon)

The release build is put in your RELEASE directory and the Debug build is put in your DEBUG directory. To get started you should just download the RELEASE build and then when you have things working go read up on how to use the debugger.