@ersmith said:
I'd really need more context to try to guess what's wrong. In one of your other posts you mentioned using a conditional debug in assembly (like if_b DEBUG()). The hardware doesn't actually support that, and so it should produce an error in flexprop, but if it somehow gets through it'll do weird things.
The particular weird thing that happens (when C=0 in that case) is that INT0 gets triggered without latching the BRK argument. So it'll repeat the processing of the most recent debug statement. If the cog never did a debug before, I think it defaults to $00, which IIRC triggers single step mode, which FlexProp doesn't have a way to handle. That would look a lot like a hard crash (incl. garbage spew on the terminal).
Comments
The particular weird thing that happens (when C=0 in that case) is that INT0 gets triggered without latching the BRK argument. So it'll repeat the processing of the most recent debug statement. If the cog never did a debug before, I think it defaults to $00, which IIRC triggers single step mode, which FlexProp doesn't have a way to handle. That would look a lot like a hard crash (incl. garbage spew on the terminal).