Does anyone know of any reason that the Netburner EFFS might not be able to handle a Duracell 2GB SD card?
I have an older version of the code that has a 2GB limit, but this card is formatted as FAT32 and is only 2GB, so it seems that it should work, but my units are not able to read any of the ...
Search found 5 matches
- Fri Jun 08, 2012 11:11 am
- Forum: NetBurner Software
- Topic: Duracell 2GB SD card not working
- Replies: 0
- Views: 3091
- Fri Oct 21, 2011 3:38 pm
- Forum: NetBurner Software
- Topic: Rebuilding MONITOR program
- Replies: 1
- Views: 2406
Rebuilding MONITOR program
I am using a version of the MONITOR program that I think dates back to version 1.77 of the Netburner tools. The target processor is the MFC5272. I have been wanting to rebuild this monitor (I have all the source files) to add a RAM or ROM test function. We use the Netburner tools but our own ...
- Fri Feb 11, 2011 9:21 am
- Forum: NetBurner Software
- Topic: TICKS_PER_SECOND limits
- Replies: 5
- Views: 5476
Re: TICKS_PER_SECOND limits
[quote="pbreed"]Why do you need finer tick resolution?
The ONLY thing tick resolution sets is the granularity of time out.
Indeed that is precisely what I want, to have a task that times itself via OSTimeDly to run every 2 milliseconds, rather than some longer period. Is there some way to achieve ...
The ONLY thing tick resolution sets is the granularity of time out.
Indeed that is precisely what I want, to have a task that times itself via OSTimeDly to run every 2 milliseconds, rather than some longer period. Is there some way to achieve ...
- Tue Feb 08, 2011 1:14 pm
- Forum: NetBurner Software
- Topic: TICKS_PER_SECOND limits
- Replies: 5
- Views: 5476
TICKS_PER_SECOND limits
The version of the bsp.c for the Coldfire MCF5272 has the following lines:
#if (TICKS_PER_SECOND >200)
#error TICKS_PER_SECOND too fast
#endif
#if (TICKS_PER_SECOND <10)
#error TICKS_PER_SECOND too slow
#endif
What I would like to know is what was used to determine these limits. In particular, I ...
#if (TICKS_PER_SECOND >200)
#error TICKS_PER_SECOND too fast
#endif
#if (TICKS_PER_SECOND <10)
#error TICKS_PER_SECOND too slow
#endif
What I would like to know is what was used to determine these limits. In particular, I ...
- Wed Nov 10, 2010 1:46 pm
- Forum: NetBurner Software
- Topic: NNDK 2.50 release TCP/UDP fixes
- Replies: 0
- Views: 2817
NNDK 2.50 release TCP/UDP fixes
I have been using an earlier release of the Netburner tools, which I assume has the "race condition" problems listed in the release notes quoted here:
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 ...
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 ...