NNDK 2.6.0 for Windows - Release Notes?

[greengene]

I downloaded and installed this but RevisionHistory.txt is for 2.5.3.

Can someone at NB post them somewhere? hopefully without requiring
the complete download again.

TIA

[greengene]

did a diff and saw some interesting changes - a couple in the ip/tcp area
that i may need to look at further, e.g., accept(), ARP and sysmetric routing,
collision monitoring(?).
also like the I2CMasterResetPeripheral() - looks better than what i had been doing.

[Forrest]

Sorry this did not get included. I am formatting it now. Ill post it here and on support by the end of the day.

/edit The release notes are now posted on this forum

[Ridgeglider]

Forrest:
I am pretty sure that the PC version of the Rel_2_6_0_010
NNDK installer omits installation of all the usual contents of the C:\nburn\docs\platform directory and subfolders

[Ridgeglider]

Forrest: Here's another issue. I thought I'd posted it earlier, but I guess not. In the PC version of Rel Rel_2_6_0_010, unlike other recent releases, when you create a run configuration, it has become necessary to enter the debug executable "m68k-elf-gdb" into the GDB debugger field on the Debugger tab of the run configuration dialog boxes:

[ecasey]

Forrest,

I noticed Ridgeglider's issues as well, it didn't set up my MOD5270B directory in the C:\nburn\docs\platform directory. It did set up MOD5270 and MOD5282 directories.

Also, one project that I opened refused to close. On closing NBEclipse, it gave me a dialog box to cancel the "Close" operation, but doing that just hung the program.

Ed

[khoney]

I just installed 2.6.0 into a separate directory from my 2.5.2, and I imported one of the projects from the 2.5.2 workspace into the 2.6 workspace. It imported and automatically rebuilt, but at the end of the build it says "NNDK release tag version:Rel_2_5_2".

Did I really build it with 2.6.0???

If I look at the build properties, my include paths for everything do not reference the new installation. I guess I thought that as part of an import, those paths would change to point to the new compiler, linker, etc.

Does everything have to manually be changed to point to my 2.6.0 install? Are there any documents available that describe what to do for a side-by-side installation?