Swordfish

Well Garry, at least you got over the first hurdle and got it to compile. What I can't figure out is how does the USART2 module know which pins to use....The program would not compile using the native USART2 module because it wanted to use PORTG I never came up with a good way of getting around this...

I'm not finding much in the way of EASYHID and 18F4620

Maybe that's because the 4620 doesn't have a USB peripheral.

The USB chips all have a "5x" in the last digits of the part number, like 18F2450, 18F4550, 18F27J53, etc

Graham, One thing you CAN do (and I don't know if this helps with what you're trying to do) is to include the subdirectory name in the 'include' statement. If you have: UserLibrary\test.bas UserLibrary\Sub Folder\test.bas then in your .bas file you can use the syntax: include "Sub Folder/test.bas" a...

Anybody know if any of the tools have the ability to track this, like one of the hardware debuggers?

I'm really only interested in the max depth. I don't need anything much more than that.

I'd like to see how deep I'm nesting subroutine calls.

Does the compiler keep track of this? Is there any way of looking at/tracking stack usage?

Thanks, David. That seems to have fixed things up.

The nice thing about that tool is that you also get an updated MPASMwin.exe, along with the '8bit_device.*' files, so that should be all someone needs to get up to date device-wise.

That's strange... mine are straight from 8.73a with SystemConvert and I get different results. Here's a few comparisons (mine followed by the new tool's output): 13K50: #const _ram_banks = $01 // 1 RAM bank(s) used #variable _maxram = $0100 // 256 bytes of user RAM #const _eeprom = $0100 // 256 byte...

I hate to go off-topic, but I just loaded the libs from the new device library installer and some of them don't match up very well with the current devices. While most of the differences are simply ADC/CCP stuff (which I never could figure out how in the world you got right to begin with), a number ...

Whatever you come up with, PLEASE don't have the IDE touch anything in the libraries without warning me... and NEVER touch my user libraries. While I understand the desire to try and keep the libs updated, if they change then when/if I rebuild something I'd have to go back and retest the entire proj...

Obviously there's more to the program that you're not showing (or it wouldn't compile), but usart.read() will read bytes until it receives a NULL (0) character unless you have changed the ReadTerminator

I would LOVE to find some nice, small, easy to use bootloader code I think it depends on your definition of small, and how you want to interface to it. For a serial port loader, DS30 is pretty reasonable. Most of the USB ones I've seen are much bigger. The MikroE StartUSB is about 6700 bytes, and t...

I was never able to find all my old test files, but I did manage to find the original board I used, which was an eIP-10 ( http://www.ljcv.net/eip10/index.html ) This board has an 18F2620 and an ENC28J60. I just compiled David's ethernet library for it (the simple ping example) and pretty much the on...

I saw that, but totally misread that part of the datasheet!

Thanks for the heads up, Richard.

I've never used that chip or the adc at 64MHz, but it sounds like the adc timing may not be setup properly. Are you calling 'SetConvTime(FOSC_64)' in your main code? If so, perhaps try a slower clock and see what happens. There is some errata for the K80 adc that suggests it's only good for 10 bits....

From what I can tell, it would appear that the compiler may not be generating the correct code for those upper registers on the 66K80 family of parts. It doesn't seem to be getting the upper ACCESS bank correct. Also, the device .bas file doesn't appear to be right, at least using the file SystemCon...