User Tools

Site Tools


doc:tools_oobdflash

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
doc:tools_oobdflash [2014/07/05 16:24] – created admindoc:tools_oobdflash [2014/08/26 11:20] (current) wsauer
Line 1: Line 1:
 ====== OOBDFlash Update your Dongle Firmware Easily ====== ====== OOBDFlash Update your Dongle Firmware Easily ======
 +
  
 Straight from the beginning the bootloader was designed to allow an easy and safe update of the firmware - but on the users side that was not really simple to flash a dongle with a terminal program and the right flash file. Straight from the beginning the bootloader was designed to allow an easy and safe update of the firmware - but on the users side that was not really simple to flash a dongle with a terminal program and the right flash file.
  
-So this process is now integrated into OOBDFlash+ 
 +So this process is now integrated into [[https://drive.google.com/folderview?id=0B795A63vSunRZU90QWVPUnowMmM&usp=sharing&tid=0B795A63vSunRbk1jc3U5VFFJbkU| OOBDFlash]]
  
 The final plan is to integrate this flash function directly into the apps, but first the process needs to be under control - so OOBDFlash is also a proof of concept of an automated tool. The final plan is to integrate this flash function directly into the apps, but first the process needs to be under control - so OOBDFlash is also a proof of concept of an automated tool.
Line 9: Line 11:
  
 ===== How does OOBDFlash work? ===== ===== How does OOBDFlash work? =====
 +
  
 Without any command line option, OOBDFlash runs the following sequence at start: Without any command line option, OOBDFlash runs the following sequence at start:
  
-  - download the latest firmware archive file from the public OOBD download server + 
-  - searches inside that archive for the latest firmware binary +    - download the latest firmware archive file from the public OOBD download server 
-  - starts a Bluetooth Discovery to find all dongles around +    - searches inside that archive for the latest firmware binary 
-  - lets the user select the dongle he wants to update +    - starts a Bluetooth Discovery to find all dongles around 
-  - flashes the firmware +    - lets the user select the dongle he wants to update 
-  - reboots the dongle+    - flashes the firmware 
 +    - reboots the dongle
  
  
 So basically an update can be done with minimal user interaction So basically an update can be done with minimal user interaction
 +
  
 ===== The Command line Options ===== ===== The Command line Options =====
 +
  
 OOBDFlash is set up as command line program without a graphical UI. This, together with some command line options, allows it to run OOBDFlash also from a script or even as part of a makefile. OOBDFlash is set up as command line program without a graphical UI. This, together with some command line options, allows it to run OOBDFlash also from a script or even as part of a makefile.
 +
  
 The options are: The options are:
  
-  java -jar OOBDFlash.jar [-d BT-MAC] [-f firmwarefile | -u Download-URL | -l Archivefile]"); + 
-  +<code> 
 +java -jar OOBDFlash.jar [-d BT-MAC] [-f firmwarefile | -u Download-URL | -l Archivefile] 
 +</code> 
 + 
 ==== -d BT-MAC ==== ==== -d BT-MAC ====
 +
 +
 When giving the Bluetooth Dongle MAC address as 12 character long hexadecimal string like 00112233445566, this address is taken directly to address the Dongle and no further Bluetooth Device Discovery is made When giving the Bluetooth Dongle MAC address as 12 character long hexadecimal string like 00112233445566, this address is taken directly to address the Dongle and no further Bluetooth Device Discovery is made
 +
  
 ==== -f firmwarefile ==== ==== -f firmwarefile ====
 +
  
 When given, that file is directly used as binary firmware file for the flash process instead of any archive file source When given, that file is directly used as binary firmware file for the flash process instead of any archive file source
Line 39: Line 54:
  
 ==== -u Download-URL ==== ==== -u Download-URL ====
 +
 +
 Overrides the build in Download- URL for the firmware archive Overrides the build in Download- URL for the firmware archive
 +
  
 ==== -l Archivefile ==== ==== -l Archivefile ====
-Uses a local file as "downloadable" firmware archive. Very similar to option -u, but while -u needs a correct URL syntax, -i handle files as normal file path names 
  
 +
 +Uses a local file as "downloadable" firmware archive. Very similar to option -u, but while -u needs a correct URL syntax, -i handle files as normal file path names
  
  
 ===== The Settings File ===== ===== The Settings File =====
-Behind a firewall like in a cooperate network, OOBDFlash might need to have a proxy to be able to download the firmware archive file. If needed, the two entries in the file ''OOBDFlash.props'' need to be uncommented and filled with the correct values for proxyhost and proxyport+ 
 + 
 +Behind a firewall like in a cooperate network, OOBDFlash might need to have a proxy to be able to download the firmware archive file. If needed, the two entries in the file ''OOBDFlash.props''  need to be uncommented and filled with the correct values for proxyhost and proxyport 
  
 <code> <code>
Line 59: Line 81:
 # the port  # the port 
 #httpProxyPort 83 #httpProxyPort 83
-</code>  +</code> 
  
 ===== Troubleshooting ===== ===== Troubleshooting =====
  
-Under Windows it happens that the Bluetooth connection fails permanently. This can be fixed when (unpairing and) pairing the dongle with the Windows Bluetooth manager first. This unfortunately destroys the idea of a quick ad-hoc flash process, so we working on it... + 
 +Under Windows it happens that the Bluetooth connection fails permanently. This can be fixed when (unpairing and) pairing the dongle with the Windows Bluetooth manager first. This unfortunately destroys the idea of a quick ad-hoc flash process, so we working on it
  
doc/tools_oobdflash.1404570279.txt.gz · Last modified: 2014/07/05 16:24 by admin