Diskussions- und Newsboard des DARC-Ortsverbandes I40
allgemeine Kategorie => mcHF Projekt Deutsch / English (here you can discuss everything related to mcHF) => Message started by: WD8BXS on 22. April 2021, 06:55:59

Title: And another NEW issue!!
Post by: WD8BXS on 22. April 2021, 06:55:59

I have a real issue here!

Brand new board set, turns on, works fine. Came up with the latest bootloader and firmware showing.

Does not see the EEprom, will NOT go into DFU mode. With or without P6 jumpered.

Tried another fresh UI board, same result!

Computer WILL see the radio when it is on though through DFU USB port!

These are fresh kits!

Tried to get ST-link to work, nothing.

Hooked ST-Link to: swdio, swclock, gnd and 3v to pin 27 on header Nothing

Any ideas?

de Chuck WD8BXS

Title: Re:And another NEW issue!!
Post by: DF8OE on 22. April 2021, 09:06:03

Hi Chuck,

No identification of EEPROM:
- bad solderings
- wrong level (1025/1026 need different level at pin 3)
- EEPROM was not empty at install (clean it via menu function)

No DFU:
- user fault (set P6 - press correct band button at startup)
- I have ONE single mcHF with 429MCU that has lost configuration vectors and cannot be corrected via ST-Link. This one does not work on DFU, neither on P6 method nor on bootloader set DFU mode. This is very strange and I have to replace the MCU. But I can use USB-stick for upgrades so I will not do this...

ST-Link:
you need to connect SWDIO, SWCLK and GND. Reset can be connected - but it is not mandatory. And 3V should not be connected. Please supply power via header to rf board.

vy 73
Andreas

Title: Re:And another NEW issue!!
Post by: SP9BSL on 22. April 2021, 09:28:57

Hi,
in both cases (Chuck and Andreas) looks like protection level 2 was enabled. In this state no recovery is possible. We've seen similar behaviour here except that there was protection level 1 activated.
Chuck, before changing the processor try to observe 3.3V power rail with oscilloscope close to processor power pins, maybe that there are some ripples or spikes.

Title: Re:And another NEW issue!!
Post by: WD8BXS on 22. April 2021, 12:35:46

I also forgot to note that if will not update the firmware via USB..
I sees the usb and gets as far as saving backup to flash memory


Will try ST-Link later today, if I remember what to do when I get it working, hihi

Should have written that down.

Thanks,
Chuck

Title: Re:And another NEW issue!!
Post by: DF8OE on 22. April 2021, 13:51:28

If you only see "saving..." you released BAND- button too early... You must hold it until message "firmware will be updated" appears.

vy 73
Andreas

Title: Re:And another NEW issue!!
Post by: WD8BXS on 22. April 2021, 19:10:01

Yes, I held it for a real long time.

OK I got the ST-Link to connect, now what do I do???

I think I have done it on a OV140 board but not an mchf


Chuck

Title: Re:And another NEW issue!!
Post by: WD8BXS on 22. April 2021, 19:32:39

OK, I hooked up ST-LINK
Loaded bootloader and Firmware.

Same result: will not go into DFU, screen says release Band + to go into dfu mode.

When I release, the screen blanks then the radio boots up and goes into button test screen since I still have the power button pushed.

I think I will try erasing the chip again and then use P6 to load and see what happens.

Chuck

Title: Re:And another NEW issue!!
Post by: WD8BXS on 22. April 2021, 19:55:44

Now ST-Link will not connect !!!

DRAT!!!!

Title: Re:And another NEW issue!!
Post by: WD8BXS on 22. April 2021, 20:14:00

What are the option bytes for the MCHF ?
The chip is STM32F437

Thank,
Chuck

Title: Re:And another NEW issue!!
Post by: WD8BXS on 22. April 2021, 22:08:27

I just tried 2 more new UI boards, same result with all 4.

There must be a way to reset the MCU and allow me to start over????

Thanks,
Chuck

Title: Re:And another NEW issue!!
Post by: WD8BXS on 23. April 2021, 11:24:18

i suppose I will order 4 mcu's since no one has any ideas!

Thanks ,
Chuck

Title: Re:And another NEW issue!!
Post by: DF8OE on 23. April 2021, 11:32:21

Sorry - no idea. :'(... I never have had changed option bytes (like reset vectors) for F4 - and I do not know if this is possible at all. You can do a complete erase (mass erase) - and I think this will remove all protection bits that are set. But thats all I can tell.

vy 73
Andreas

Title: Re:And another NEW issue!!
Post by: WD8BXS on 23. April 2021, 18:34:53

Thanks Andreas,

Yes, I did that.

Take care my friend,

Chuck

Title: Re:And another NEW issue!!
Post by: WD8BXS on 24. April 2021, 14:24:28

I just discovered that I am seeing 3v at pin 3 on the DFU USB port.

That should not be there


Chuck

Title: Re:And another NEW issue!!
Post by: WD8BXS on 29. April 2021, 19:43:45

Replaced the MCU and all is well.

Hard to believe 4 bad MCU's.

I still think that there must be a way to do a hard reset to the chip so it will be like new.

Chuck, 73


Diskussions- und Newsboard des DARC-Ortsverbandes I40 | Powered by YaBB SE
© 2001-2003, YaBB SE Dev Team. All Rights Reserved.