NetBurner Community Forum

Not an NB employee, and I just skimmed the thread, but: TCP_NODELAY is almost certainly your problem (or rather the lack of it.) Everybody who ever does anything with TCP/IP has to learn this lesson the hard way, it seems. :( To blame the right person, you need a time machine . Don't forget your gun...

Yes, MODM7AE70 on the carrier board. Just as an exercise, can you try to run the QuadSPIModule demo with P2[43] jumpered to P2[47] and verify that typed characters are echoed back? I'm using the USB connection provided by the carrier board, whichever UART that is. (Not urgent, as I've already switch...

A few questions -- 1) What's the difference between DSPIModule, QSPIModule, and plain old SPIModule? This is never really articulated in any docs or examples as far as I can tell. Yes, the nominal difference is the number of data lines that can be used, but the examples all seem to use only one data...

Thanks, Paul, looks good now. I just added case 'G': and let it fall through to the 'g' case.

This is a different question -- sorry, I should've probably started a new thread for it. The %G specifier is definitely broken. Please see the message right above your reply.

One more issue with printf() that actually does appear to be a real bug (no pun intended): printf("%g\n",4.25332E-14); printf("%G\n",4.25332E-14); printf("%g\n",4.25332); printf("%G\n",4.25332); printf("%g\n",-4.25332E-14); printf("%G\n",-4...

Hmm, OK, got it, I think. My impression (and experience so far) is that if a given task doesn't explicitly yield by pending on something (possibly via printf or some other function that itself will wait for a resource to become available), nothing other than interrupts will run, ever. Then, as soon ...

pbreed wrote: ↑Wed Apr 01, 2020 10:20 am If A higher priority task interupts the printf....

That leads to another question -- under what conditions could another task interrupt a printf() call?

The OS never performs preemptive task switching, correct?

The problem I always run into with documenting these things is that I know too much. I'm the person who designs those linker files these days after all! For things that are not 'driver' or 'software library' related, the question is always how to collect the information in a way that is accessible ...

Good to know, Dan -- thanks again for your help. FAST_USER_VAR bought me a 7x speedup. You guys might consider documenting this stuff. Now that I know what to Google for, I see a helpful blog entry from a couple of years ago, and there's a 2008-era NNDK Programming Guide .PDF floating around that ta...