Resetting the Arduino Uno R3 Atmega16U2

Thanks so much for your help dhunt. Here is the terminal output when I try to run the code:

Jacks-MacBook-Pro:Downloads JackBookPro$ tar xzf ~/Downloads/dfu-programmer-0.5.4.tar.gz
Jacks-MacBook-Pro:Downloads JackBookPro$ cd dfu-programmer-0.5.4
Jacks-MacBook-Pro:dfu-programmer-0.5.4 JackBookPro$ patch -p0 < ~/Downloads/atmega16u2.diff
patching file src/arguments.c
patching file src/arguments.h
Jacks-MacBook-Pro:dfu-programmer-0.5.4 JackBookPro$ sudo apt-get install build-essential libusb-1.0-0-dev
sudo: apt-get: command not found

Upon further investigation, it appears as though I need to install the libsub-1.0-0-dev library, which I found online here: http://libusb.6.n5.nabble.com/libusb-1-0-0-released-td6100.html Upon downloading libusb-1.0.0.tar.bz2, unpacking it and following the included installation instructions, I get this:

Jacks-MacBook-Pro:~ JackBookPro$ cd Downloads/libusb-1.0.0
Jacks-MacBook-Pro:libusb-1.0.0 JackBookPro$ ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... ./install-sh -c -d
checking for gawk... no
checking for mawk... no
checking for nawk... no
checking for awk... awk
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... 
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking build system type... i386-apple-darwin11.3.0
checking host system type... i386-apple-darwin11.3.0
checking for a sed that does not truncate output... /usr/bin/sed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
checking for ld used by gcc... /usr/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin11/4.2.1/ld
checking if the linker (/usr/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin11/4.2.1/ld) is GNU ld... no
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm
checking the name lister (/usr/bin/nm) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 196608
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking for /usr/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin11/4.2.1/ld option to reload object files... -r
checking for objdump... no
checking how to recognize dependent libraries... pass_all
checking for ar... ar
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm output from gcc object... ok
checking for dsymutil... dsymutil
checking for nmedit... nmedit
checking for lipo... lipo
checking for otool... otool
checking for otool64... no
checking for -single_module linker flag... yes
checking for -exported_symbols_list linker flag... yes
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fno-common -DPIC
checking if gcc PIC flag -fno-common -DPIC works... yes
checking if gcc static flag -static works... no
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin11/4.2.1/ld) supports shared libraries... yes
checking dynamic linker characteristics... darwin11.3.0 dyld
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for inline... inline
checking whether gcc and cc understand -c and -o together... yes
[b]checking operating system... configure: error: unsupported operating system[/b]

Does this mean that OSX Lion 10.7.3 does not support the libsub-1.0-0-dev library needed to rebuild the dfu-programmer?

Ok I gave you instructions for the wrong OS, sorry. I've built it on OSX 10.6.8 without problems (the patch still applies the same way with patch -p0), I'll give it a go tonight on a lion VM with 10.7.3.

I use MacPorts (http://www.macports.org/) as a package manger on my Mac to get easy access to ported libraries and apps.

I wasn't able to get the xcode install completed on my lion system tonight - it wants to spend 2 hours downloading for some reason.

But on 10.6.8 I built and installed this libusb version without any problems: Download libusb-1.0.8.tar.bz2 (libusb). Do the usual ./configure; make; sudo make install.

After that you should be able to build dfu-programmer.

I got the dfu-programmer to build on OSX Lion 10.7.3 with the following steps:

  • Install Xcode 4.3 from the Appstore
  • Install Xcode command line tools from Xcode preferences (see Documentation Archive).
  • Tell Xcode where Xcode is installed: sudo xcode-select -switch /Applications/Xcode.app
  • Set up a link for the missing clang executable: cd /Applications/Xcode.app/Contents/Developer/usr/bin; sudo ln -s clang llvm-gcc; cd -
  • Install macports from http://www.macports.org/
  • Install autoconf tools via macports: sudo port install pkgconfig automake
  • Install libusb via macports: sudo port install libusb-devel
  • Configure and build dfu-programmer: cd dfu-programmer-0.5.4; ./bootstrap.sh; ./configure; ./make; ./sudo make install

After this you should be pretty much set for building other packages and tools too. You can also search for available packages using the macports search command.

For example:

port search libusb
libusb @1.0.8 (devel)
    library for USB device access

libusb-compat @0.1.3 (devel)
    library for USB device access

libusb-devel @1.0.8.20101017 (devel)
    library for USB device access

libusb-legacy @0.1.12 (devel)
    Library providing access to USB devices

I can't thank you enough for all of your help! I installed Xcode and the command line tools and tried to execute the code you gave me, but I made a mistake; I ran the sudo port install pkgconfig automake command before putting in sudo ln -s clang llvm-gcc and then -cd:

Jack-Wolfes-MacBook-Pro:bin JackBookPro$ cd
Jacks-MacBook-Pro:~ JackBookPro$ sudo xcode-select -switch /Applications/Xcode.app
Jacks-MacBook-Pro:~ JackBookPro$ cd /Applications/Xcode.app/Contents/Developer/usr/bin
Jacks-MacBook-Pro:bin JackBookPro$ sudo port install pkgconfig automake
Warning: port definitions are more than two weeks old, consider using selfupdate
--->  Computing dependencies for pkgconfig
--->  Cleaning pkgconfig
--->  Computing dependencies for automake
--->  Dependencies to be installed: autoconf help2man p5.12-locale-gettext m4
--->  Fetching archive for p5.12-locale-gettext
--->  Attempting to fetch p5.12-locale-gettext-1.50.0_6.darwin_11.x86_64.tbz2 from http://packages.macports.org/p5.12-locale-gettext
--->  Fetching p5.12-locale-gettext
--->  Attempting to fetch gettext-1.05.tar.gz from ftp://ftp.cpan.org/pub/CPAN/modules/by-module/Locale
--->  Verifying checksum(s) for p5.12-locale-gettext
--->  Extracting p5.12-locale-gettext
--->  Applying patches to p5.12-locale-gettext
--->  Configuring p5.12-locale-gettext
--->  Building p5.12-locale-gettext
--->  Staging p5.12-locale-gettext into destroot
--->  Installing p5.12-locale-gettext @1.50.0_6
--->  Activating p5.12-locale-gettext @1.50.0_6
--->  Cleaning p5.12-locale-gettext
--->  Fetching archive for help2man
--->  Attempting to fetch help2man-1.40.4_1.darwin_11.x86_64.tbz2 from http://packages.macports.org/help2man
--->  Fetching help2man
--->  Attempting to fetch help2man-1.40.4.tar.gz from ftp://ftp.gnu.org/gnu/help2man
--->  Verifying checksum(s) for help2man
--->  Extracting help2man
--->  Configuring help2man
[b]Error: Target org.macports.configure returned: configure failure: shell command failed (see log for details)
Error: Failed to install help2man
Log for help2man is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_help2man/help2man/main.log
Error: The following dependencies were not installed: autoconf help2man m4
Error: Status 1 encountered during processing.[/b]
To report a bug, see <http://guide.macports.org/#project.tickets>

After that, I tried switching back to the main directory but I kept getting the same error:

Jack-Wolfes-MacBook-Pro:~ JackBookPro$ cd /Applications/Xcode.app/Contents/Developer/usr/bin
Jacks-MacBook-Pro:bin JackBookPro$ sudo ln -s clang llvm-gcc
[b]ln: llvm-gcc: File exists[/b]
Jacks-MacBook-Pro:bin JackBookPro$ cd -
/Users/JackBookPro
Jacks-MacBook-Pro:~ JackBookPro$ sudo port install pkgconfig automake
--->  Computing dependencies for pkgconfig
--->  Cleaning pkgconfig
--->  Computing dependencies for automake
--->  Dependencies to be installed: autoconf help2man m4
--->  Configuring help2man
Error: Target org.macports.configure returned: configure failure: shell command failed (see log for details)
Error: Failed to install help2man
Log for help2man is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_help2man/help2man/main.log
Error: The following dependencies were not installed: autoconf help2man m4
Error: Status 1 encountered during processing.
To report a bug, see <http://guide.macports.org/#project.tickets>
Jacks-MacBook-Pro:~ JackBookPro$ sudo port install libusb-devel
--->  Computing dependencies for libusb-devel
[b]Error: Unable to execute port: Can't install libusb-devel because conflicting ports are installed: libusb[/b]

Do you know what these errors mean, and how I can avoid encountering them? I've attached the main.log file referenced in the above code. Please excuse my limited knowledge of programming; I'm a much better digital artist than I am a coder.

main.log (3.74 KB)

It might be easiest to just uninstall macports and install it again. 2.4. Uninstall MacPorts

Make sure running clang from a terminal works before you install it.

hi,
i had kind of the same problem.
my uno r3 stopped responding after setting the baudrate to 14400 and started to create a new serial (/dev/ttyACM*) port with each reset.
i did patch and build the dfu-programmer with the mentioned patch but when it comes to flashing the firmware i get a parsing error:

sudo dfu-programmer atmega16u2 flash unor3.hex
Error parsing the line.
Something went wrong with creating the memory image.
(i renamed the the *.hex for being lazy in the typing area).

uname -a
Linux laptopanatol2 2.6.32-39-generic #86-Ubuntu SMP Mon Feb 13 21:47:32 UTC 2012 i686 GNU/Linux

the lsusb returns a "03eb:2fef Atmel Corp" device (instead of the unnamed 2341:0043 which used to be the arduino)
and dmesg confirms the "full speed USB device"

the erase command with dfu-programmer went just fine and that was the last i heard from the arduino.

any idea if i got the wrong firmware or if the patch went wrong? (the one i used was "Arduino-usbserial-atmega16u2-Uno-Rev3.hex" from the git)

dhunt:

tar xzf ~/Downloads/dfu-programmer-0.5.4.tar.gz

cd dfu-programmer-0.5.4
patch -p0 < ~/Downloads/atmega16u2.diff

Make sure you have the tools needed to build it

sudo apt-get install build-essential libusb-1.0-0-dev

configure and build it

./bootstrap.sh
./configure

bootstrap succeeds, but configure fails with:
./configure: line 3588: syntax error near unexpected token LIBUSB_1_0,' ./configure: line 3588: PKG_CHECK_MODULES(LIBUSB_1_0, libusb-1.0 >= 1.0.0 , have_libusb_1_0=yes, have_libusb_1_0=no)'

This is on Debian 6.
Help?

hodwy,
it seems to me that you have the *dev lib installed but not libusb itself.
just do the sudo apt-get install libusb (don't remember the package name right now but you could use aptitude to search for it)
recompile again and it should go fine

anatolw:
hodwy,
it seems to me that you have the *dev lib installed but not libusb itself.
just do the sudo apt-get install libusb (don't remember the package name right now but you could use aptitude to search for it)
recompile again and it should go fine

That would be weird. Installing the dev lib should install the base lib also. E.g. apt-rdepends output for libusb-1.0-0-dev:
libusb-1.0-0-dev
Depends: libc-dev
Depends: libc6-dev
Depends: libusb-1.0-0 (= 2:1.0.8-4)

I would think it more likely that libusb-1.0-0-dev and libusb-1.0-0 is not installed.

Running "dpkg -l | grep libusb" would be one way to check.

right you are dhunt,
but you never know
it turns out that my *.hex was corrupted
i got the right one now and the flashing went fine
never the less, the arduino, even with the new bootloader, still doesn't respond to the arduino ide.
i've got the /dev/ttyACM0, the ide reports it correctly, but when it comes to uploading i get a java error:

Experimental: JNI_OnLoad called.
Stable Library

Native lib Version = RXTX-2.1-7
Java lib Version = RXTX-2.1-7
RXTX Warning: Removing stale lock file. /var/lock/LCK..ttyACM0
processing.app.SerialException: Error opening serial port '/dev/ttyACM0'.
at processing.app.Serial.(Serial.java:146)
at processing.app.Serial.(Serial.java:91)
at processing.app.SerialMonitor.openSerialPort(SerialMonitor.java:204)
at processing.app.Editor.handleSerial(Editor.java:2415)
at processing.app.EditorToolbar.mousePressed(EditorToolbar.java:352)
at java.awt.Component.processMouseEvent(Component.java:6200)
at javax.swing.JComponent.processMouseEvent(JComponent.java:3267)
at java.awt.Component.processEvent(Component.java:5968)
at java.awt.Container.processEvent(Container.java:2105)
at java.awt.Component.dispatchEventImpl(Component.java:4564)
at java.awt.Container.dispatchEventImpl(Container.java:2163)
at java.awt.Component.dispatchEvent(Component.java:4390)
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4461)
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4122)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4055)
at java.awt.Container.dispatchEventImpl(Container.java:2149)
at java.awt.Window.dispatchEventImpl(Window.java:2478)
at java.awt.Component.dispatchEvent(Component.java:4390)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:649)
at java.awt.EventQueue.access$000(EventQueue.java:96)
at java.awt.EventQueue$1.run(EventQueue.java:608)
at java.awt.EventQueue$1.run(EventQueue.java:606)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:105)
at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:116)
at java.awt.EventQueue$2.run(EventQueue.java:622)
at java.awt.EventQueue$2.run(EventQueue.java:620)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:105)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:619)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:275)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:200)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:185)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:177)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:138)
Caused by: gnu.io.UnsupportedCommOperationException: Invalid Parameter
at gnu.io.RXTXPort.setSerialPortParams(RXTXPort.java:171)
at processing.app.Serial.(Serial.java:136)
... 35 more

anyone got an idea?
might it be a mixup between processing and arduino libs?

edit (just a few hours later)
sorry about filling it up
a very strange thing happened with the user permissions
i had to re-add myself to the dialout group to get r/w access to the /dev/ttyACM* and still i have no clue wtf happend.

anatolw:
my uno r3 stopped responding after setting the baudrate to 14400 and started to create a new serial (/dev/ttyACM*) port with each reset.

Last time I looked (about 3 years ago when Teensy started and all Arduino boards were still FTDI), multiple software issues all combined in a terrible way.

1: Linux cdc_acm driver didn't support 14400 and 28800 baud settings.

2: The RXTX library behaves badly when an unsupported baud rate setting is configured.

3: Arduino remembers and applies the old setting before giving you the serial monitor window, and won't accept a new setting after RXTX starts misbehaving.

The net result was choosing either of these baud rates made the board forever inaccessible. The only way to fix it was editing the prefs file to change back to a supported baud rate.

One of the many patches Teensyduino installs is a tiny bit of code which silently turns 14400 into 19200 and 28800 into 38400 if Linux is in use, and a Teensy board is selected. I'd pretty much forgotten about this little problem until now....

Hopefully this explanation helps?

hi there.

have some issue with flashing my mega 2560 R3

this is what i did so far:

http://arduino.cc/forum/index.php/topic,99902.0.html

following @dhunts suggestion

".......

Ah yes, dfu-programmer 0.5.4 does not know about the atmega16u2 and the developers don't seem to have updated it yet.

Download the dfu-programmer source from Atmel USB DFU Programmer download | SourceForge.net, apply the attached patch and build your own:
Code:
tar xzf ~/Downloads/dfu-programmer-0.5.4.tar.gz
cd dfu-programmer-0.5.4
patch -p0 < ~/Downloads/atmega16u2.diff

Make sure you have the tools needed to build it

sudo apt-get install build-essential libusb-1.0-0-dev

configure and build it

./bootstrap.sh
./configure
make

install it

.........."

i get this results

Claudio-Battistas-MacBook-Pro:dfu-programmer-0.5.4 claudiobattista$ sudo apt-get install build-essential libusb-1.0-0-dev
Password:
sudo: apt-get: command not found

what am i missing here?

apt-get is a debian package management tool, so if you're not running a debian-based destroy (like Ubuntu) you'll have to use whatever package manager comes with your distro instead. There should also be a GUI interface tat you can use instead of the command line.

Hi Claudio,

We have managed to get the Chronome firmware to install using Mac OS X 10.6 by doing roughly the following:

Install autoconf tools via macports: sudo port install pkgconfig automake

Install libusb development packages:
sudo port install libusb-devel
and maybe before that
sudo port uninstall libusb
if you have the trouble installing that you did earier.

installing dfu-programmer from source whilst utilising dhunt's patch:

tar xzf ~/Downloads/dfu-programmer-0.5.4.tar.gz
cd dfu-programmer-0.5.4
patch -p0 < ~/Downloads/atmega16u2.diff

# configure and build it
./bootstrap.sh
./configure
make

# install it
sudo make install

now you don't need to run dfd-programmer yourself doing the build of arduino-usbserial will do that for you later but first you need to tweak its makefile so it's looking for your more modern board by editing the following lines in it:

MCU_AVRDUDE = at90usb82                                                       
MCU_DFU = at90usb82

such that they look like:

MCU_AVRDUDE = atmega16u2
MCU_DFU = atmega16u2

and now short the pads to put the arduino in dfu mode and do

sudo make dfu

it should install this time, then install the chronome sw on to it, get serialosc going and you can get on with testing your hardware!

that's probably a fairly hacky way of doing things but it got us going!

hi tristan.

can´t wait to get home to try this out....
will let you know....
thanks in the meanwhile.

so exited.... :sweat_smile:

no luck sofar =( =( =(

still get this error when typing ./configure

...configure: error: cannot run C compiled programs.
If you meant to cross compile, use --host'. See config.log' for more details.

same when i try to instal chronome serialosc. even when trying to instal libconfuse....

thanks.

Claudio-Battistas-MacBook-Pro:~ claudiobattista$ tar xzf ~/Downloads/dfu-programmer-0.5.4.tar
Claudio-Battistas-MacBook-Pro:~ claudiobattista$ cd dfu-programmer-0.5.4
Claudio-Battistas-MacBook-Pro:dfu-programmer-0.5.4 claudiobattista$ patch -p0 < ~/Downloads/atmega16u2.diff
patching file src/arguments.c
patching file src/arguments.h
Claudio-Battistas-MacBook-Pro:dfu-programmer-0.5.4 claudiobattista$ ./bootstrap.sh
Claudio-Battistas-MacBook-Pro:dfu-programmer-0.5.4 claudiobattista$ ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... m4/install-sh -c -d
checking for gawk... no
checking for mawk... no
checking for nawk... no
checking for awk... awk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... configure: error: in /Users/claudiobattista/dfu-programmer-0.5.4': configure: error: cannot run C compiled programs. If you meant to cross compile, use --host'.
See `config.log' for more details

i´m running out of ideas.

seems my mainproblem is, this error:

configure: error: cannot run C compiled programs.

it just WON´T let me ./configure

@triss

it´s working like a charm now. the problem was some funny issue with my root permission which didn´t allow me to do some commands in terminal... jus had a little jam with pages and ableton.... :slight_smile:

thanks a ton

after installing dfu programmer and patching
I get this:

cortex:~ nicosteckhan$ sudo dfu-programmer atmega16u2 erase
dfu-programmer 0.5.4
Usage: dfu-programmer target command [command-options] [global-options] [file|data]
targets:
at89c51snd1c
at89c51snd2c
at89c5130
at89c5131
at89c5132
at90usb1287
at90usb1286
at90usb1287-4k
at90usb1286-4k
at90usb647
at90usb646
at90usb162
at90usb82
atmega32u6
atmega32u4
atmega32u2
atmega16u4
atmega8u2
at32uc3a0128
at32uc3a1128
at32uc3a0256
at32uc3a1256
at32uc3a0512
at32uc3a1512
at32uc3a0512es
at32uc3a1512es
at32uc3a364
at32uc3a364s
at32uc3a3128
at32uc3a3128s
at32uc3a3256
at32uc3a3256s
at32uc3b064
at32uc3b164
at32uc3b0128
at32uc3b1128
at32uc3b0256
at32uc3b1256
at32uc3b0256es
at32uc3b1256es
at32uc3b0512
at32uc3b1512
at32uc3c064
at32uc3c0128
at32uc3c0256
at32uc3c0512
at32uc3c164
at32uc3c1128
at32uc3c1256
at32uc3c1512
at32uc3c264
at32uc3c2128
at32uc3c2256
at32uc3c2512
global-options: --quiet, --debug level
commands:
configure {BSB|SBV|SSB|EB|HSB} [--suppress-validation] [global-options] data
dump [global-options]
dump-eeprom [global-options]
dump-user [global-options]
erase [--suppress-validation] [global-options]
flash [--suppress-validation] [--suppress-bootloader-mem] [global-options] {file|STDIN}
flash-eeprom [--suppress-validation] [global-options] {file|STDIN}
flash-user [--suppress-validation] [global-options] {file|STDIN}
get {bootloader-version|ID1|ID2|BSB|SBV|SSB|EB|
manufacturer|family|product-name|
product-revision|HSB} [global-options]
getfuse {LOCK|EPFL|BOOTPROT|BODLEVEL|BODHYST|
BODEN|ISP_BOD_EN|ISP_IO_COND_EN|
ISP_FORCE} [global-options]
setfuse {LOCK|EPFL|BOOTPROT|BODLEVEL|BODHYST|
BODEN|ISP_BOD_EN|ISP_IO_COND_EN|
ISP_FORCE} [global-options] data
reset [global-options]
start [global-options]
version [global-options]
cortex:~ nicosteckhan$

any ideas ?