NetBurner Community Forum

OK thanks I'll try THAT. I did create a test project which built ok but I get the following error saving the workbench when exiting Eclipse. Problems occurred while trying to save the state of the workbench. Internal Error org.eclipse.core.internal.localstore.HistoryStore2.<init>(Lorg/eclipse/core/i...

Is eclipse Rel22_rc2 capable of running on vista x64? I've tried and it shows internal errors when saving and importing existing projects.
If not does the newest release work?

Thanks

Well after much gnashing of teeth and clean installs across several PC's I think I've uncovered what's happening. First, off topic, there's a problem on some NNDK installs with the rebuild system files heading in eclipse not picking up the right make file. Its not obvious, or at least I couldn't fin...

Further to my last post, I've discovered that a version of the simple test app runs fine under the debug configuration, but compiled under the release configuration it restarts every few seconds.

Thanks for the various suggestions. Here's where I am right now. I ruled out a stack problem by adding a semi-recursive call in place of the OSTimeDLy() call and it ran fine. However moving the OSTimeDly() around the code and commenting and uncommenting various other calls in the code had random res...

Thanks, I agree that the behaviour seems to point to that, however; I put an infinite loop before the trap and dumped the stack before entering the loop, basically the second line of main(). the main task is still priority 10 at this point. uc/OS Stacks Prio StackPtr Stack Bottom Free Now Minimum Fr...

Doubled the stack size with a defined amount of 65k, same problem. Just to be sure I wasn't going insane I reloaded the original app (compiled under NNDK 21 rc4). It runs fine and here's the stack report from that. 50 is the main task. OS Stacks Prio StackPtr Stack Bottom Free Now Minimum Free 63 | ...

Thanks for the feedback. The large stack is needed to handle constructors initialized before main() in a multi-channel (64 channel in 8 out) application .i.e. every array or object initialized is multiplied by (64+8) in terms of amount of storage required and unfortunately the main body of the code ...

Sadly the same problem exists when I comment out #define ENABLE_SRAM_SYS.

It is a possibility but I'm confused because it worked under the previous NNDK. (I'm installing the new one to experiment with the better transmit and receive performance). We do need larger stacks and we have a modified constants.h as follows (NB_SSH_SUPPORTED not defined) /* Stack definitions, SSH...