Page 1 of 1

NNDK Beta release 2.5.0

Posted: Mon Oct 04, 2010 11:18 am
by Forrest
NNDK 2.5.0 is now out and available for download at http://support.netburner.com. Please report any issues in this thread or directly to support by submitting a new ticket at http://support.netburner.com.

Beta versions of our NNDK are released for evaluation purposes only. We do not recommend using this release in an end product until it has been thoroughly tested. As with all new releases, this will be a beta for the first 8-12 weeks while we await feedback. If no major issues are present, we will upgrade this to an official release.

Code: Select all

New in Release 2.5.0

New Platform
   Added support for SBL2eX
   Added support for SBL2eXA
   Added support for SBL2e Chips
SSL
   New new mail example
   New mailto function
SSH
   Added SSHServerUserKey and SSHMinimalServer examples
PPP
   Added 3rd UART support
   Added magic number support
WIFI
   Added QOS support
   Improved ad hoc support
   Added regulatory domain support
L2e
   Added new pins class
   New NTP Client code and example
   New http password example
   New post example
System
   Added ATCommands
   Added const char * GetReleaseTag(), which returns the current NNDKRelease tag
   Added OSSimpleTaskCreateSRAM, OSSimpleTaskCreatewNameSRAM to create tasks in SRAM
TCP/UDP
   Added selective acknowledgment (SACK)
   Added window scaling options
   Added out of order TCP user options
   New functions TcpGetSocketState, TcpAllDataACked, WaitForSocketFlush (see tcp.h)


Corrections in Release 2.5.0

SSL
   Fixed buffer error related to simultaneous RX/TX
Tools
   Fixed crashing bug in comphtml
   Updated Virtual Comm application with bug fix and added documentation
MOD5213
   Fixed bad system header in iosys.h
MOD5234
   changed interrupt levels and priorities in TPU to avoid conflicts
MCF5208 (License)
   Fixed interrupt vector issues with SetIntC
L2e
   Fixed monitor to set proper 50MHz CPU frequency
   Fixed serial timeout problem in L2e factory applications
   Fixed Post HTML bug in which variable would lose their last char
   Fixed bug that sent extraneous RST packets
   Fixed bug that caused lost SYN packets on connection, slowing down TCP connections
System
   GATHER_RANDOM is now enabled by default
   Fixed MS Vista/7 issue that caused autoupdate and IPSetup to sometimes fail
   Updated timezones calculation feature
   Updated taskscan stack size reporting to show bytes instead of DWORDs
   Fixed buffer overrun error in mailto
   Fixed error in mail subject lines
   Fixed stack alignment in OSTaskCreate when passed misaligned stack
TCP/UDP
   Fixed TCP timeout race condition
   Fixed TCP close race condition
   Updated window size on TCP connect and accept to not be 0
   Fixed ARP race condition causing network buffer corruption
I2C
   Changed interrupt from level 5 prio 1 to level 3 prio 4 to avoid CAN conflicts


Re: NNDK Beta release 2.5.0

Posted: Tue Nov 09, 2010 3:40 pm
by greengene
any feedback on this release yet?

Re: NNDK Beta release 2.5.0

Posted: Thu Dec 09, 2010 10:47 am
by k1mgy
I'm confused by the announcement today that NNDK 2.5.0 has been released as beta, when the root message in this thread indicates the same thing.

Re: NNDK Beta release 2.5.0

Posted: Thu Dec 09, 2010 11:18 am
by rsg
Today's release appears to be Beta 2.5.1...

Re: NNDK Beta release 2.5.0

Posted: Thu Dec 09, 2010 12:10 pm
by Forrest
Sorry,
When I edit an old post, if you subscribe to the email updates, it gets emailed out like a new post. It causes confusion, even here around the office. I was removing the 2.5.0 sticky.

In other news, the 2.5.1 sticky is now up
k1mgy wrote:I'm confused by the announcement today that NNDK 2.5.0 has been released as beta, when the root message in this thread indicates the same thing.

Re: NNDK Beta release 2.5.0

Posted: Thu Dec 09, 2010 1:56 pm
by k1mgy
Does this then indicate that 2.5.0 is the official production release? If so, how may it be acquired?

Re: NNDK Beta release 2.5.0

Posted: Thu Dec 09, 2010 2:00 pm
by Forrest
k1mgy wrote:Does this then indicate that 2.5.0 is the official production release? If so, how may it be acquired?
2.5.0 had some bugs that were addressed in 2.5.1. Because of those issues, we did not upgrade 2.5.0 to official release. 2.5.1 is a second try, and we hope to upgrade it to official release after a public testing period.