Astrobe Forum

Astrobe's SYSTEM offers easy access to the PC, LNK, SP, and FP registers, both readable and writable, which is very -- very! -- useful to muck around with separate stacks for each process, exception handling (errors, faults), and other low level code of that nature. To separate the process stacks (t...

I agree, the parameter list for this procedure is on the edge, but still just acceptable. But defining a record type for just some config parameters is worth a thought, especially as I already factored out one parameter, assuming a default value (ptype := Essential), and providing an additional conf...

Indeed, using an open array is the work-around, combined with an ASSERT to check the length. The API just gets less expressive and "compile-time-checkable" this way: TYPE ProcessID* = ARRAY 4 OF CHAR; PROCEDURE Init*(p: Process; proc: Coroutines.PROC; stack: ARRAY OF BYTE; startAfter: INTEGER; perio...

Thanks. Renaming the file as advised does the trick.

I don't quite understand why I cannot pass a string literal in this case: MODULE M; TYPE Pid = ARRAY 4 OF CHAR; VAR id: Pid; id2: ARRAY 4 OF CHAR; PROCEDURE P(pid: Pid); END P; BEGIN P("id"); (* error *) id := "id"; P(id); (* ok *) id2 := "id"; P(id2) (* ok *) END M. Isn't "id" a string, which by it...

Thanks! However, I do not get this working OMM, ie. I still see the same colouring as before. I replaced the file and restarted Astrobe. Do I need to reset any preference setting? I still have the personal edition installed in addition to the professional one -- could this interfere?

Commenting out a block of code with nested comments, I seem to have run into a limitation of the syntax colouring related to comments, see screenshot. It's purely "cosmetic", as the compiler recognises the comments correctly.

Are the modules initialised in the order as listed in the ".map" file? Background: I want to "intercept" the reset process at some point. Upon run-errors or some MCU faults, my process scheduler can reset and restart a single process and continue, as an attempt to keep the (unsupervised) program goi...

Another version of the stack trace procedure. The above one stops at the address of the last FP-entry on the stack, this one stops with the contents of this FP-entry. I ran into the problem of where to stop the stack trace when I implemented simple coroutines (as basis for a cooperative task schedul...

Thanks for your explanation. Looks (sounds) like much added complexity without sufficient benefits indeed.