BasicMicro - Forums

Hello Hiskey. Yeaaah! Houston, we have verify!
Dude, we have just GOT to have that code to give you anything like a real answer. This is the only way the programmer will take the time to study your code. The first thing that comes to mind to me is the LCD needs a 250mS PAUSE at the start of the program, first thing, before you do anything else. Do you have an LCD in this project?
Take care.

_________________
kenjj
http://blog.basicmicro.com/
http://kjennejohn.wordpress.com/

Nope. I have two custom made pressure sensors (actually just using some black, dense chip packing foam that works surprisingly well for this sort of thing). You just poke a couple wires into it and add a nice sized resistor before running electricity through it and they make great variable resistors where the resistance is changed by how much the foam is squeezed (hence nice, ridiculously cheap pressure sensors). With my current ones the reading ranges from about 300-500 when read with the ADC.

Then I have a normally open switch and a transistor that is switched on right away. However, all those things were in the circuit and being used in code before when it was working. It was some very minor tweak in my code that seems to have stopped it working. So that's where the mystery comes in .

I'm not too concerned about it, but if you guys want to double check it's not an issue with the nano/usbtoserial programmer, I can send you a picture of my circuit and my code (can't post it publicly as it's a device being made for a business). But if you don't think it would be something like that, I'm really not at all concerned right now. A 232 millisecond pause when the device is switched on, is not an issue with this device. As long as I can program it, I'm happy.

Cool! I myself made the mistake of troubleshooting a logic circuit on the stuff once and it made for some real interesting readings.
Hiskey, if you're happy with the present situation, we're done. Eventually we'll be in deep testing (another word comes to mind) and DIG will be flogged well and truly. It would be nice to catch it now, but you go where the flames are seen and ignore the smoke on the horizon.

_________________
kenjj
http://blog.basicmicro.com/
http://kjennejohn.wordpress.com/

Just so you know, I tracked down the line that is the problem. The line that is causing the "verify xxxx" error, even with the capacitor, is where i'm writing to the eeprom 1 byte. If i put the Pause statement before that line, it programs fine, directly after that line it gives me the "verify xxxx" error on programming, even when I go all the way up to a 1000 uF capacitor hooked up. The power supply i'm using is 5 volts, 350 mA (just so you know). All i have hooked up is my two foam pressure sensors, 1 tiny general purpose NPN transistor, one LED, and one pushbutton. I know writing to the eeprom takes some time (i'm guessing around 231 milliseconds??? and whatever is happening in the verification step apparently can't happen correctly when writing to the eeprom. Does that sound about right? (note: I can read from the eeprom fine without any verification error, just the writing part that throws it on the verification step. Also, writing to the eeprom works fine otherwise, when it's not trying to verify at the same time).