Load EEPROM & run problem

Rsadeika

Project Directory: E:/PropGCC/SimpleBot/SimpleBot/

propeller-elf-gcc.exe -v GCC 4.6.1 (propellergcc_v1_0_0_2162)
propeller-elf-gcc.exe -I . -L . -I C:/Users/Ray/Documents/SimpleIDE/Learn/Simple Libraries/ActivityBot 2013-10-31/libabdrive -L C:/Users/Ray/Documents/SimpleIDE/Learn/Simple Libraries/ActivityBot 2013-10-31/libabdrive/cmm/ -I C:/Users/Ray/Documents/SimpleIDE/Learn/Simple Libraries/libsonyremote -L C:/Users/Ray/Documents/SimpleIDE/Learn/Simple Libraries/libsonyremote/cmm/ -I C:/Users/Ray/Documents/SimpleIDE/Learn/Simple Libraries/Text Devices/libsimpletext -L C:/Users/Ray/Documents/SimpleIDE/Learn/Simple Libraries/Text Devices/libsimpletext/cmm/ -I C:/Users/Ray/Documents/SimpleIDE/Learn/Simple Libraries/Convert/libadcDCpropab -L C:/Users/Ray/Documents/SimpleIDE/Learn/Simple Libraries/Convert/libadcDCpropab/cmm/ -I C:/Users/Ray/Documents/SimpleIDE/Learn/Simple Libraries/Sensor/libping -L C:/Users/Ray/Documents/SimpleIDE/Learn/Simple Libraries/Sensor/libping/cmm/ -I C:/Users/Ray/Documents/SimpleIDE/Learn/Simple Libraries/Utility/libsimpletools -L C:/Users/Ray/Documents/SimpleIDE/Learn/Simple Libraries/Utility/libsimpletools/cmm/ -I C:/Users/Ray/Documents/SimpleIDE/Learn/Simple Libraries/Protocol/libsimplei2c -L C:/Users/Ray/Documents/SimpleIDE/Learn/Simple Libraries/Protocol/libsimplei2c/cmm/ -I C:/Users/Ray/Documents/SimpleIDE/Learn/Simple Libraries/Text Devices/libfdserial -L C:/Users/Ray/Documents/SimpleIDE/Learn/Simple Libraries/Text Devices/libfdserial/cmm/ -o cmm/SimpleBot.elf -Os -mcmm -m32bit-doubles -fno-exceptions -std=c99 SimpleBot.c -lm -labdrive -lsonyremote -lsimpletext -ladcDCpropab -lping -lsimpletools -lsimplei2c -lfdserial -lm -labdrive -lsonyremote -lsimpletext -ladcDCpropab -lping -lsimpletools -lsimplei2c -lm -labdrive -lsonyremote -lsimpletext -ladcDCpropab -lping -lsimpletools -lm -labdrive -lsonyremote -lsimpletext -ladcDCpropab -lping -lm -labdrive -lsonyremote -lsimpletext -ladcDCpropab -lm -labdrive -lsonyremote -lsimpletext -lm -labdrive -lsonyremote -lm -labdrive -lm
SimpleBot.c: In function 'get_Time':
SimpleBot.c:279:3: warning: return makes integer from pointer without a cast [enabled by default]
SimpleBot.c: In function 'get_Date':
SimpleBot.c:291:3: warning: return makes integer from pointer without a cast [enabled by default]
SimpleBot.c: In function 'get_Volts':
SimpleBot.c:304:3: warning: return makes integer from pointer without a cast [enabled by default]
propeller-load -s cmm/SimpleBot.elf
Patching __cfg_sdspi_config1 with 00000000
Patching __cfg_sdspi_config2 with 00000000
propeller-elf-objdump -h cmm/SimpleBot.elf
Done. Build Succeeded!

propeller-load.exe -Dreset=dtr -I C:/Program Files (x86)/SimpleIDE/bin/../propeller-gcc/propeller-load/ -b ACTIVITYBOARD cmm/SimpleBot.elf -e -r -p COM11
Propeller Version 1 on COM11

Patching __cfg_sdspi_config1 with 18161701
Loading cmm/SimpleBot.elf to EEPROM via hub memory

24660 bytes sent

Verifying RAM ...
OK

Programming EEPROM ...
OK

Verifying EEPROM ...
OK

I programed it with 'Load EEPROM & Run', it seems like it completed with out hitch, but when I go to battery power and start back up again, power setting is on #2, the program is not starting. Of course this is the ActivityBot with the li-ion battery power pack, and the batteries are fully charged(7.7V). Code Size 24,660 bytes (28,688 total).

I am also wondering if SimpleIDE could have just a 'Load EEPROM' setting, sometimes it is necessary to just load the EEPROM without having it start up a program.

Ray

jazzed

Ray,

What happens if you use a simple LED blinker program?

/**
 * This is the main blinky program file.
 */
#include "simpletools.h"

int main(void)
{
  int pin = 27; // Activity Bot Amber LED near breadboard.

  high(pin);
  while(1) {
    pause(250);
    toggle(pin);
  }
  return 0;
}

Rsadeika

Yes, I just tried a simple blinker on the ActivityBot, and that does not work. I also tried programming my PropBOE, that seems to work, so it is NOT a SimpleIDE problem. Does anybody have a working program to test the first 32k of the EEPROM, I am wondering if my EEPROM, on the ActivityBot, has gone bad? So I guess it is an ActivityBot Board problem, but when I have the programming cable plugged in, it seems to be working the way it supposed too, it just isn't working off of the EEPROM.

Ray

jazzed

Ray,

If it doesn't work with a simple blinker, there is no hope of it working with anything else.

Did you try the Activity board power test? Some Activity boards had a little power trouble.

I don't have time to work on an EEPROM test today. The turkey needs me.

Rsadeika

Yes, I hear you, the turkey comes first, have a nice feast. For me it is working out weird, I am doing the turkey thing tomorrow.

I found a "Supply Noise and Range Test" program, the p26/p27 LEDs stayed illuminated, so I guess the power supply is OK. I tried blanking out the EEPROM, meaning I just loaded a blank program to EEPROM that seemed to work, cleaning out the blinker. I then re-loaded the blinker, and started it up on battery power, and nothing. So, this is the second Activity Board that has gone bad, starting to wonder about the quality of these boards. I guess I can still use it as long as I do not use the EEPROM. Anybody have any other ideas as to what or how I could check to see what the real problem is?

Ray

Phil Pilgrim (PhiPi)

I don't think it's the EEPROM, since the the contents are read back and verified during the load -- at least I think that's the case with SimpleIDE's loader. Just as a test of this hypothesis, try loading a Spin blinker program with Propeller Tool and see what happens. If it complains, then you have an EEPROM issue.

Also, does the EEPROM program run when under USB power? IOW, after loading and pressing the reset button, does the program work okay?

-Phil

Rsadeika

Also, does the EEPROM program run when under USB power? IOW, after loading and pressing the reset button, does the program work okay?

I just tried that, and yes the blinker program works. Now for the Spin program, what the heck is SPIN? LOL Maybe I should use this opportunity to check out FORTH, maybe they have a quick and dirty program for doing this.

Ray

Phil Pilgrim (PhiPi)

It appears to be a power problem, then. What happens if you use a DC wall transformer instead of the battery?

-Phil

Rsadeika

What happens if you use a DC wall transformer instead of the battery?

I do not have anything like that, so I am unable to try that. I did try doing a Spin blinker program, and I get nothing. When the prop tool was doing the verification of the EEPROM load, there were NO error flags going up, so I assume the prop tool thinks the EEPROM is OK. Has anybody made a good diagnostics program for checking things out on any of boards that are available? Open source I hope.

Ray

Phil Pilgrim (PhiPi)

Rsadeika wrote:

... there were error flags going up ...

Did you mean to say, "... there were no error flags going up ..." ?

Anyway, I suspect your power source might be the problem. Have you got any other 6V-9V DC source other than the Li-ion batteries that you could try?

-Phil

Rsadeika

This is the sequence of events:
With the li-ion battery source plugged in, and NO USB plugged -
move power switch to 1, green LED turns on
move power switch to 2, both LEDs are on, no blinker program working.

With 9V wall-wart plugged in, and NO USB plugged -
move power switch to 1, NO green LED
move power switch to 2, both LEDs are on, the blinker program is working.
move power switch back to 1, green LED stays ON
move power switch back to 0, LEDs are off.

Something is definitely gone bad. Well I guess I have to put my ActivityBot in a box, and move on to other things.

Ray

Phil Pilgrim (PhiPi)

That's totally weird. One symptom points to a faulty power switch; another, to a bad/weak battery source. In any event, we can definitely rule out any EEPROM issues.

Just out of curiosity, what happens in the 9V wall wart scenario if you jumper a 100-ohm resistor between +5V and Gnd? Then between +3.3V and Gnd?

-Phil

Rsadeika

The smallest I have is 220-ohm resistor, very limited supply of that kind of stuff.

Ray

Phil Pilgrim (PhiPi)

Rsadeika wrote:

The smallest I have is 220-ohm resistor, ...

Two of those in parallel would work.

-Phil

Rsadeika

Nothing changed. Thanks Phil, I have had enough with the AcitivityBot, in the box it goes.

Ray

jazzed

Ray,

If it works on a wall wart, but not the LI-ON, maybe there is an issue with the battery's current capacity.

I use Duracell Alkaline AA.

Rsadeika

Thanks jazzed, it is in the box, I am done with the ActivityBot and the Acitivity Board. I still have the PropBOE Board to work with, I think I have had it with the xxxBot stuff. Now I will sit back and try to think of something else to do.

Ray

Rsadeika

To be fair about my latest observation, I did a final test and assessment, and the problem is with the Li-ion BoeBot Power Pack-Charger. I used some fresh charged batteries in the power pack, and the blue flashing LEDs concur, but the power pack is not delivering the correct power supply. This is the second power pack that has failed, or at least not functioning correctly. So, it seems like the Activity Board is not showing any obvious signs of malfunction yet, but it is doing do blinker thing when loaded to the EEPROM.

But, I am still done with the xxxBOT stuff, it is now packed in a box. I will also be very apprehensive as to what and how I use the Activity Board, maybe later today I will try to test the components on the board, and maybe my new project will be a diagnostic program for testing the board. Or maybe I should just lay down and read a good book...

Ray