-
Notifications
You must be signed in to change notification settings - Fork 3k
Enter DFU mode with stm32F401 (bootloader Issue) #8523
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Just to be certain - you are using f401 with v163 (mbed 2 version), not Mbed OS 5.10.2 ? @ARMmbed/team-st-mcd Please review |
Yes @0xc0170, the version that works is mbed 2 (v163), and the version that doesn't work is mbed-os 5.10.2. Thank you for your quick reply. |
Can you compare R0 value before and now? What toolchain - using online compiler? I reviewed quickly recent changes , only change there was alignment for ARMCC change (affects RAM to be aligned to 8 byte). That should not have any affect to this issue.
Look at ST forum to find some help - missing driver for instance? |
I'm using eclipse with GCC_ARM compiler. In the online compiler the I'm trying to see how to read R0 in c++, when I know how to do it I'll post it here
This is not the problem, because as I said, with mbed 2 (v163) it works, and the PC takes the proper driver because the driver is installed. |
This code snippet from the mbed_application can help you: https://github.com/ARMmbed/mbed-os/blob/master/platform/mbed_application.c#L143 (using inline asm for ARMCC - the first one, later is for GCC and IAR).
OK, might be the board is in bad state and cant connect. |
I just tried this simple example with the same board (NUCLEO-F401RE), using mbed 2 (v163), and then mbed-os 5.10.2. Both with the online compiler.
With the mbed 2 (v163) it works perfect (PC recognized it as STM Device in DFU Mode), but with mbed-os 5.10.2 doesn't work. It says Unknown USB Device (Device Descriptor Request Failed) |
Internal Jira reference: https://jira.arm.com/browse/MBOCUSTRIA-107 |
is the ST team (@ARMmbed/team-st-mcd) reviewing or aware? |
@devHAA Right now, it seems like this is waiting on @ARMmbed/team-st-mcd to take a look. |
Maybe you can check intermediate version ? |
Ok, after some test, still no lucky: v5.10.2 -> failed |
I would like to know what happened between 5.9.6 and 5.10.2 ? |
Just checked v5.9.6 but is not working for me neither, is it working for you? |
Dear all, |
Hi @devHAA and all, could you test this:
Note: edited to be more mbed compliant. Thanks @LMESTM 😉 |
@neurodigitaltechnologies |
@adbridge Could we close this issue ? |
Uh oh!
There was an error while loading. Please reload this page.
Description
Hello,
I'm having troubles with mbed-os 5. With the previous version of mbed (v163) it worked perfectly. With the following piece of assembler code, the micro (stm32F401) enters DFU mode. But with the newest version of mbed-os 5 (5.10.2) doesn't work.
I've been doing some tests and I think that the problem is in the last line
__asm ("BX R0");
, when it should jump to the Bootloader. If I try to connect the device on the PC it says "descriptor request error".Any ideas what may be happening, Thank you.
Issue request type
[ ] Question
[ ] Enhancement
[x] Bug
The text was updated successfully, but these errors were encountered: