[can-do-users] CAN-Do info

[Stephen Moraco]

Enric,

On Thu, Jun 25, 2009 at 9:57 AM, Enric Fernandez Murcia <efermu at gmail.com>wrote:

> I think this is the menu to install firmware to CAN-Do widget. Now I am
> trying to understand it, but if you have time could give me an idea about
> what I have to do?
>

      Congratulations on the great progress!
      Regarding how to run flasher...

      Make sure you've downloaded the latest widget firmware from our CAN-Do
site.

      Study the command line examples I've left in the
flasher-0.4.8/examples/  directory.
      In the examples you'll find *USB and *232 scripts.  For the CAN232
you'll be able to
      use the *232 scripts.  They will make your flashing effort very easy.
 See the
      README.txt in this directory for more info.

      Note that the *232 scripts expect /dev/cando to be a symbolic link to
the correct
      serial TTY device. [as described in flasher(1)]

      We number each of our devices sequentially.  This number is stored in
the
      firmware image by flasher and is queried by CDNC and is available in
the
      bus census message.  We also write this number on the DE9 connector
      shell on the Widget with a permanent marker.  This way we can keep
      them straight and keep notes about each one.

      Our devices use ID numbers from 1 to 199.  Would you mind working from
the
      other end of the range?  Give yours the 9xx serial numbers as we will
stay out
      of each others way.  :)

      Ok, on to flashing the firmware into a widget.  In real general terms:

        I cable up the hardware

        turn on the power

        reset the Widget (so it's in bootloader mode)

        set the widget id number (for logs) in the shell
          - export WIDGET=9xx    <-  replace the xx with your real serial
number!!!!

        run the scripts :
          - doit dvcCheck232      <-  (repeat until device is ready)
          - doit loadTstCurr232    <- this does the actual flashing...

        If this is the first time ever flashing a new Widget then you must
also run:
          - doit setBootUserX2232    <- once, when first flashing a new
Widget


       NOTE: "doit" is a simple script wrapper which logs everything written
to the console.
       It automatically names the log files sequentially and by widget ID
making running
       these scripts and capturing their output very easy.

       The loadTstCurr232 expects the Widget firmware to be in a nearby
directory.

       If, for example, you have flasher-0.4.8 unpacked in your home
directory then you
       would have:
           ~/flasher-0.4.8
           ~/flasher-0.4.8/examples
        make the directory:
            ~/firmware
        unpack the widget firmware into this new directory
        now you should see the .hex file as:
            ~/firmware/flight.hex
        if it is there then the scripts will be able to find it.

       You do not have to have flasher unpacked in your home directory, I'm
       just using this as an example.   Just make sure that flasher-0.4.8
and firmware
       directories are side-by-side in the file-system and the scripts will
work.

       This make sense?

Regards,
Stephen, KZ0Q
--
Stephen M Moraco
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gag.com/pipermail/can-do-users/attachments/20090625/a1991d20/attachment.htm>