Shop OBEX P1 Docs P2 Docs Learn Events
Protect sourcecode in BS2p??? — Parallax Forums

Protect sourcecode in BS2p???

kintikinti Posts: 9
edited 2005-01-13 00:30 in BASIC Stamp
Someone knows if it is possible to protect the sourcecode in the BS2p???

thnx

Comments

  • NewzedNewzed Posts: 2,503
    edited 2004-09-25 15:02
    Once you've programmed a Stamp, that code is secure.· There is no way it can be copied from the Stamp.

    ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
    Sid Weaver
    Try the Stamp Tester

    http://hometown.aol.com/newzed/index.html
    ·
  • kintikinti Posts: 9
    edited 2004-09-25 17:19
    thnx for the info Sid
  • Chris SavageChris Savage Parallax Engineering Posts: 14,406
    edited 2004-09-25 23:34
    Kinti,

    ·· Since you mentioned "Source Code" I will elaborate on Sid's reply a bit...The Source Code resides on your computer only.· It's not downloaded into the BASIC Stamp, but rather compiled into tokens, which the BS2 interprets.· So your source is safe.



    ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
    Chris Savage

    Knight Designs
    324 West Main Street
    P.O. Box 97
    Montour Falls, NY 14865
    (607) 535-6777

    Business Page:·· http://www.knightdesigns.com
    Personal Page:··· http://www.lightlink.com/dream/chris
    Designs Page:··· http://www.lightlink.com/dream/designs
    ·
  • Martin KingMartin King Posts: 9
    edited 2005-01-11 01:04
    A late reply I know, but I've only just joined the forum, Only the tokenised version of the actual source·is stored on the stamp, however the tokens can be read from the EEPROM on the stamp with a little effort, and with a bit more effort could be reverse enginered back to something very close to your source (original variable names would be lost and replaced be arbitary ones).

    Martin.
  • GadgetmanGadgetman Posts: 2,436
    edited 2005-01-11 08:06
    If you want to make certain no one does just that, cover the EEPROM in a big glob of epoxy...

    If they want to try reading it, they'll then have to remove the epoxy first, and not only running the risk of destroying the EEPROM, but they will also leave evidence of the attempt.
  • LoopyBytelooseLoopyByteloose Posts: 12,537
    edited 2005-01-12 15:57
    For really secure code, you have to switch to the Ubicom SX. It has a scrabble feature that may be enabled. While you are developing and want to debug your code, you leave the feature off. This allows you to single step the microprocessor and observe bugs.

    But once you have completed your project, you may turn on a flag that scrabbles any and all attempt to read the on-chip eeprom.

    Is that what you desire?

    ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
    G. Herzog in Taiwan
  • Martin KingMartin King Posts: 9
    edited 2005-01-12 22:42
    Switching to an SX wouldn't help here, the tokenised code on a BS2P·is stored on an external I2C EEPROM plus changing the SMT processor is not for the faint hearted!

    Martin.
    ·
  • BeanBean Posts: 8,129
    edited 2005-01-13 00:30
    I don't think Kramer meant to replace the PIC on the stamp with an SX. He meant to use the SX development kit. The SX has built-in flash memory and and "code-protect" flag.

    Of course if someone is REALLY desperate to get the out a protected SX they still can, but it is much harder.

    Bean
Sign In or Register to comment.