[Flashforth-devel] PIC18F14K50 + gpasm + gplink

[Tristan W. <ho...@tj...>]

Hello,

In preparation for my winter FlashForth project I thought I would try
using gpasm as assembler, and gplink as linker, with a
PIC18F14K50. Using them I got a working FlashForth 5 on my mcu, but I
have a question about the link process. This is what I did.

I am learning that each assembler/linker is different and gpasm found
fault where mpasm appeared not to [1],[2]. After editing the two clrf
statements that left the linker file issue [3].

[1]
usbcdc.asm:289:Error[128]   Missing argument(s).
Error[181]   System error while writing object file.

        clrf    ctrl_trf_state,             ; WAIT_SETUP

[2]
ff-pic18.asm:2358:Error[128]   Missing argument(s).
Error[181]   System error while writing object file.

        clrf    UCON,

ff-pic18.asm:4047:Message[305] Using default destination of 1 (file).

[3] 
error: No target memory available for section ".stack".
error: Linker script has no definition that matches the type of section ".stack".
error: Error while writing hex file.

Commenting out the STACK SIZE=0x0 RAM=usbep line removed the gplink
error. I flashed the hex file to the mcu and FlashForth was there via
USB.   

//SECTION 
//STACK   SIZE=0x0          RAM=usbep
SECTION NAME=FORTH_VARS   RAM=acs_ram
SECTION NAME=FLASH_BUF    RAM=flashbuf
SECTION NAME=USER_AREA    RAM=userarea
SECTION NAME=USB_EP       RAM=usbep
SECTION NAME=USB_VARS     RAM=usbvars
SECTION NAME=IRQ_STACK    RAM=irqstack
SECTION NAME=FF_RESET     ROM=coder
SECTION NAME=FF_INT_HI    ROM=codeih
SECTION NAME=FF_END_CODE  ROM=code1
SECTION NAME=FF_DP        ROM=code2

The questions I have are -

What is the reason for the STACK SIZE=0x0 RAM=usbep line in the
original linker file? And by commenting it out have I broken anything
I don't know about yet?

Best wishes and thanks,

Tristan