Home/Support/Support Forum/Connect ME 9210 programmable
Welcome to Digi Forum, where you can ask questions and receive answers from other members of the community.

Connect ME 9210 programmable

0 votes
Hello

any one had this issues with the DC-ME-Y402-C modules?
the serial port output:
Thread Name: HSV
Thread ID: 54485244
Thread Stack start address:002DB3C0
Thread stack end address: 00EDDBBF
Program counter:000609F8
Stack pointer:002269B0
Current program status register:20000097
R00:001FEBF4 R01:0C0C0C0C
R02:00000106 R03:00003578
R04:001FEBF4 R05:000000FE
R06:000009A0 R07:001FEBB4
R08:FFFFFFFF R09:002F081C
R10:00213070 R11:001FEBB4
R12:00000001
normally, the serial port will no output. if had this output, the e-mail server will not working in the application, and the module will not working then. but some modules download this application will working.
anyone had this issues? maybe some issues with the Thread? please give some suggestions

Thanks!
asked Sep 24, 2014 in NET+OS by superf4ur New to the Community (25 points)

Please log in or register to answer this question.

3 Answers

0 votes
This looks like memory corruption.

Make sure you are memset() ing '\0' all pointer variables before use, like TX_THREAD, TX_QUEUE etc...
If you are using any dynamic buffers for reading/writing values make it to pre-allocated buffers for now.

Thread stacks should be malloc'ed and cleared out to '\0' before use. Increase thread stack size also.

These are the steps that i followed when i got similar errors
answered Sep 24, 2014 by tuxembb Veteran of the Digi Community (288 points)
0 votes
Thread Name: HSV
this indicates the crash happened in the web server, but like tuxembb said it is most likely a memory corruption
answered Sep 25, 2014 by LeonidM Veteran of the Digi Community (3,028 points)
0 votes
The responses included so far are excellent. I would add the following:

When the pbuilder creates stub functions, they are made to be modified. In fact the "get" functions must be modified. For example, the standrd "get" stub functions begin with something like char * the return. It might end with return theReturn. This is returning a char * stack variable. Depending on timing that char * could be out of scope when returned to the web server engine and thus cause a crash looking like what you presented. At minimum, change char * theReturn to static char * theReturn. This will keep the variable in scope. Though be careful, doing so, the variable is now not cleared out on the next call to the function. So you'll need to memset it before use.

But in general, I'd be looking for a memory issue in one of your stub functions.
answered Sep 29, 2014 by dakotas_dad Veteran of the Digi Community (694 points)
...