getNextTask() in Schedule_Int returns invalid task IDs on some compilers about firmware_v1 HOT 3 CLOSED

I never heard about port for LEON 3 so I have to support that it may be incomplete.

Anyway I guess the problem is that the variable ReadyVar is not zero. Per default global variables shall be set to 0 in C90. So ReadyVar per default shall be an array of many queues which are all empty. In your LEON 3 port it seems not to be the case. This may happens when the startup code tries to optimize the startup time and does not set all global variables to zero. Is a common behaviour in embedded ECUs but is not conform to C.

Please do the following, set a break point in main, reset the board and when main is reached check the content of ReadyVar. If is not all 0 values something is wrong during the initialization. :(

from firmware_v1.

Did as you said and indeed I found that the compiler was not to blame for the problem. When execution is stopped exactly at the start of main() the structure is initialized to 0.

Kept digging and found that there was a memory corruption problem very early in the initialization code for my port, a buffer overrun during an interrupt handling routine that was causing parts parts of adjacent data structures to be partially overwritten.

My fault, I'm sorry.

As far a I'm concerned this issue is ready to be closed.

from firmware_v1.

Good to know that you found the solution to the problem. :)

Am 11.10.2016 7:43 PM schrieb "Gerardo Puga" [email protected]:

Closed #446 #446.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#446 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AG7km6O7lS9_rTi7MMqM5WiH8ve0Zs3qks5qy8q6gaJpZM4KRr53
.

from firmware_v1.