Search:

I don't need the editor to work or anything... just be able to compile and load it so I can debug, even at the asm level.
I thought that part still worked, but maybe I'll try treating it as an asm...

Not really that I can think of.

I thought I'd try and load it into MPLABX so I could debug it, but it's been so long since I've used it w/PBP I can't seem to get the two so I can build and debug...

On the Q43 (and most recent PIC18's with the VIC), the SFR registers have been moved down in memory starting at BANK 0,
so general purpose RAM no longer starts there. The access bank used to be part...

From what I can tell the basic interrupt structure looks to be ok.
Unfortunately, the way the various files are written, all of the ReEnterPBP routines don't appear in the .lst files, so it makes...

In your main file you need to uncomment the 'define use_lowpriority' and rearrange the DT-INTS setup section.

Try:


' ---------- Set up DT_INTS-18 Routine for Instant Interrupt handling ...

Oops, that one's on me! I forgot that they re-arranged things with the new VIC module and there's only GIE/GIEH and GIEL.
You can just kill that line.


I'm gonna have to take a closer look at...

... and one I forgot.

In your Timer0_Count routine, stop messing around with the PIE bits. You can't get another TMR0 interrupt while you're already inside the ISR.


Timer0_Count:
'...

I don't see anything wrong with ReEnterPBP-18LP.bas, but there are a few other things I noticed.

First off, as I said, you can't have just a low-priority interrupt.
If you don't define a...

Could be, but I don't have any PBP version even remotely up to date to test it with.

Could you post the .lst and .hex files that go along with that?

One thing I never see... the INTCON0.GIE bit...

Keep us posted on if it works.


That should have read '4K boundary'

If you're feeling adventurous you could try the attached.

It's a modified version of the DT_INTS-18_K42b.bas code from post #9 with the context save stuff removed (now done in hdw) and the MOVFF...

Look at the SERIN2/SEROUT2 commands in the manual.
They allow you to specify optional flow control pins which you would connect to the RTS/CTS pins of the module you're using if it has hdw flow...

Yes, the MSSP does both.

Well, that's going to make I2C operations about ten times slower than what it could be running at.

A while back you mentioned using software SPI and complained about it being slow too.
You'd...

If you're running at 8MHz then no wonder everything is slow.

32MHz (or 64MHz for something like an 18F26K22) would definitely be faster, way faster.
The I2C won't necessarily be a lot faster on...

If you're trying to write something totally generic that can be used with all the 8-bit PIC's then the most generic solution is to use the bit-banged I2C routines.

If you want a faster method then...

In that case, if you're looking for speed then an I2C EEPROM isn't the best of choices.

I have no idea how slow the bit-banged I2CREAD is (probably pretty slow).
A 24C256 isn't all that slow, but...

Would 1K of EEPROM be enough for what you're doing?

If so, switch to a pic18, like an 18F26K22. It'll be MUCH faster than trying to read from an I2C EEPROM.

They should show up. I've had this happen for a number of chips lately... 0 stock but I can still get free samples.

I have a feeling they have more stock than they're letting on, probably for...

I don't know if it's different for AUS, but for the US MicrochipDirect has a "sample" request that allows you to get up to two devices x qty 3 of each every 30 days.

It's showing the PIC18F47Q43...

It sounds like you are describing the R-M-W (read-modify-write) effect that you get when setting one bit of a PORT output.
When you do a bit operation on a PORT, the entire PORT is read, the bit is...

I meant to open a windows command prompt and run ICD3CMD.exe from the command line so you can play around with the various options and see what the results are.
As I said, you don't get much output...

For the MCS IDE, if you tack on a "-B" that puts it into batch mode and it should leave the command window open.
Here's an example command line:
-P$target-device$ -F$hex-filename$ -W -B

ICD3CMD...

Did you look in the file "Readme for RealICECMD_ICD3CMD.htm", sections 8 (command line options) and 11 (examples)?

They're all pretty similar...

Have you setup the commandline options for icd3cmd? They can be found in the MPLABX folder docs\Readme for RealICECMD_ICD3CMD.htm

See http://www.picbasic.co.uk/forum/showthread.php?t=23910 for...