NetBurner Community Forum

Posted: **Fri Sep 10, 2010 3:25 pm**

For sanity sake I'd look in nburn\include\constants.h
In both the old and new environments and double check that some time in the distant past someone
did not change TICKS_PER_SEC in your old build.

Paul

Posted: **Tue Sep 14, 2010 1:30 am**

tod wrote:hector,
If you're willing to try an experiment and are using a 5270/72/82 family of boards. I have an example program up on the Wiki for Ajax. Grab the newer sample for AjaxII it is the link at the bottom without the folder icon. Unzip and then File->Import that into a new project. Build and load it. (I also have to go to the project properties, click on the NetBurner options, (you get an error), click on some other line, click back on the NetBurner options and set the Target platoform to your platform - this is just a quirk in the project import). Then Open a web browser and enter your board's IP address. I just did all the above steps (just to be sure) and it takes no more than 10 seconds for the web server to come up and then you should see screen updates every .5 seconds. The program also writes out a "." to MTTY every .5 seconds. If yours takes 2 minutes and the the screen updates are slower then we know something is awry in your NNDK installation and at least we have a common code base to experiment with. One of the demos may also work if one of them has a constant MTTY or web update.

Just an idea.

Tod

Hello tod,

I tried the example. The webserver and the debug output seem to work properly

I also checked constants.h and compared the values with the ones from the Dev-C++ environment. No differences at all (especially TICKS_PER_SECOND, which are both set to 20). So I guess the problem has to be in my application code (maybe a semaphore/task problem...).

NetBurner Community Forum

Problems transferring Dev-C++ 1.14 project to NEclipse

Re: Problems transferring Dev-C++ 1.14 project to NEclipse

Re: Problems transferring Dev-C++ 1.14 project to NEclipse