NetBurner Community Forum

I'm not saying to comment anything out, but to add the code highlighted in yellow. There is no need to change the mode, or to expect the end user to do so. Seems that you can just update the function as shown, to make WaitForActiveNetwork() recognize that it doesn't need to keep spinning if the boar...

Well, yeah, I could turn off DHCP (how/why would I want to do that?), but would it still be able to come up with an AutoIP address if I did that? I'm suggesting that you change the system code to fix what looks like a bug. :) But I don't know enough about the system to know if my hack will have unde...

Just noticed that WaitForActiveNetwork always times out on my Win10 PC, which is using a secondary NIC that has nothing else connected but the MODM7AE70. Is this a valid way to fix that in \nburn\nbrtos\source\dhcpc.cpp? https://i.imgur.com/LXnvB1q.png There doesn't seem to be a dedicated "Auto...

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 ...