Honored Contributor
Honored ContributorI usually also test in hardware, but as the tests didn't korked, I tried to do it in the ISS simulator, in order to see if the problem was software or hardware.
The fact is that if I run it in the evaluation board (now I can), all the tests (that didn't worked before) work except "stress_threads". If I debug it, it runs until "main", and then continues. When I stop it, the value of PC is 0x10000 (more or less), which is not a valid address for executing code, isn't it? Obviously, the program doesn't works I've seen also that sometimes the console shows "Bad byte in chunk". NOW. I have activated xxx_STACK_CHECKING, and also CYGPKG_INFRA_DEBUG, because the previous option needs asserts activated. Now, when I run the "stress_threads", it says " ASSERT FAIL: <1>stream.cxx[585]Cyg_ErrNo Cyg_StdioStream::write() Stream object is not a valid stream! ASSERT FAIL: <1>stream.cxx [ 585] Cyg_ErrNo Cyg_StdioStream::write() " I have seen asserts like these many times while running my code. Asserts that, if a line of code is added (e.g. a printf) , disappear (sometimes, not always). I thought it was some part of my code that was wrong, but looking at this, I think there's another problem. Notice that this assert is happennig before "main", because I have the debugger configured to stop when the program user starts, and the asserts appears before that. Any idea? Alex
