Stm32flash linux failed to init device

Arduino for STM32

Everything relating to using STM32 boards with the Arduino IDE

• Unanswered topics
• Active topics
• Search
• The team

Failed to init device STM32 using Arduino

Failed to init device STM32 using Arduino

Post by idir93 В» Sun Sep 10, 2017 3:15 pm

Hello,
This is my first time I use STM32, I have followed the instructions provided in this link http://www.oddwires.com/blog/using-a-ge . h-arduino/ but at the end I get this:
Failed to init device.
stm32flash 0.4

Using Parser : Raw BINARY
Interface serial_w32: 230400 8E1
What could be the reason?

Re: Failed to init device STM32 using Arduino

Post by terraduino В» Sun Sep 10, 2017 9:57 pm

I’ve the same error.

I found multiple discussions related to Linux ch34x driver issues. However, the error message was a different. Therefore, I think it is not related to a missing parity implementation.

Some system infos

Note, I can upload code to the BluePill with ArduinoIDE and PlatformIO using the serial adapter and DFU, respectively. I followed the wiki to burn bootloader (generic_boot20_pc13.bin) via a Windows machine and the same USB serial adapter that fails with Linux. Hence, wiring and USB serial adapter should be fine.

Would be great if someone has an idea. Couldn’t find a working solution.

Re: Failed to init device STM32 using Arduino

Post by RogerClark В» Sun Sep 10, 2017 10:18 pm

The internal serial bootloader in the F103 does not work well with all USB to Serial adaptors.

Also ST32Flash does not seem to work as well as STM’s own Windows EXE program.

You could try using different baud rates, but ultimately the F103 internal serial bootloader has issues which prevent it working with some combinations of hardware and software.

The only guaranteed way to upload or flash the bootloader is using a SWD programmer like STLink, or JLink or BlackMagic Probe etc

STLink clones only cost a few dollars and are widely available.

Re: Failed to init device STM32 using Arduino

Post by terraduino В» Tue Sep 12, 2017 12:30 am

Thanks @RogerClark for the info.
I agree, the STLink clones are cheap enough. However, I would prefer to have not another device sit on my desk. Moreover, I would be tempted to buy some STM8 to put the STLink clone to good use And, unfortunately, the WAF is already low here .

Источник

Device init failed #31

Comments

danielkucera commented Dec 16, 2017

I’m trying to make my st-link clone work. I flashed generic_boot20_pa9.bin , LED blinks at boot, I can read serial output from /dev/ttyACM0 but stm32flash says Failed to init device. Can you help please?

The text was updated successfully, but these errors were encountered:

GrantM11235 commented Dec 16, 2017 •

stm32flash is used to upload using the built-in serial bootloader. To upload using the STM32Duino USB bootloader, use maple_upload . (PlatformIO puts it in

stevstrong commented Dec 16, 2017 •

Once you flashed the bootloader, this will set the SWD pins to normal GPIO function, so that STLink cannot connect to the device using the STlink utility.
But you can still upload over USB and the just flashed Stm32duino bootloader.
Or upload over STLink if you press reset just before the IDE wants to upload.
If you want to use only STLink in the future for upload, then you have to first re-enable the SWD interface by adding the linker directive -DCONFIG_MAPLE_MINI_NO_DISABLE_DEBUG=1 to line 374 of the boards.txt.
Then upload the blinky sketch over USB.
Now you can use the STLink again.

danielkucera commented Dec 16, 2017

ok, so how do I use stm32duino uploader in platformio (or directly) ?

GrantM11235 commented Dec 16, 2017

Add upload_protocol = dfu to platformio.ini. There was also a PlatformIO bug that was fixed recently, so you may need to change platform = ststm32 to platform = https://github.com/platformio/platform-ststm32.git to use the latest pre-release version.

danielkucera commented Dec 16, 2017

it still doesn’t work:
platformio.ini

GrantM11235 commented Dec 16, 2017

Try board = bluepill_f103c8

danielkucera commented Dec 16, 2017

still, the same. and thank you for helping me.

danielkucera commented Dec 16, 2017

I successfully uploaded firmware like this:
sudo ./dfu-util/dfu-util -a 2 -D /home/danman/Projects/stm32-443rx/project/.pioenvs/genericSTM32F103C8/firmware.bin

When I plug-in my device it starts as 1eaf:0003 and after few seconds changes to 1eaf:0004 . When it is 0003, I can use dfu-util to list upload targets:

and also the upload works:

Now, how to make it work from platformio?

danielkucera commented Dec 16, 2017

My device is simply not resetting, even with usbreset utility:

GrantM11235 commented Dec 16, 2017

/.platformio/packages/tool-stm32duino/maple_upload /dev/ttyACM0 2 1EAF:0003

danielkucera commented Dec 16, 2017

upload-reset doesn’t work on my device:

even if I run it as sudo:

danielkucera commented Dec 16, 2017

even if it sometimes finishes successfully, it doesnt reset the device:

danielkucera commented Dec 16, 2017

For now, I’ve added following to maple_upload and I plug it off and in manually:

danielkucera commented Dec 16, 2017

It is very possible that my device doesn’t have pull-up resistor from USB D+ to VCC as described here:
https://github.com/rogerclarkmelbourne/STM32duino-bootloader/blob/master/README.md

GrantM11235 commented Dec 16, 2017

It looks like PlatformIO uses an outdated (unknown) version of the tools from https://github.com/rogerclarkmelbourne/Arduino_STM32. You could try copying the contents the appropriate tools folder to

/.platformio/packages/tool-stm32duino to see if that improves anything.

rogerclarkmelbourne commented Dec 17, 2017

This discussion seems like it migrated well outside the scope of it being a possible issue on the bootloader code and is something to do with Platformio.

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

SOLVED — Failed to Init Device to 1.4.12 update via pi-star #73

Comments

dhchenault commented Nov 20, 2018 •

Been running, no problems. Updated previously using the ssh shell in pi-star. Tried it tonight with same command and received a failed to init device error. Also, the temp rises quickly like the CPU is hung, but I didn’t look at the load status to confirm. After reboot, it shows back to 1.4.7 and operates normally. I tried multiple times to flash the firmware with the same technique with no luck.

Any ideas?
David

Here’s the text from the process:

$ sudo pistar-mmdvmhshatflash hs_hat
MMDVM_HS_Hat-v1.4.7 20180821 14.7456MHz ADF7021 FW by CA6JAU GitID #b14548e
Press any key to write the hs_hat firmware to this modem or Ctrl-C to quit.
Flashing your hs_hat modem to the latest version
—2018-11-20 01:01:45— http://github.com/juribeparada/MMDVM_HS/releases/download/v1
.4.12/install_fw_hshat.sh
Resolving github.com (github.com). 192.30.253.113, 192.30.253.112
Connecting to github.com (github.com)|192.30.253.113|:80. connected.
HTTP request sent, awaiting response. 301 Moved Permanently
Location: https://github.com/juribeparada/MMDVM_HS/releases/download/v1.4.12/install_
fw_hshat.sh [following]
—2018-11-20 01:01:46— https://github.com/juribeparada/MMDVM_HS/releases/download/v
1.4.12/install_fw_hshat.sh
Connecting to github.com (github.com)|192.30.253.113|:443. connected.
HTTP request sent, awaiting response. 302 Found
Location: https://github-production-release-asset-2e65be.s3.amazonaws.com/80589711/a3
81d300-e050-11e8-8ba3-5272f575399f?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=
AKIAIWNJYAX4CSVEH53A%2F20181120%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20181120T0
70146Z&X-Amz-Expires=300&X-Amz-Signature=76e5cd2cc70273f285fb24b38f333d7aaaad7c125da2
3cb87fd958368f126696&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition
=attachment%3B%20filename%3Dinstall_fw_hshat.sh&response-content-type=application%2Fo
ctet-stream [following]
—2018-11-20 01:01:46— https://github-production-release-asset-2e65be.s3.amazonaws.
com/80589711/a381d300-e050-11e8-8ba3-5272f575399f?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-
Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20181120%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-
Date=20181120T070146Z&X-Amz-Expires=300&X-Amz-Signature=76e5cd2cc70273f285fb24b38f333
d7aaaad7c125da23cb87fd958368f126696&X-Amz-SignedHeaders=host&actor_id=0&response-cont
ent-disposition=attachment%3B%20filename%3Dinstall_fw_hshat.sh&response-content-type=
application%2Foctet-stream
Resolving github-production-release-asset-2e65be.s3.amazonaws.com (github-production-
release-asset-2e65be.s3.amazonaws.com). 52.216.128.107
Connecting to github-production-release-asset-2e65be.s3.amazonaws.com (github-product
ion-release-asset-2e65be.s3.amazonaws.com)|52.216.128.107|:443. connected.
HTTP request sent, awaiting response. 200 OK
Length: 2908 (2.8K) [application/octet-stream]
Saving to: ‘/tmp/mmdvmhshatfirmware/flash.sh’

/tmp/mmdvmhshatfirmwa 100%[========================>] 2.84K —.-KB/s in 0.001s

2018-11-20 01:01:46 (3.16 MB/s) — ‘/tmp/mmdvmhshatfirmware/flash.sh’ saved [2908/2908
]

FINISHED —2018-11-20 01:01:46—
Total wall clock time: 1.9s
Downloaded: 1 files, 2.8K in 0.001s (3.16 MB/s)
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 609 0 609 0 0 1407 0 —:—:— —:—:— —:—:— 1409
100 48216 100 48216 0 0 53026 0 —:—:— —:—:— —:—:— 53026
Cloning into ‘STM32F10X_Lib’.
remote: Enumerating objects: 5, done.
remote: Counting objects: 100% (5/5), done.
remote: Compressing objects: 100% (5/5), done.
remote: Total 178 (delta 0), reused 3 (delta 0), pack-reused 173
Receiving objects: 100% (178/178), 3.27 MiB | 921.00 KiB/s, done.
Resolving deltas: 100% (60/60), done.
Checking connectivity. done.
Raspberry Pi 2 or Pi Zero W detected
stm32flash Arduino_STM32_0.9

Using Parser : Raw BINARY
Interface serial_posix: 57600 8E1
Failed to init device.

Flashing your hs_hat modem complete, press any key to reboot your Pi-Star System.
Session closed.

The text was updated successfully, but these errors were encountered:

Источник

stm32flash

Open source flash program for STM32 using the ST serial bootloader

Brought to you by: tormod

Milestone

Searches

#134 STM32L462 «Failed to init device» problem

Hello I’m having a problem with stm32flash returning «Failed to init device.» error when trying to flash my STM32L462 microcontroller through UART on my Linux Operating system.

These are the steps I’m going through when trying to flash the MCU:
First I run the script to put the MCU into bootloader mode

then I try to flash the MCU with stm32flash :

where I get the response:

Looking at the code of stm32flash I can see that the «Failed to init device» can happen inside stm32_send_init_seq function, when trying to read a byte from the port. The cause can be either:
timeout
not reading OK or NACK response

I also found the comment saying that putting -c flag prevents sending the init sequence. This is the output when trying to do that:

I’ve also tried changing the baud rate to 115200 and serial port mode to 8o1 (and the combination of the two, e.g. 57600 baud rate and 8o1 serial mode), but the problem persists.

Lastly I tried if I can flash the MCU with the Stm32CubeProgrammer and I can do that. However, when looking at verbose logging during the establishing the connection to the MCU I can see that the MCU times out on the response when the Stm32CubProgrammer sends the 0x7F byte the first time (and after sending the 0x7F the second time the MCU sends the proper response). I’m attaching the logs from that program.

What do you think? Do you have any idea of what I could try, because I’m slowly running out of ideas on how to solve this.

Источник

stm32flash

Open source flash program for STM32 using the ST serial bootloader

Brought to you by: tormod

Milestone

Searches

#81 failing communication via CH341 chipset on Linux

Hi ! I have try many rev of the code build it and test but never have good communication with
my stm32f103C8 . always these errors :

./stm32flash /dev/ttyUSB0
stm32flash 0.4

Interface serial_posix: 57600 8E1
Failed to read ACK byte
Unexpected reply from device on command 0x01

Please someone have a fix ?
I have try ST loader demonstrator tools and it work great with my chip and my usbserial adapter on the same port on a Win on Virtualbox so my hardware setup is good. the problem seem come from stm32flash. I have try to another computers same issues.

Discussion

This may occur if a terminal program or another application in the background is working on the same serial interface.
For diagnosing the problem, you can try to manually connect to the STM bootloader with a terminal program by typing a DEL character (0x7F). The expected answer would be an y character.

Anonymous

Hi i have ever test this with minicom and the stm32 reply me the good characters.

Anonymous

• Milestone: 1.0 —> none

Anonymous

I am using the STM32F103 series a lot, so I am surprised there are issues with it. Can you try a different baud rate, e.g. 115200? Last time somebody had similar trouble it was a bad ground connection, although I see you’re saying it works with other software. What kind of usb-serial adapter are you using?

Anonymous

For milestone yes i have seen that’s any 1.0 exist but i have try with ten revision to see if one works.. but any..

It’s a very curious problem.
I have ever try many baud rate. and i have retry many because you say me thats.. anyone work. when i test with the siemens demonstrator all baud rate work. My Usb serial is a CH340 chip.

Anonymous

I have read the source code to found a debug mode but none found ? So i have load it in eclipse to try to debug .
So when running in debug mode It’s appears that’s the first command send to stm32 was 0x01 . or that’s must be 0x7f ?? but i don’t know if i watch the good variable i don’t knowledge this source code.. so could you tell me what variable i must whatch and were i can found the breakpoint to well view where is the problem. thanks

Anonymous

(Don’t worry about the «milestone», it is just for planning purpose, when deciding something must be fixed before a given release.)

Thanks for debugging this! Actually I never tested a CH340 chip myself, maybe it needs some special treatment. You should see 0x7f being sent first. Try going through the stm32_send_init_seq() function with the debugger. To see everything sent to the port you can track serial_posix_write() and look at buf and nbyte, or even the write() call inside this function.

Another thing that could be tried is to run a Windows build of stm32flash in your virtual machine.

Anonymous

I try to watch what the serial_posix read from serial but don’t success?? Could you say me what var i must watch. I ‘ve try the «pos» one time i have the «0x79» or the .read in the port structure. but no good result.
If i watch the cmd var i see the 7f send. but for .read serial always 0x40 .

Anonymous

I have setting wireshark to dump the ttyUSB input output when running stm32flash.
So i See the 7F send and the 79 reply from stm32 so the usbserial work good when stm32flash use it. But stm32flash seams to do error when compute receive date.

Anonymous

I have test an ever build version of stm32flash on the same computer with virtual machine with win where st tools work .
So i am on the same usb port same ch341 chip on a win10 version running on exactly same computer and on windows that’s work .
So it’s a linux version problem.

Anonymous

The «command 0x01» in your error message is probably STM32_CMD_GVR in the code. It is the first command after sending 0x7F in stm32_send_init_seq(). Is it always here that it fails?

Can you please try, instead of the debugger, to trace it with strace like this:
strace -tt -T -e read,write ./stm32flash /dev/ttyUSB0

Anonymous

Maybe the ttyUSB echos all data sent to it, I once observed such an issue (unrelated to stm32flash) with an FTDI ttyUSB. It was fixed after setting the following parameters to stty:

stty 57600 cs8 parenb -parodd igncr -echo

Anonymous

I have strace the stm32flash:

10:04:59.337060 read(3, «\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\220\t\2\0\0\0\0\0». 832) = 832
10:04:59.337450 write(1, «stm32flash 0.4\n», 15stm32flash 0.4
) = 15
10:04:59.337485 write(1, «\n», 1
) = 1
10:04:59.337512 write(1, «http://stm32flash.googlecode.com». 35http://stm32flash.googlecode.com/

) = 35
10:04:59.357704 write(1, «Interface serial_posix: 57600 8E». 34Interface serial_posix: 57600 8E1
) = 34
10:04:59.357759 write(3, «\177», 1) = 1
10:04:59.357796 read(3, «y», 1) = 1
10:04:59.361753 write(3, «\1\376», 2) = 2
10:04:59.361859 read(3, «», 1) = 0
10:04:59.861846 write(2, «Failed to read ACK byte\n», 24Failed to read ACK byte
) = 24
10:04:59.862102 write(2, «Unexpected reply from device on «. 45Unexpected reply from device on command 0x01
) = 45
10:04:59.869805 write(1, «\n», 1
) = 1
10:04:59.870203 +++ exited with 1 +++

Anonymous

I have try to remove the hypothetic echo mode with :

stty -F /dev/ttyUSB1 57600 cs8 parenb -parodd igncr -echo

And retry stm32flash. and always same issue.

Thanks for the idea.

Anonymous

I finally understood that the message «Unexpected reply from device on command 0x01» does not mean that the unexpected reply was 0x01, but that the reply to the command 0x01 was unexpected.
The strace shows that there isn’t any answer to the 0x01 0xFE sequence, the read(3. ) returns 0.

Another idea:
Maybe the CH340 initialization takes some time, so the baud / parity settings are not active during the transmission of the first characters. Since the STM32 does autobauding and the first characters (0x7F, 0x79) look the same on the line with even parity or no parity (parity bit is 1, identical to stopbit), communication starts.
You may add an excessive waiting time after serial initialization to check if something changes.

If you have the oportunity, you may have a look at the transmitted characters on the serial line (logic analyzer like sigrok) to see what really goes wrong.

Источник