BringUpWin » History » Version 5
laforge, 10/11/2019 12:25 PM
| 1 | 3 | {{>toc}} |
|
|---|---|---|---|
| 2 | 1 | ||
| 3 | 3 | h1. Bring-Up (Windows) |
|
| 4 | 1 | ||
| 5 | 3 | ||
| 6 | After manufacturing, the [[OsmoSDR]] device has to be flashed with the USB-DFU loader. Only after that the normal update procedure using usbdfu will work. |
||
| 7 | |||
| 8 | 1 | This procedure has also to be repeated when the USB-DFU loader needs to be upgraded. |
|
| 9 | |||
| 10 | |||
| 11 | 3 | h2. Remove any old firmware |
|
| 12 | |||
| 13 | |||
| 14 | 1 | To remove the old firmware from the device, follow these steps: |
|
| 15 | |||
| 16 | 3 | - disconnect the [[OsmoSDR]] from the USB port |
|
| 17 | 1 | - put a jumper on the ERASE jumper |
|
| 18 | 3 | - connect the [[OsmoSDR]] to the USB port |
|
| 19 | 1 | - remove the jumper |
|
| 20 | |||
| 21 | Now the Atmel CPU is blank again and the device will show up with the USB ID 03eb / 6124. You will need the attached .inf-file to bind the CDC ACM driver, which is integrated into Windows, to the device. |
||
| 22 | |||
| 23 | 3 | h2. Install CDC ACM driver |
|
| 24 | 1 | ||
| 25 | 3 | ||
| 26 | Windows sometimes seems to detect the [[OsmoSDR]] as GPS device or even as mouse. No idea why this happens, but then again it's just Windows. |
||
| 27 | 1 | ||
| 28 | 5 | laforge | Please use the attached attachment:osmosdr.inf to bind the Windows CDC ACM driver to the [[OsmoSDR]]. If everything works, you should find a device called "ATMEL SAM3U Initial Flash Driver (COMxx)" in the "Ports (COM & LPT)" section of the Windows driver manager. |
