Swordfish

I just posted my updated version of the SF USB library over on Digital-DIY ( http://digital-diy.com/Download-document/87-SF-USBv14-Library.html ) Features include: - support for all current 30 18F USB devices, including: 18F2550, 18F4550, 18F2553, 18F4553, 18F2455, 18F4455, 18F2458, 18F4458, 18F2450...

If it's const string handling, then it's very likely the TBLPTR thing. I just tried the second program you listed, and it works fine using MY USB bootloader and system.bas (but my bootloader clears the TBLPTR registers). I'm using an 18F2553, but otherwise it's the same. Using the standard SF USB li...

Just had a closer look.

If you're building for use with a bootloader that uses low memory, you want to use instead of That'll move everything up to $1000. Using 'org_program' leaves a 'goto' at location 0

The issue is most likely with the TBLPTR register settings, which is used by SF to read code/const strings. In the 18F, the table ptr is a 24-bit value comprised of three 8-bit registers: TBLPTRU, TBLPTRH, and TBLPTRL. This gives you full access to the 16M address space of the 18F, which you need to...

That dll makes a lot of assumptions. The problem with transferring anything but single 8-bit unsigned bytes between two systems is that the data representation may not be the same on both ends, and it's machine and language dependant. What's an 'integer' on your host system? 16 bits? 32 bits? Is it ...

Is the TBLPTRU register ever set or initialized? I realize that SF doesn't have support for a 24-bit data type (which is really what the TBLPTRU/TBLPTRH/TBLPTRL register set is), and does table accesses using a 16-bit address. There's the following alias in the device .bas files... public dim TABLEP...

Nix what I said in that last post. I've had a support ticket open for almost a month now about this, but it seems I was given bogus information about the 18F66K80 family. They just released an errata to the datasheet, and supposedly it's the DATASHEET that was wrong, so the include files in MPLAB 8....

This might be a bit of a kludge, but it seems you can use an asm block to get absolute data into the hex file at a particular location macro InitUserID() asm cur_loc set $ ; record current program address org 0x200000 ; point to the UserID area db 0x5a,"1",0x20,0x30,40h,50h,60,"7" ; eight bytes of u...

Is there anyway to generate initialization data for the User ID locations (the eight bytes @ 200000h-200007h) like you can for the eeprom and config areas?

I know how to read and write them at runtime, but I'm looking for a way to set the data in the hex file.

I just noticed that system.bas has a conditional compile... public inline sub ClrWDT() #if (WDT) asm ClrWDT end asm #endif end sub This will result in the sub being completely optimized away if you have "#option WDT = false". While that can save a few bytes here and there, it might be a lot less dan...

I don't know about "always", but for the last few versions SF checks the following locations for 'include' files (and in this order): - the current project folder - the <swordfish install>/UserLibrary folder - and finally <swordfish install>/Library folder So, you can override the system libraries o...

I've been swapping devices back and forth a lot lately, and I kept running afoul of the different names used for the WDT configuration setting. Thanks to Microchip, some devices use 'config WDT' while others use 'config WDTEN', and it's a real pain to keep track of. I finally broke down and wrote re...

One oddity I found in the Code Explorer window as I add the macros... I just tossed some of that code together, and I see funny things in the Code Explorer as well for the ActivateTimers() and De_activateTimers() routines. I've never noticed that before because I have 'Explore Includes' unchecked i...

I don't think there's much documented on the new macro facility besides a few forum posts... mostly just some questions to David. http://www.sfcompiler.co.uk/forum/viewtopic.php?t=1308 http://www.sfcompiler.co.uk/forum/viewtopic.php?t=1316 There's nothing about it in the help file yet AFAIK. There's...

I've followed that on and off (mostly off since it's for PDS), but I really didn't want to get into the whole PC app end of things... it just adds too much support effort. Mchip's HIDBootLoader.exe isn't the greatest of apps, but it seems workable, supports all the chips, comes with source code, and...