Loading ...
Sorry, an error occurred while loading the content.
 

Re: [tracker2] Config program update

Expand Messages
  • Stan, KC7EHJ
    Watch out for the . period at the end of the link, proper URL is http://n1vg.net/opentracker/otwincfg_beta.exe Stan/KC7EHJ
    Message 1 of 2 , Jun 19, 2007
      Watch out for the "." period at the end of the link, proper URL is
      http://n1vg.net/opentracker/otwincfg_beta.exe

      Stan/KC7EHJ

      'Scott Miller' wrote:
      >
      >
      > I've posted a new version of the config program to
      > http://n1vg.net/opentracker/otwincfg_beta.exe.
      > <http://n1vg.net/opentracker/otwincfg_beta.exe.>
      >
      > The previous version would check to make sure the firmware file selected was
      > valid for the type of tracker connected, but it turns out that the check was
      > being ignored if you loaded the firmware with the erase/reload option.
      > That's fixed now.
      >
      > Also, the initial load option will let you load from the web now. This
      > should make it a lot easier to upgrade when a config program update is
      > needed, and it's just generally more convenient.
      >
      > The diagnostic screen no longer gets weird values for the temperature and
      > voltage if you click on the test tone buttons in the wrong sequence.
      >
      > And finally, the 'about' box includes a build date now, so you can see if
      > you've actually got the right version.
      >
      > As for the processors that got zapped by the OT1 firmware, I confirmed that
      > there's no way to fix them without re-flashing in a programmer. The config
      > program erased a big chunk right out of the middle of the bootloader.
      >
      > There's no way to set the flash protection to protect the firmware, but I've
      > added a safety check to the bootloader itself so that it won't erase any
      > block occupied by itself. This should provide about 99% of the same
      > protection - if you write your own firmware that does flash erase operations
      > you could still wipe it out, but other than that it should be safe.
      >
      > Right now there's no way to update the bootloader in the field. The
      > Tracker2 has that ability, but in that case it's simpler because the T2 has
      > plenty of RAM. (It actually works by using the bootloader to load a
      > bootloader-loader into flash, and then the bootloader-loader copies the new
      > bootloader to RAM, and calls the routines in ROM that copy it from RAM to
      > flash.) The OT1+ has almost exactly as much RAM as bootloader code, so it'd
      > probably mean even more juggling than the T2 updater.
      >
      > So in short, the new config program won't let you load the wrong firmware,
      > and the OT1+ chips now shipping don't care even if you do.
      >
      > Scott
      >
    Your message has been successfully submitted and would be delivered to recipients shortly.