Title: (SOLVED) OVI40 repair question
Post by: WD8BXS on 08. September 2018, 14:19:18
A friend sent me his non working OV140 board. He was having an RF board
issue, and kept plugging and unplugging the unit, NOT letting it boot up,
and now the board will not even turn on (white screen only) No LED's nothing.
I jumpered P6 to try to reload bootloader, but nothing happens, just white
screen. No computer recognition.
I have no real experience with this board, so any help would be appreciated.
Do you think he fried the MCU??
Thanks,
ChuckWD8BXS
|
Title: Re:OV140 repair question
Post by: DF8OE on 08. September 2018, 15:34:51
Hi Chuck,
same causes as on mcHF:
- MCU dead
- no clock to MCU
- missing or bad 3.3V
- missing or bad reset on MCU
- tracks to USB plug cut or shortend
vy 73
Andreas
|
Title: Re:OV140 repair question
Post by: peter_77 on 08. September 2018, 21:20:50
Try with a cheap ST-Link Adapter connected to JP8 (Debug Interface) if the CPU is still alive.
Otherwise as Andreas said...
Take the circuit diagram, check all voltages, CPU clock etc. if they have all their values.
The I40 can run standalone without RF if you apply 5V to the connection header pins.
|
Title: Re:OV140 repair question
Post by: WD8BXS on 10. September 2018, 02:18:36
I have clock signal
I have 3 v
I have good traces to USB
Not sure how to test "Bad or missing reset on MCU" |
Title: Re:OV140 repair question
Post by: DB4PLE on 10. September 2018, 05:30:53
Hi Chuck,
Not sure how to test "Bad or missing reset on MCU"
|
|
"Bad Reset" -> CPU is permanently in reset condition, for that you use a multimeter on the reset pin NRST (25). If it shows low level, you've got a problem here. Check C94 or solder bridges and power supply (which you already did).
"Missing Reset" is not a real problem, the power on reset / brown out reset will happen in any case on power on since the STM32 features an internal reset circuit.
However, clock is extremely important, I recently checked the ST bootloader document AN2606 and if I understood it correctly USB DFU bootloader mode will only work with the external clock available.
As Peter wrote, the use of a cheap ST-Link and the STM32 Link utility (or its linux equivalent) is the best way to figure out if the CPU is working, since the debug mode should work in any case (even if under reset or without external clock). Takes 2 seconds to verify that the tool connects to the CPU and you know it is kind of alive.
73
Danilo |
Title: Re:OV140 repair question
Post by: WD8BXS on 10. September 2018, 18:58:32
Hi Danilo,
I have one of the ST-Link devices, but I have no idea what to do with it..
Are there instructions anywhere that a novice like me can understand?
Thanks,
Chuck |
Title: Re:OV140 repair question
Post by: DB4PLE on 10. September 2018, 19:45:47
Hi Chuck,
1. connect the wires SWDIO, SWCLK and GND with the correspondingly named pins on the P8 pinheader.
2. Install STM32 Link Utility (at the very end of https://www.st.com/en/development-tools/stsw-link004.html (https://www.st.com/en/development-tools/stsw-link004.html) there is a "Get Software" button).
3. Plug in the ST-Link
4. Power the board with 5v, as usual
5. Start STM32 Link Utility, select menu "Target" -> "Connect"
If the cpu is powered correctly and you did the wiring of the 3 ST-Links signals correctly, you should now some output in the tools window telling you which processor it found. At this point you know the processor is not dead. Now you can try to do a "Erase chip" which normally brings the processor back into a state where the USB DFU mode works if there no solder bridges on the clock and USB data lines and a working external clock.
73
Danilo
|
Title: Re:OV140 repair question
Post by: WD8BXS on 10. September 2018, 19:55:47
OK, I did it, here is what I see!
de Chuck |
Title: Re:OV140 repair question
Post by: DB4PLE on 10. September 2018, 19:59:37
Hi Chuck,
the last lines tell you the problem:
"Disable read out protection and retry".
The "Erase Chip" operation does exactly that.
Instable power supply seems to get the STM32F767 in the read out protected state. In this state DFU is no longer working.
So please run "Target"->"Erase Chip", and the board is as good as new...
73
Danilo |
Title: Re:OV140 repair question
Post by: WD8BXS on 10. September 2018, 20:05:33
Title: Re:OV140 repair question
Post by: DB4PLE on 10. September 2018, 20:15:21
Hi Chuck,
that is strange. A full chip erase always returned the processor to a working state for me, and I also know it did the same for others.
Try it again. That is the only advice which I can give you...
73
Danilo |
Title: Re:OV140 repair question
Post by: WD8BXS on 10. September 2018, 21:18:36
NO Go, I keep getting
17:18:06 : Read out protection is activated
Chuck |
Title: Re:OV140 repair question
Post by: DB4PLE on 10. September 2018, 21:22:57
Hi Chuck,
the only other thing which comes to my mind is to try to go to the option bytes ("Target"->"Option Bytes") and try to set the read out protection to Level 0. But I doubt this will work. But trying is for free, so please try, you can't make this any worse than it is.
BTW: What is the message you get at the end of the "Erase Chip" operation? Do you see some error message or something indicating success of the erase?
73
Danilo
|
Title: Re:OV140 repair question
Post by: WD8BXS on 10. September 2018, 23:32:03
As soon as I click erase chip I get the warning that" read out protection is activated."
The it shows the same message in red in the lower window,
Is there a way to turn off read out protection?
Chuck |
Title: Re:OV140 repair question
Post by: WD8BXS on 10. September 2018, 23:34:59
I think that worked setting the read out to "0"
Here is the screen shot, now what do I do next?
Chuck |
Title: Re:OV140 repair question
Post by: WD8BXS on 10. September 2018, 23:41:43
I just jumpered P6 and tried to load the bootloader, but still just white screen, no USB acknowledgement
Chuck |
Title: Re:OV140 repair question
Post by: DF8OE on 11. September 2018, 06:55:21
That does not tell you anything. For professionel diagnosis you need a ST-Link (which is needed for professionel debugging of mcHF, too). It is possible to reconfigure STM MCUs by accident so that they do not show any life except you speak to them using ST-Link 8)
vy 73
Andreas |
Title: Re:OVI40 repair question
Post by: WD8BXS on 11. September 2018, 15:12:55
I do have the ST-Link Andreas, read the previous posts please.
What would you have me do next to figure this out??
Can I load bootloader / firmware with st-Link.
What next please!
TNX de Chuck WD8BXS |
Title: Re:OVI40 repair question
Post by: DF8OE on 11. September 2018, 15:22:11
You have to reenter some options and start vectors... Hope someone with Windows can attach a screenshot.
vy 73
Andreas |
Title: Re:OVI40 repair question
Post by: DB4PLE on 11. September 2018, 15:57:22
Hi,
yes, someone with an OVI40 F7 and ST-Link and Windows and STM32-Link should post a screenshot. I currently have no access to my OVI40 F7.
Chuck, meanwhile it would be worth trying "Target"->"Erase Chip" (or simply CTRL+E), it might now do the trick to reset everything to default.
73
Danilo |
Title: Re:OVI40 repair question
Post by: WD8BXS on 11. September 2018, 17:30:55
Now I am very confused, are you not reading my previous posts??
I have already used the target erase chip.
After I did that I tried to load the bootloader and all I get is white screen, no LED's
Chuck |
Title: Re:OVI40 repair question
Post by: DF8OE on 11. September 2018, 17:43:20
Mass erase does not set your vectors to the right values. This must be done seperately AFTER mass erase. I do it on Linux command line - not suitable for you.
There are already some screenshots of the Windows-tool for these settings in our discussion group but I do not have the time to dig for them.
EDIT:
You can apply firmware and bootloader via ST-Link without reconfiguring the vectors but it is better to do it right (== with correction).
vy 73
Andreas |
Title: Re:OVI40 repair question
Post by: WD8BXS on 11. September 2018, 17:45:30
OK Andreas, I understand.
I will try to look for a topic that may help.
Chuck |
Title: Re:OVI40 repair question
Post by: DB4PLE on 11. September 2018, 20:59:40
Hi Chuck,
Now I am very confused, are you not reading my previous posts??
I have already used the target erase chip.
After I did that I tried to load the bootloader and all I get is white screen, no LED's
Chuck
|
|
I do read you posts. I know that you did the Erase, which did not work, then you used the "Option Byte" to change read out protection.
And I did not knew that you tried "Chip Erase" after changing the read out protection. If you did, was not clear from your posts...
Anyway, I read the reference manual again (and again) and I would say, there might by no point in actually doing the Chip Erase.
Resetting the option bytes is not part of the "Mass Erase" operation. However, it might be the case that "Chip Erase" does not only do a Mass Erase of the Flash memory, the STM32 Link Utility documentation is not clear on that.
So your best bet is to get the boot address set correctly in the option bytes and all the other settings.
73
Danilo
|
Title: Re:OVI40 repair question
Post by: WD8BXS on 11. September 2018, 22:44:15
Thanks Danilo,
I do not know how to do that , so I will wait to see if someone posts how.
I do have a laptop that can run linux, so If I had instructions I could use that.
Chuck |
Title: Re:OVI40 repair question
Post by: WD8BXS on 11. September 2018, 23:27:51
I have searched as well, and see no reference to resetting the vectors.
Is there just a file I can load to do that?
Chuck |
Title: Re:OVI40 repair question
Post by: DF8OE on 12. September 2018, 06:36:12
Here is a hint for you (https://www.amateurfunk-sulingen.de/wiki/doku.php?id=en:uhsdr:uhsdrtroubleshooting)
Hope this helps.
vy 73
Andreas |
Title: Re:OVI40 repair question
Post by: peter_77 on 12. September 2018, 10:42:04
Maybe its a register problem...?!
Some I40 builders faced the same problem here when the MCU somehow scrambled the internal register setting.
Take a look here:
https://www.amateurfunk-sulingen.de/forum/index.php?board=15;action=display;threadid=577;start=315 (https://www.amateurfunk-sulingen.de/forum/index.php?board=15;action=display;threadid=577;start=315)
You should better check the MCU option byte settings with the ST-Link if they have the approriate values like Andreas posted:
https://www.amateurfunk-sulingen.de/forum/index.php?board=15;action=display;threadid=577;start=285 (https://www.amateurfunk-sulingen.de/forum/index.php?board=15;action=display;threadid=577;start=285)
Code:
Read Out Protection: Level0
BOR-Level: Level3
IWDG_SW: checked
WWDG_SW: checked
nRST_STOP: checked
nRST_STDBY: checked
FZ_IWDG_STOP: checked
FZ_IWDG_STDBY: checked
nDBOOT: checked
nDBANK: NOT checked
BOOT_ADD0: 0x0080 Boot from 0x200000
BOOT_ADD1: 0x0040 Boot from 0x100000 |
|
No checkmark set at all "Flash Section Protection" checkboxes !
This should definitely make the DFU mode working again.
Then you need to set jumper P6 and fire up the DFUSe tool again and flash the bootloader and firmware !
Make sure you have the .dfu files here (NOT the .bin !!) for both bootloader and firmware !
That should bring the I40 UI back to life.
|
Title: Re:OVI40 repair question
Post by: WD8BXS on 12. September 2018, 13:45:46
I reloaded registers, as listed with St-Link
Jumpered P6, and was able to load bootloader with dfuse
removed P6
Loaded firmware with USB, worked as normal
removed USB, radio came on to boot screen and stayed there.
Unplugged and reconnected power, now when I hit power button, just white screen.
Chuck |
Title: Re:OVI40 repair question
Post by: WD8BXS on 12. September 2018, 13:52:10
Well, I put P6 jumper back in and reloaded bootloader AND firmware with the DFuse, and now all is well!!!
Thanks to all who helped out!
Chuck |
Diskussions- und Newsboard des DARC-Ortsverbandes I40 | Powered by YaBB SE
© 2001-2003, YaBB SE Dev Team. All Rights Reserved.
|