Moving from 6.8.1 to 6.9.2 Breaks my project

Real-Time Embedded Frameworks based on active objects & state machines

Brought to you by: quantum-leaps

Moving from 6.8.1 to 6.9.2 Breaks my project

Forum: Free Support

Created: 2021-03-05

Updated: 2021-03-15

Steve - 2021-03-05

Updating to 6.9.2 (also tried 6.9.2a) breaks my project. The MSP430FR5969 continually restarts as if a watchdog is timing out. The watchdog is disabled and the project runs in 6.8.1.

I was tracking down a problem, which might be the subject of another post, with the project and decided to try 6.9.2 to see if the symptoms changed. I will continue to investigate. Would appreciate any ideas.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Panopticon - 2021-03-05

Steve -- did you happen to look yet at the diffs between 6.9.2 and 6.8.1? I haven't but might do that later today. I'm guessing there were no changes in the MSP port, so the only relevant deltas would be in the framework itself?

Actually just checked 6.9.2 against 6.7.0, the MSP430 port directory differences look innocuous -- just adding "U" suffixes to force integer literals to unsigned...

I guess you don't know how far it gets, for example does QF_run() complete and start running the AOs? Do you have a breakpoint in the Q_onAssert() function in case the framework is asserting?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Steve - 2021-03-08

Not had time to check, I am up against a deadline. I will take a look when I have a chance to dig into things a bit more.

Thanks

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Steve - 2021-03-11

My bad, I had forgotten to update QF_MAX_ACTIVE in qf_port.h. Symtoms when stepping thru the code was as soon as I tried to start AO 9 the MSP430 would reset. Took me a while to get the TI debug to work correctly.

FYI when using bitfields there can be problems when compiling in debug mode that causes a link error. Took me a little while to find the right settings where I could step thru the code in release mode and find my problem. The bug has been duplicated/verified by TI and they are working the problem.

unresolved symbol __mspabi_srli_6

Think we are done with this one.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Quantum Leaps - 2021-03-11

Hi Steve,
I'm glad to hear that most of your issues with migrating to QP 6.9.2 seem to be resolved.

For the future, perhaps it would be a good idea to put a big comment in any QP ports that you have modified, so that when you upgrade, you'll see what has changed.

Or, come to think, perhaps even better would be to put your modified port(s) in a new directory, (which could be in qpc\ports), but under a different name. That way, when you upgrade QP, you will immediately see that your applications won't compile (because your directory will be missing). I hope you get the idea.

--MMS

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Steve - 2021-03-15

Yes, I have already done that. But, in a slightly different way.
Regards

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Log in to post a comment.