wip_netInit

IoT Modules Development tools
1

hi all,

i didn’t realize it but the blue was much better than red, when i am irritated!

anyway, i have spent some time to get all my code from the VS5 IDE to M2M. now i am at a stand-still due to a the wip_netInit function call that causes a module reset (not seen in the code version compiled under VS5, and i am using all the same versions of things so there really should be no difference since both IDEs should be calling the tool chain in the same way).

Now i did a search for the wip_netInit on this forum and got 0 results, kinda strange. does anyone have any ideas why the wip_netInit would cause a modue reset? such a simple function that never casued me any problems is now a show-stopper.

thx,
M

2

Did the version of OpenAT remain the same as before? What version of OpenAT and which module do you use? It could be some memory problem.

3

I seem to recall, back in the mists of time when I first used it, that it caused my system to reset.
IIRC, increasing the stack size fixed it.

And, I think, stack size is one of the things affected by M2MStudio…

4

@blackyblack
i am using the q24pl003 with the following module versions:
-Using firmware version 657g00
-Using wiplib version 3.10.1034
-Using OS version 3.16.00

and the project was build last under VS5 using the module versions:
-Using firmware version 657g00
-Using wiplib version 3.10.1034
-Using OS version 3.16.00
-gcc version 4.01.2
-mingw version 3.8.0.1

@awneil
increasing the stack size as with ‘wm_apmCustomStack’, and if so to what size? Or is there a way to do it in m2m ide?

thanks for the replies guys!

5

I use a value of 1024 :slight_smile:

6

i ended up using 4096, now it works fine!

Thanks agian guys.