Différences
Ci-dessous, les différences entre deux révisions de la page.
Les deux révisions précédentes Révision précédente Prochaine révision | Révision précédente | ||
fr:uhsdr:uhsdrtroubleshooting [09.02.2018 08:00] – df9ts_user | fr:uhsdr:uhsdrtroubleshooting [26.02.2018 18:59] (Version actuelle) – df9ts_user | ||
---|---|---|---|
Ligne 20: | Ligne 20: | ||
=== Mode d' | === Mode d' | ||
- | Un MCU non fonctionnel peut être restauré - s'il n'y a pas de problème " | + | Un MCU non fonctionnel peut être restauré - s'il n'y a pas de problème " |
[[https:// | [[https:// | ||
Ligne 45: | Ligne 45: | ||
Le câble entr ST-Link/V2 est OVI40 UI ne doit pas dépasser 10 cm. 3 à 4 connexions sont nécessaires dans ce cable: | Le câble entr ST-Link/V2 est OVI40 UI ne doit pas dépasser 10 cm. 3 à 4 connexions sont nécessaires dans ce cable: | ||
- | |<40% 50% 50%>| | | + | |< 60% 50% 25% 25% >| |
- | |Interface utilisateur | + | |ST-link |
- | |JTAG-9 SWCLK|JP8 Pin 4| | + | |Pin-13 TRACESWO |
- | |JTAG-7 SWDIO|JP8 Pin 3| | + | |Pin-15 NRST |JP8 Pin 2 |
- | |JTAG-20 Gnd|JP8 Pin 6| | + | |Pin-07 |
- | |pas essentiel: Signal: Reset|JP8 Pin 2| | + | |Pin-09 SWCLK |JP8 Pin 4 |
+ | |Pin-01 MCU VDD |JP8 Pin 5 |VDD from MCU | ||
+ | |Pin-20 Gnd |JP8 Pin 6 | ||
{{: | {{: | ||
Ligne 79: | Ligne 80: | ||
1. Vous aurez besoin de l' | 1. Vous aurez besoin de l' | ||
- | 2. Connectez ST-LINK USB (3 Leitung | + | 2. Connectez ST-LINK USB (3 connections |
- | 3. Appliquez + 5V à l' | + | 3. Appliquez + 5V à OVI40 UI, puis dans l' |
- | 4. Si l' | + | 4. Si l' |
- | Ce sont les valeurs correctes: <50% 50% 50%> | + | [{{:uhsdr: |
- | |Protection | + | Voici les valeurs correctes: |
- | |Niveau | + | |< 50% 50% 50% >| |
- | |IWDG_SW:|Gesetzt| | + | |Read Out Protection: |
- | |WWDG_SW:|Gesetzt| | + | |BOR-Level:| Level3| |
- | |nRST_STOP: | + | |IWDG_SW: |
- | |nRST_STDBY: | + | |WWDG_SW: |
- | |FZ_IWDG_STOP: | + | |nRST_STOP: |
- | |FZ_IWDG_STDBY: | + | |nRST_STDBY: |
- | |nDBOOT:|Gesetzt| | + | |FZ_IWDG_STOP: |
- | |nBANQUE:|nicht gesetzt| | + | |FZ_IWDG_STDBY: |
- | |BOOT_ADD0: | + | |nDBOOT: |
- | |BOOT_ADD1: | + | |nDBANK:| pas coché| |
+ | |BOOT_ADD0: | ||
+ | |BOOT_ADD1: | ||
|Aucune case à cocher dans la case " | |Aucune case à cocher dans la case " | ||
- | ==== Bogues | + | ==== Erreurs dans le SW (" |
- | + | | |
- | La liste des problèmes | + | * Aussi intéressant de vérifier [[https:// |
- | - il peut ne pas être une erreur SW du tout, donc mieux vérifier | + | * Si vous ne trouvez pas votre problème discuter le dans le[[https:// |
- | + | - il se peut que ce n' | |
- | ==== Vérifiez le matériel défectueux ==== | + | * Au cas où vous pensez avoir découvert un "bug" |
- | + | | |
- | * MCU est-il soudé avec le Pin1 correct? | + | |
+ | ==== Vérifiez si votre matériel est défectueux ==== | ||
+ | * MCU: est-il bien soudé avec le Pin1 a l' | ||
* + 3.3V disponible pour MCU? Terre ok? | * + 3.3V disponible pour MCU? Terre ok? | ||
- | * Horloge TCXO disponible? | + | * Horloge TCXO ok? |
- | + | * Toutes les connexions de MCU aux ports USB OVI40 UI ok - pas de courts-circuits, | |
- | * Toutes les connexions de MCU aux ports USB ok - pas de courts-circuits, | + | |
- | + | ||
- | ===== UHSDR Troubleshooting ===== | + | |
- | + | ||
- | ==== LCD constant white screen ==== | + | |
- | + | ||
- | In case the LCD remains white (background light on, no text) after OVI40 UI power up this indicates | + | |
- | + | ||
- | * no UHSDR boot loader present or | + | |
- | * UHSDR boot loader doesn' | + | |
- | + | ||
- | The correct UHSDR functioning can be verified with simple means: | + | |
- | + | ||
- | * If the LCD flickers bright white when switching OVI40 UI on this indicates a bootloader present and working | + | |
- | * Press and keep pressed switch "Band +", then apply +5V to OVI40 UI. Text should appear on LCD. | + | |
- | * Press and keep pressed switch "Band -", then apply +5V to OVI40 UI. Text should appear on LCD. | + | |
- | + | ||
- | If this is not the case the boot loader needs to be (re)installed (see below). If this still doesn' | + | |
- | + | ||
- | ==== MCU " | + | |
- | + | ||
- | If there is no hardware defect it may help to re-install boot loader and firmware: | + | |
- | + | ||
- | * den [[: | + | |
- | * die [[: | + | |
- | + | ||
- | === In case ST-Link/V2 available === | + | |
- | + | ||
- | A non-functional MCU may be restored - if there is no hardware problem - with the ST-Link/V2 adapter and the required .bin file. The file can be found [[: | + | |
- | + | ||
- | [[https:// | + | |
- | + | ||
- | You will need: | + | |
- | + | ||
- | * STM32 ST-Link SW utility | + | |
- | * [[http:// | + | |
- | * [[: | + | |
- | + | ||
- | === 1. Preconditions === | + | |
- | + | ||
- | * STlink software installed | + | |
- | * ST-Link/V2 adapter connected | + | |
- | * PC connected to Internet | + | |
- | + | ||
- | === 2. ST-Link/V2 Firmware updateProcedure === | + | |
- | + | ||
- | * Connect ST-Link/V2 with PC via USB cable | + | |
- | * SW Utility: ST-Link→Firmware update | + | |
- | * Check on PC screen in status messages that MCU is reckognized correctly | + | |
- | [{{: | + | |
- | + | ||
- | === 3. Debug cable === | + | |
- | + | ||
- | The debug cable shouldn' | + | |
- | + | ||
- | |< 40% 50% 50% >| | + | |
- | + | ||
- | | ST-link UI | JP8 | | + | |
- | | JTAG-9 SWCLK | JP8 Pin 4 | | + | |
- | | JTAG-7 SWDIO | JP8 Pin 3 | | + | |
- | | JTAG-20 Gnd | JP8 Pin 6 | | + | |
- | | not essential: Signal: Reset | JP8 Pin 2 | | + | |
- | + | ||
- | {{: | + | |
- | + | ||
- | [{{: | + | |
- | + | ||
- | === 4. Connect === | + | |
- | + | ||
- | * SW Utility: Target→Connect | + | |
- | * SW Utility: File → Open (select the right .bin file, see above). The following screen should appear: (example shows mcHF boot loader) | + | |
- | [{{: | + | |
- | + | ||
- | === 5. Flash the MCU === | + | |
- | + | ||
- | * Write the .bin file onto MCU with Target → Program & Verify | + | |
- | * In the subsequent windo enter start address: | + | |
- | * start adresse for boot loader: 0x08000000 | + | |
- | * Then hit start button to program MCU | + | |
- | [{{: | + | |
- | + | ||
- | < | + | |
- | \\ * Then program firware in the same manner. | + | |
- | * start address for firm ware would be 0x08010000 | + | |
- | </ | + | |
- | + | ||
- | [{{: | + | |
- | + | ||
- | === 6. Done === | + | |
- | + | ||
- | Boot loader and firmware are now programmed again onto MCU. | + | |
- | + | ||
- | ==== Restore MCU Option bytes ==== | + | |
- | + | ||
- | 1. You will need the [[http:// | + | |
- | + | ||
- | 2. Connect ST-LINK USB (3 Leitung SWDIO, SWCLK und GND) with the corresponding pins of OVI40 UI (adapter cable see above). | + | |
- | + | ||
- | 3. Apply +5V to OVI40 UI, then in SW tool click Target→Connect. The MCU should be recognized, see status messages on screen. Otherwise re-check cables. | + | |
- | + | ||
- | 4. If ok in SW tool click Target→MCU Core to display MCU option bytes. | + | |
- | + | ||
- | These are the correct values: | + | |
- | + | ||
- | |< 50% 50% 50% >| | + | |
- | + | ||
- | |Read Out Protection: | + | |
- | |BOR-Level: | + | |
- | |IWDG_SW: | + | |
- | |WWDG_SW: | + | |
- | |nRST_STOP: | + | |
- | |nRST_STDBY: | + | |
- | |FZ_IWDG_STOP: | + | |
- | |FZ_IWDG_STDBY: | + | |
- | |nDBOOT: | + | |
- | |nDBANK: | + | |
- | |BOOT_ADD0: | + | |
- | |BOOT_ADD1: | + | |
- | |No ticks set at all in any box below "Flash Section Protection" | + | |
- | + | ||
- | ==== SW Bugs in boot loader or firmware ==== | + | |
- | + | ||
- | The list of open issues can be found [[https:// | + | |
- | + | ||
- | * Also interesting to check [[https:// | + | |
- | * If not found in open or closed issues please discuss on [[https:// | + | |
- | - it may not be a SW error at all, so better verify | + | |
- | * In case you think you discovered a bug not mentioned yet: | + | |
- | * Please post as new issue in Github. Add additional info as comment, if diiscovered later. | + | |
- | * Please be patient. All Github members work on this in their free spare time | + | |
- | + | ||
- | ==== Check for defective hardware ==== | + | |
- | + | ||
- | * Has MCU be soldered in with correct Pin1 orientation? | + | |
- | * +3.3V available for MCU? Ground available? | + | |
- | * TCXO clock available? | + | |
- | * All connections from MCU to USB ports ok - no shurtcuts, no interruptions? | + | |
- | + | ||
- | \\ | + | |