|
Step 3: I skipped over all code relating with the LCD and it still is not recognized.
So now I've narrowed it down to the TMR1 interrupt not working perfectly. How can I tweak it to interrupt at a faster rate?
I assume I have to accelerate the prescaler, I just don't know which way is which. And then possibly adding a counter to fine-tune the interval between USBservice.
Robert
My Creality Ender 3 S1 Plus is a giant paperweight that can't even be used as a boat anchor, cause I'd be fined for polluting our waterways with electronic devices.
Not as dumb as yesterday, but stupider than tomorrow!
|
I had screwed up the disabling/enabling of the interrupt during USB subroutines.
Step 4: Disabled TMR1 _before_ the assembler loop, manually issue USBSERVICE within the loop and then enabled TMR1 after the loop and the device is recognized.
Robert
My Creality Ender 3 S1 Plus is a giant paperweight that can't even be used as a boat anchor, cause I'd be fined for polluting our waterways with electronic devices.
Not as dumb as yesterday, but stupider than tomorrow!
|
Step 5: Reactivated LCD logic along with USART and RX interrupt and device is still recognized.
Go figure, the LCD works properly even if I'm using pins C0 and C1 to output the data and commands to the LCD.
Robert
EDIT: I'm thinking the LCD works because I'm not using an external oscillator for the timer.
================================
When Timer1 is enabled, the RC1/T1OSI/UOE and
RC0/T1OSO/T13CKI pins become inputs. This means
the values of TRISC<1:0> are ignored and the pins are
read as ‘0’.
================================
Last edited by Demon; - 25th July 2006 at 14:46.
My Creality Ender 3 S1 Plus is a giant paperweight that can't even be used as a boat anchor, cause I'd be fined for polluting our waterways with electronic devices.
Not as dumb as yesterday, but stupider than tomorrow!
|
Can DT_INTS-14.bas be used with 12Fxxx PICs?
|
YES!
It's a little tight for RAM and program space. But it should work.
DT
DT
|
One note of interest, I kept hanging at the end of one of the interrupt modules, like it lost an address on the stack or something. I ran ICD and I saw the execution just hang on the ENDIF at the very bottom.
I have an RX interrupt that would write out to an I2C device 2 bytes received via USART. I removed the I2C command from within the interrupt and instead set a flag. Then I checked the flag from within the main logic and issued the I2C write and everything worked perfectly.
Darrel, here are some screenshots in case you see something obvious. Sorry, I didn't keep a copy of the code.
Robert
My Creality Ender 3 S1 Plus is a giant paperweight that can't even be used as a boat anchor, cause I'd be fined for polluting our waterways with electronic devices.
Not as dumb as yesterday, but stupider than tomorrow!
|
2nd pic:
The program USB 18F2550 is for the master processor, that is not the one I am debugging. I am running the next program, MCP23016 16F628A.
Robert
My Creality Ender 3 S1 Plus is a giant paperweight that can't even be used as a boat anchor, cause I'd be fined for polluting our waterways with electronic devices.
Not as dumb as yesterday, but stupider than tomorrow!
|
With a 12F629 my app gets lots of "beyond ram_end" messages; with a 12F683, only two, so I might be able to pare it down to fit.Originally Posted by Darrel Taylor
|
If you don't have any complex math formula's in the program, you can reduce the number of T?_Save variables.
From ReEnterPBP.bas...
T1_Save VAR WORD
T2_Save VAR WORD
T3_Save VAR WORD
T4_Save VAR WORD
Start with T4. Comment it out and recompile. If no error, try T3, etc.
Then try ...
RS1_Save VAR BYTE
RS2_Save VAR BYTE
Might save a few bytes of RAM.
Just remember to un-comment them if you write a program for another chip.
DT
Members who have read this thread : 4You do not have permission to view the list of names.
Posting Permissions
Bookmarks