Re: [gpsim-devel] PIC18F4550 increment PC=0x4000 == memory size 0x4000

[Rob P. <lis...@fl...>]

On 25/12/2022 14:48, kus...@sp... wrote:
>
> So my test hack was just wrong.
>
> But I'm now thinking if there is (also) a problem witht .cod file 
> generated by gpasm.
> Reading through cod.cc <http://cod.cc> I I find:
>
>  * Memory map table - describes the ranges of memory used in the 
> processor.
>
> If this refers to the actuall processor type and not just what is 
> compiled for that particular piece of code then if might be that the 
> processor spec for gpasm is faulty in someway.
>
> This rabbit hole gets deeper all the time.
>
I'm not really sure it does.

The message you are seeing is generated at line 125 of pic-registers.cc 
and indicates only that the program execution has reached the top of 
memory and is wrapping round to the start. This is actually normal for 
some 12-bit CPUs where the reset address is the last word of flash and 
contains a calibration value for the internal oscillator.

The only problem, and what is causing you to think it's all wrong, is 
that the code that produces the message was written for a 12-bit CPU and 
reports the values simply as internal indices. That matches proper 
addresses for 12-bit and 14-bit cores but needs to be doubled for the 
16-bit.

Oh, and the other problem is that your code under test is escaping out 
into empty memory...