HSEROUT using STR modifier - length parameter as variable not working

[HenrikOlsson]

it fails of course for more than 255 chrs

Of course, since the macro only uses the low byte of R4 to index the array. That would also make it fail when using a constant >255.

In any case, the "example" posted in the first place had a BYTE sized variable with a value of 40 and everything we've seen this far is that it should (and ideed does, for 18F at least) work. I think I compiled for 16F628 when I looked at the .lst yesterday.

flotulopex,
You're going to have to post code that we can just compile, assemble and program into a chip that shows the problem.

[flotulopex]

flotulopex,
You're going to have to post code that we can just compile, assemble and program into a chip that shows the problem.

Yup, I will do so asap.... Sorry, didn't have much time yesterday.

[Ioannis]

Charles replied:

Yes, I believe it can be trusted with a variable. I've used this form to receive a variable number of characters based on a length parameter received immediately prior to the string:

[wait($80),length,STR idstring\length]

So officially it is valid syntax.

Ioannis

[flotulopex]

For now, here a my two test programs with 16F690 and 18F1220.

Surprisingly (to me), both accept the STR length as variable in the 3 ways I'm using it (HSEROUT, SEROUT2 and DEBUG).

I'll go back to my current program and try again....