Shop OBEX P1 Docs P2 Docs Learn Events
Help accidentally wrote to eeprom and now nothing will work — Parallax Forums

Help accidentally wrote to eeprom and now nothing will work

darthsnarkeydarthsnarkey Posts: 9
edited 2012-12-04 13:02 in Propeller 1
I accidently loaded a program into the eeprom and now nothing will work! Does anyone have the stock eeprom file for the Quickstart board?

Comments

  • Oldbitcollector (Jeff)Oldbitcollector (Jeff) Posts: 8,091
    edited 2012-12-03 13:59
    What was on your EEPROM before this happened?

    Jeff
  • darthsnarkeydarthsnarkey Posts: 9
    edited 2012-12-03 14:02
    It was the stock eeprom on the board I have't used it but a few hours :(
  • MagIO2MagIO2 Posts: 2,243
    edited 2012-12-03 14:07
    Isn't it the touch buttons demo?

    http://www.parallaxsemiconductor.com/products/quickstart

    But this is much more interesting:

    http://forums.parallax.com/showthread.php?135316-Quickstart-Smile-Games-Contest
  • darthsnarkeydarthsnarkey Posts: 9
    edited 2012-12-03 14:08
    Maybe more info would help. I am using a Mac and BST to upload to the Quickstart board and I uploaded to the eeprom instead of the ram like I wanted to. Now I can load spin files but none of them work anymore.
    Can I simply clear the eeprom of what I wrote or did I really Fubb this one?
  • darthsnarkeydarthsnarkey Posts: 9
    edited 2012-12-03 14:12
    I didn't do anything and now it works again!!! I just uploaded the same program I did 5 times and didn't work before but now it does! I guess never mind and thanks for your help :)
  • MagIO2MagIO2 Posts: 2,243
    edited 2012-12-03 14:13
    Write to EEPROM means that you overwrite whatever there was before (to be precise you overwrite 32kB). But you can overwrite until the EEPROM is broken, which might happen after 100,000 cycles.
  • D.PD.P Posts: 790
    edited 2012-12-03 15:38
    darthsnarkey wrote: »
    Maybe more info would help. I am using a Mac and BST to upload to the Quickstart board and I uploaded to the eeprom instead of the ram like I wanted to. Now I can load spin files but none of them work anymore.
    Can I simply clear the eeprom of what I wrote or did I really Fubb this one?

    I've lost bst comms to my QuickStart as well, spin tool is working fine though in parallels and minicom is working on osx as well?

    I didn't stop to fix this problem yet but my guess is the vcpi drivers gortched.

    I deleted the bst.plist and bst.ini files, no joy.
  • Mike GreenMike Green Posts: 23,101
    edited 2012-12-03 15:50
    You don't have to clear anything out of the EEPROM. Whatever was there will remain there until you save a different program to the EEPROM. Whatever is there will be erased (at least the 1st 32K if there's more).

    That said, what version of MacOS are you using? BST seems to have problems on the most recent incarnation (Mountain Lion or tabby ... whatever). I've switched over to using either Windows under Parallels Desktop or the GCC Beta release which will run the command line version of BST which does seem to work.
  • rjo__rjo__ Posts: 2,114
    edited 2012-12-03 19:00
    BST seems to get a slightly more unstable with each update of the Mac OS. Not sure about it... just my impression. In the beginning I used it without so much as a hiccup. Not so lately. I still use BST and find its foibles more than balance out with its overall use and design.

    I don't use BST as a serial terminal the way I would PST... and I never write serial stuff that uses pins 30 and 31 to the EEPROM. I have momentarily hung some boards doing that. I use Processing.org for my serial communications with the Prop... works fine in v.1.5 not so in v2.0... they won't talk about it. Questions all over their forums and nothing real coming out.
    I'm planning to migrate to SimpleIDE, but haven't completely evaluated it yet.
  • Duane DegnDuane Degn Posts: 10,588
    edited 2012-12-03 21:20
    rjo__ wrote: »
    I don't use BST as a serial terminal the way I would PST... and I never write serial stuff that uses pins 30 and 31 to the EEPROM.
    Really? I use pins 30 and 31 all the time for debug lines. This could cause a small glitch with the QuickStart when using earlier versions of the Prop Tool but the latest version of the Prop Tool fixed the problem. Using a 4.7K pull-up (to 3.3V) on P30 also solves the problem.
  • rjo__rjo__ Posts: 2,114
    edited 2012-12-03 21:49
    No... not with the Quickstart... this happened before it became available and I actually haven't tried it since. As I recall, I could also put a delay into my programs so that BST could grab the Prop first. Maybe it has been fixed. I had to swap out a couple of eeproms before I decided to insert a delay... and they working just fine, except that I couldn't erase them. maybe a bad diagnosis... sorry if I'm wrong.
  • darthsnarkeydarthsnarkey Posts: 9
    edited 2012-12-04 11:28
    OK so I'm obviously a noob since I did two things wrong. 1) I uploaded the object not the actual usage of it and 2) I loaded it into eeprom not knowing enough. I found out that when I loaded the correct file into EEPROM it worked fine and I also found you can put an "empty" program into EEPROM to clear it out :smile:
  • Duane DegnDuane Degn Posts: 10,588
    edited 2012-12-04 12:03
    darthsnarkey wrote: »
    I also found you can put an "empty" program into EEPROM to clear it out :smile:

    FYI, you don't ever have to "clear" the EEPROM. You just load the program you want to run and it over writes whatever was there.
  • darthsnarkeydarthsnarkey Posts: 9
    edited 2012-12-04 13:02
    Noted and thank you :)
Sign In or Register to comment.