-
Notifications
You must be signed in to change notification settings - Fork 3k
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
make_armc5 exporter does not support NUCLEO_F767ZI, NUCLEO_F401RE and DISCO_L476VG #5145
Comments
@soramame21 It looks like you encountered a windows "I can't tell the difference between |
BTW, this becomes a problem, because the Arm assebler, |
@soramame21 .. can you check if #5149 helps ? please confirm..thanks! |
Hey @ashok-rao. Thanks for mentioning that issue. It should have worked, but something is going awry with @soramame21's setup here. We have discussed what that patch brings to the table already, and it did not seem to work. |
@ashok-rao, @theotherjimmy, cc @MarceloSalazar Thanks for your comments. I had verified that the file is "irq_cm4f.S" although windows treats it as the same as "irq_cm4f.s".
I attached the file at here. |
PR #5149 will not help with any code issues, as it is purely documentation. I'm not sure why you attached the file. The problem is that make is treating the file as if it were named |
@theotherjimmy I'll try to remove mbed-os and deploy it. |
@soramame21 Turns out Arm Compiler 5's behavior on assembly files is platform dependent! See the |
That explains why I can't reproduce this, ever. I'm generally only using UNIX-like systems. |
I am encountering this issue with a KW24D, see log attached Host OS: Windows 10 @theotherjimmy I can confirm the name of the file in my fs is irq_cm4f.S. I did try to delete the mbed-os folder as suggested and run |
@dhwalters423 yeah, I have a workaround in #5166 |
Description
Bug
Target
NUCLEO_F767ZI, NUCLEO_F401RE and DISCO_L476VG|??
Toolchain:
ARMC5
Toolchain version:
MDK_ARM Professional Ver. : 5.22
C Compiler: v5.06 update 4(build 422)
mbed-cli version:
1.2.0
mbed-os sha:
mbed-os-example-fat-filesystem (08607866ff3f09b75e429ac0432587478d5e1fc3)
mbed-os (6e08748)
Expected behavior
Make can pass to generate a binary executable without error.
Actual behavior
Make get failed. please check the attached log.
Steps to reproduce
The text was updated successfully, but these errors were encountered: