DEFINE RESET_ORG and DEC modifier issue

[Marcick]

If you don't care too much to optimize, it's not difficult to arrive above 64k. For example I use a lot of Hserout messages just for debug of what the program is doing.
Really, a PIC18 is much more powerful than what I need

[Marcick]

From Charles: "I'm afraid this is a limitation of PBP that probably won't be changed. The library routines (assembly language for high-level commands like HSEROUT) were written with the assumption that they would be in memory below 64K. They are the first thing placed after the RESET_ORG address. When I tested a variant of your code, the maximum address that could be safely defined was 0FFE4h. That limit will move down every time you use a new high level command which triggers a library inclusion.
"

[richard]

it's not difficult to arrive above 64k. For example I use a lot of Hserout messages just for debug of what the program is doing.

do you realise that hserout messages of a constant str type are the least efficient way to store and retrieve text ?
ditto for arraywrite

[Marcick]

uhm ... how do you send a message to the serial port with ArrayWrite ?

[richard]

arraywrite to a buffer then hserout str buffer

[Marcick]

I'll do some test, thank you

[Marcick]

arraywrite to a buffer then hserout str buffer

These are my result:

1) simple program with some code and 1 line as below is 7099 bytes

	Hserout2["nel mezzo del cammin di nostra vita",13,10]

2) same program with 11 line like that is 9319 bytes, so each Hserout2 eat 222 bytes

3) simple program with some code plus this as below is 7157 bytes

	buf	VAR BYTE[200]
	arraywrite buf,["nel mezzo del cammin di nostra vita",13,10]
	gosub send

send:
	Hserout2[str buf\200]
	return

4) same program above but with 11 "arraywrite + send" is 9497 bytes, so each Hserout eat 234 bytes

Looks like it's not as you say. I did this test with PBP Long option enabled, maybe without the results are different ?

[richard]

i think you misunderstand neither method is efficient
two hunted bytes to store a message 32 or so bytes long , not good

[Marcick]

i think you misunderstand neither method is efficient
two hunted bytes to store a message 32 or so bytes long , not good

I agree ... please explain how would you do. Of course debug strings are different and mixed also (fixed test, formatted variables, etc). Not possible to have them flashed in code memory.