Search found 219 matches
- Wed Feb 19, 2014 1:43 pm
- Forum: General
- Topic: Odd startup behavior at low voltage
- Replies: 14
- Views: 10230
Re: Odd startup behavior at low voltage
I'll give that a shot. Thinking about it, I don't use MCLR for anything on this version of the design. I did have it going to an option jumper as I had made allowance for an analogue input but decided I didn't need that. I could solder a pull-up resistor on the ICSP header. I must admit I don't know...
- Wed Feb 19, 2014 10:25 am
- Forum: General
- Topic: Odd startup behavior at low voltage
- Replies: 14
- Views: 10230
Re: Odd startup behavior at low voltage
I don't use BOR, that was my next step as I was wondering if I could create a low-battery detect using the BOR, but it might be worth trying just to get it reliable. I've got the following CONFIG settings: Config DEBUG = OFF, FCMEN = OFF, IESO = OFF, PWRTEN = ON, BBSIZ = OFF, BOREN = OFF, WDTEN = OF...
- Wed Feb 19, 2014 8:51 am
- Forum: General
- Topic: Odd startup behavior at low voltage
- Replies: 14
- Views: 10230
Re: Odd startup behavior at low voltage
I looked in to this a bit more last night and I'm still confused. I don't have a bench power supply to test it with, but I measured the battery voltage at 2.7V with the display illuminated. The software is also running as expected and is responding to an input by waking from 'sleep' (not the PIC sle...
- Tue Feb 18, 2014 1:53 pm
- Forum: General
- Topic: Odd startup behavior at low voltage
- Replies: 14
- Views: 10230
Re: Odd startup behavior at low voltage
I did wonder that but as I say, it runs as expected just the display is corrupted. The Hall sensor I use is a low power one - the SL353HT. I use 100R resistors on each LED segment, hard to tell what the current will be as you are towards the Vf of the LEDs so you need to study how Vf drops with curr...
- Tue Feb 18, 2014 9:11 am
- Forum: General
- Topic: Odd startup behavior at low voltage
- Replies: 14
- Views: 10230
Odd startup behavior at low voltage
I wonder if anyone on the forum has seen something similar to this and can suggest a possible cause? I've got a circuit that is powered by a CR2032 cell. It is a PIC18LF14K22 running a 3-digit 7-segment common anode display. It basically just looks for an input pulse from a hall effect sensor and ou...
- Tue Feb 18, 2014 8:53 am
- Forum: Compiler
- Topic: Multiple interrupt question
- Replies: 4
- Views: 2393
Re: Multiple interrupt question
Thanks, David and Jerry, unfortunately that confirms you can't have a library for interrupt-driven serial comms which is a shame. I guess what I was hoping is that you could define a code block that could be automatically inserted in to the interrupt handler defined in the main source file. In theor...
- Fri Feb 14, 2014 2:42 pm
- Forum: Compiler
- Topic: Multiple interrupt question
- Replies: 4
- Views: 2393
Multiple interrupt question
I'm working on some code where there are several possible sources of an interrupt - currently all the same priority level - and I'm struggling to understand what is possible within Swordfish. Can you define more than one interrupt handler for the same priority and if so, how are they 'merged'? The h...
- Wed Sep 11, 2013 2:37 pm
- Forum: Compiler
- Topic: Error in assembler file after upgrade to full Swordfish
- Replies: 3
- Views: 2126
- Wed Sep 11, 2013 2:00 pm
- Forum: Compiler
- Topic: Error in assembler file after upgrade to full Swordfish
- Replies: 3
- Views: 2126
Error in assembler file after upgrade to full Swordfish
I've been evaluating Swordfish for a number of months and have just upgraded to the full version. However, I'm hitting an odd problem. A piece of code that compiles fine under SE causes an error in the full version. The error (typed, as you seemingly can't cut and paste from the results bar) is: [AS...