DEFINE RESET_ORG and DEC modifier issue

[HenrikOlsson]

Yeah, until you here from Charles I'd be very careful with pushing the library routines beyond the 64k barrier.

I did compile the code and I did look at the .lst but I didn't see/understood the issue, nice work Richard! I know you've mostly moved on but please don't leave ;-)

/Henrik.

[Marcick]

Charles says "I'll presume it's a bug and try to figure it out."
Let's wait.
I wonder if we could have same problem also without DEFINE RESET_ORG, just with code larger than 64k .....

[richard]

i have never written a program that big with pbp , in fact if my code {excluding data fonts etc} got bigger than 16k would seriously think that a
8 bit pic with pbp is the wrong platform.

[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