Skip to content
Snippets Groups Projects
Select Git revision
  • a0a504569b5ae4d6e485414c43be0fd4bb216bab
  • master default protected
  • v0.10.0
  • v0.10.0-rc2
  • v0.10.0-rc1
  • v0.9.0
  • v0.9.0-rc1
  • v0.8.0
  • v0.8.0-rc2
  • v0.8.0-rc1
  • v0.7.0
  • v0.7.0-rc2
  • v0.7.0-rc1
  • v0.6.1
  • v0.6.0
  • v0.6.0-rc2
  • v0.6.0-rc1
  • v0.5.0
  • v0.5.0-rc2
  • v0.5.0-rc1
  • v0.4.0
  • v0.4.0-rc2
22 results

guess-rev.sh

Blame
    • dbrownell's avatar
      b1f7b359
      Change version labels to work better with GIT · b1f7b359
      dbrownell authored
       - The guess-rev.sh script is now a tweaked version of "setlocalversion" as
         seen in Linux, U-Boot, and various other projects.  When it finds source
         control support (git, hg, svn) it uses IDs from there.  Else (specific
         to this project) it reports itself as "-snapshot", e.g. from gitweb.
      
         I verified this new "guess-rev.sh" script runs under Cygwin.
      
       - Also update the generic version strings to be like "0.3.0-dev" (during
         development) instead of the very long "0.3.0-in-development".  These also
         show up in the PDF docs.  For better tracking, we might eventually change
         these strings to include the version IDs too.
      
       - Change the startup banner version strings so they include the guess-rev
         output.  Development and release versions with GIT will be like
      
          Open On-Chip Debugger 0.3.0-dev-00282-g7191a4f-dirty (2009-10-05-20:57) 
          Open On-Chip Debugger 0.3.0 (2009-10-05-20:57) 
      
         instead of the previous SVN-specific (even when using git-svn!)
      
          Open On-Chip Debugger 0.3.0-in-development (2009-10-05-01:39) svn:exported
          Open On-Chip Debugger 0.3.0 (2009-10-05-01:39) Release
      
      
      
      git-svn-id: svn://svn.berlios.de/openocd/trunk@2809 b42882b7-edfa-0310-969c-e2dbd0fdcd60
      b1f7b359
      History
      Change version labels to work better with GIT
      dbrownell authored
       - The guess-rev.sh script is now a tweaked version of "setlocalversion" as
         seen in Linux, U-Boot, and various other projects.  When it finds source
         control support (git, hg, svn) it uses IDs from there.  Else (specific
         to this project) it reports itself as "-snapshot", e.g. from gitweb.
      
         I verified this new "guess-rev.sh" script runs under Cygwin.
      
       - Also update the generic version strings to be like "0.3.0-dev" (during
         development) instead of the very long "0.3.0-in-development".  These also
         show up in the PDF docs.  For better tracking, we might eventually change
         these strings to include the version IDs too.
      
       - Change the startup banner version strings so they include the guess-rev
         output.  Development and release versions with GIT will be like
      
          Open On-Chip Debugger 0.3.0-dev-00282-g7191a4f-dirty (2009-10-05-20:57) 
          Open On-Chip Debugger 0.3.0 (2009-10-05-20:57) 
      
         instead of the previous SVN-specific (even when using git-svn!)
      
          Open On-Chip Debugger 0.3.0-in-development (2009-10-05-01:39) svn:exported
          Open On-Chip Debugger 0.3.0 (2009-10-05-01:39) Release
      
      
      
      git-svn-id: svn://svn.berlios.de/openocd/trunk@2809 b42882b7-edfa-0310-969c-e2dbd0fdcd60
    README.md 2.79 KiB

    Machine Kit Router

    This is a message passing / compute center for machines, robotics.

    fab

    Status

    It works! If you have one, it should forward packets no problem. Let me know if you find weird errors...

    Next Steps

    Did a redesign for this using the ATSAMD51 and USB-Serial on-chip conversion so that networks can run at 1-3MBaud, not 0.1MBaud. That board is out to the house.

    New Board

    • is out to fab

    routed

    schematic

    Board Design

    I use the ATSAMS70 micro, which is very fast but still simple enough. 300Mhz and the I/O we need.

    That said, setting up the power schematic is messier than I would like. There's an internal regulator on the chip that is externally connected to a few 'vddcore' input pins (5), each of which needs a bypass cap. In addition, there are 5 vddio pins that supply voltage to the i/o lines. These also get bypass caps. This is 10 bypass caps. That is a lot to place right off the bat. In addition, there are some pesky vddpll lines that ask for filtered inputs from either the main line or the regulator, meaning I have now inductors and more bypass caps. Oh my. Here is the schematic checklist diagram:

    schematic-power

    To do nice ADC things I want a well stabilized vrefp and vrefn, I will neglect doing this with this chip.

    Setting up the USB successfully is nontrivial, as it can be a properly high-speed differential line. I have bricked a few of these chips trying to implement the usb operation, so I'm going to skip most of this as well... Maybe breaking out the USBDM and USBDP lines just in case I get bored later, but I kind of doubt that.

    So, here it is. I didn't ask for this complexity. grumbling

    schematic-power

    Less talk more routing ... one note - I am putting some ground plane between all of the RX and TX lines, which I hope to be driving around-and-above 3MHz. So, I want them to not be coupling into eachother. Leaving some ground plane between each trace is a bit like shielding a wire... Here you can see two of the ports taking 'the dive' to the ground plane, where they have lots of room, and then being routed with some space between. I should update other boards using similar rules as well - I'm re-doing my BLDC driver and have started a stepper board that I'll be bringing up at the same time, so I can do that. Nice.