There's nothing wrong with first command, can't see why that fails. That's a BUG...jsa wrote: ↑2024 Jan 13, 08:07In light of the math hex/dec issue in my last post, 71, is that hex or dec??wwhite wrote: ↑2024 Jan 11, 23:10 Well, I have 5.0.5 working the best I can with my dir.
Now I get the following in msg from SAD:Code: Select all
## sym 2 "CPU_OK" [B 6] ## Error - '[' expected ## sym 4 "AD_Cmd" W [B 0 71] ## Error - '[' expected after '_Cmd" ' ## sym 5 "WDG_Timer" W [B 0 71] ## Error - '[' expected after 'imer" '
TVRfan what should it be and is it a contributing bug??
The next two fail because the 'W' is outside the brackets - all options MUST be tied to a data item, and each set of '[ ]' is a new data item. So that's right, cmd needs a '['
You can have nested data items i.e. [W [B0]] but 'bit 0' is still a separate data item from a syntax point of view. One extra 'global' (for that command) is allowed, format is [$ ...], only for some commands (e.g. struct) which is used for layout and other things.
NOTE - there are several bugs reported in the command reader to be found - it seems to report the wrong error a lot, i.e. "Duplicate Command" when it's "invalid address" , and "overlaps" when it's not.
The '71' should be rejected as an invalid bit number, only 0-31 is allowed (a 'long') so again, wrong error reported..