logo
Welcome, Guest. Please Login or Register.
24. April 2024, 15:01:04


Home Help Search Login RegisterWIKIUHSDR Download

Amateurfunk Sulingen
Diskussions- und Newsboard des DARC-Ortsverbandes I40  |  allgemeine Kategorie  |  OVI40 SDR Projekt (English AND German discussions around OVI40 SDR project) (Moderators: DF8OE, DL1PQ)  |  Topic: (SOLVED) OVI40 repair question <- zurück vorwärts ->
Pages: 1 [2] Go Down Print
   Author  Topic: (SOLVED) OVI40 repair question  (Read 4945 times)
WD8BXS
alter Hase
****

Offline

Posts: 286





View Profile
Re:OV140 repair question
« Reply #15 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
Logged

Thanks,
De WD8BXS vy 73
DF8OE
Administrator
*****

Offline

Posts: 6268



Stellvertr. OVV I40, Jugend / Nachwuchsreferent

View Profile WWW
Re:OV140 repair question
« Reply #16 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

vy 73
Andreas
Logged

Wenn der Wind des Wandels weht, nageln die einen Fenster und Türen zu und verbarrikadieren sich. Die anderen gehen nach draußen und bauen Windmühlen...
qrz.com-Seite von DF8OE
-----------------------------------------------------
>>>> Die Inhalte meiner Beiträge dürfen ohne meine explizite Erlaubnis in jedwedem Medium weiterverbreitet werden! <<<<
WD8BXS
alter Hase
****

Offline

Posts: 286





View Profile
Re:OVI40 repair question
« Reply #17 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
Logged

Thanks,
De WD8BXS vy 73
DF8OE
Administrator
*****

Offline

Posts: 6268



Stellvertr. OVV I40, Jugend / Nachwuchsreferent

View Profile WWW
Re:OVI40 repair question
« Reply #18 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
« Last Edit: 11. September 2018, 15:25:03 by DF8OE » Logged

Wenn der Wind des Wandels weht, nageln die einen Fenster und Türen zu und verbarrikadieren sich. Die anderen gehen nach draußen und bauen Windmühlen...
qrz.com-Seite von DF8OE
-----------------------------------------------------
>>>> Die Inhalte meiner Beiträge dürfen ohne meine explizite Erlaubnis in jedwedem Medium weiterverbreitet werden! <<<<
DB4PLE
positron
Urgestein
*****

Offline

Posts: 1278





View Profile
Re:OVI40 repair question
« Reply #19 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
Logged
WD8BXS
alter Hase
****

Offline

Posts: 286





View Profile
Re:OVI40 repair question
« Reply #20 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
Logged

Thanks,
De WD8BXS vy 73
DF8OE
Administrator
*****

Offline

Posts: 6268



Stellvertr. OVV I40, Jugend / Nachwuchsreferent

View Profile WWW
Re:OVI40 repair question
« Reply #21 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
« Last Edit: 11. September 2018, 17:44:42 by DF8OE » Logged

Wenn der Wind des Wandels weht, nageln die einen Fenster und Türen zu und verbarrikadieren sich. Die anderen gehen nach draußen und bauen Windmühlen...
qrz.com-Seite von DF8OE
-----------------------------------------------------
>>>> Die Inhalte meiner Beiträge dürfen ohne meine explizite Erlaubnis in jedwedem Medium weiterverbreitet werden! <<<<
WD8BXS
alter Hase
****

Offline

Posts: 286





View Profile
Re:OVI40 repair question
« Reply #22 on: 11. September 2018, 17:45:30 »

OK Andreas, I understand.
I will try to look for a topic that may help.

Chuck
Logged

Thanks,
De WD8BXS vy 73
DB4PLE
positron
Urgestein
*****

Offline

Posts: 1278





View Profile
Re:OVI40 repair question
« Reply #23 on: 11. September 2018, 20:59:40 »

Hi Chuck,

Quote from: 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

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
« Last Edit: 11. September 2018, 21:03:42 by DB4PLE » Logged
WD8BXS
alter Hase
****

Offline

Posts: 286





View Profile
Re:OVI40 repair question
« Reply #24 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
Logged

Thanks,
De WD8BXS vy 73
WD8BXS
alter Hase
****

Offline

Posts: 286





View Profile
Re:OVI40 repair question
« Reply #25 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
Logged

Thanks,
De WD8BXS vy 73
DF8OE
Administrator
*****

Offline

Posts: 6268



Stellvertr. OVV I40, Jugend / Nachwuchsreferent

View Profile WWW
Re:OVI40 repair question
« Reply #26 on: 12. September 2018, 06:36:12 »

Here is a hint for you

Hope this helps.

vy 73
Andreas
Logged

Wenn der Wind des Wandels weht, nageln die einen Fenster und Türen zu und verbarrikadieren sich. Die anderen gehen nach draußen und bauen Windmühlen...
qrz.com-Seite von DF8OE
-----------------------------------------------------
>>>> Die Inhalte meiner Beiträge dürfen ohne meine explizite Erlaubnis in jedwedem Medium weiterverbreitet werden! <<<<
peter_77
Urgestein
*****

Offline

Posts: 735



THE mcHF and UHSDR forum !

View Profile
Re:OVI40 repair question
« Reply #27 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
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
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.

« Last Edit: 13. September 2018, 11:56:03 by peter_77 » Logged
WD8BXS
alter Hase
****

Offline

Posts: 286





View Profile
Re:OVI40 repair question
« Reply #28 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
Logged

Thanks,
De WD8BXS vy 73
WD8BXS
alter Hase
****

Offline

Posts: 286





View Profile
Re:OVI40 repair question
« Reply #29 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
Logged

Thanks,
De WD8BXS vy 73
Pages: 1 [2] Go Up Print 
Diskussions- und Newsboard des DARC-Ortsverbandes I40  |  allgemeine Kategorie  |  OVI40 SDR Projekt (English AND German discussions around OVI40 SDR project) (Moderators: DF8OE, DL1PQ)  |  Topic: (SOLVED) OVI40 repair question <- zurück vorwärts ->
Jump to: 


Login with username, password and session length

 Es wird die Verwendung von Browsern die auf der "Blink"-Engine basieren und mindestens
1024x768 Pixel Bildschirmauflösung für die beste Darstellung empfohlen
 
Amateurfunk Die Beiträge sind, sofern nicht anders vermerkt, unter der folgenden Lizenz veröffentlicht:
GNU Free Documentation License 1.3 GNU Free Documentation License 1.3
verbindet!
Powered by MySQL Powered by PHP Diskussions- und Newsboard des DARC-Ortsverbandes I40 | Powered by YaBB SE
© 2001-2004, YaBB SE Dev Team. All Rights Reserved.
- modified by Andreas Richter (DF8OE)
Impressum & Disclaimer
Valid XHTML 1.0! Valid CSS!