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.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For some reason I don't know yet, the builds produced by GCC do not work.
They compile fine and a quick inspection of the generated file shows no obvious problems and yet when one tries to use it the module gets bricked and a hard reset is required (which makes trial and error debugging quite a challenge).
However, the problem is definitely not with objcopy since when used with the elf generated using armcc it generates exactly the same result as fromelf (md5sum match).
So there must be something wrong with the generated code.
Can't validate linking since the object files generated by armcc don't work with normal ld.
The text was updated successfully, but these errors were encountered:
The module no more crashes, but uart only sends garbage for some reason. The same code compiled using armcc works fine. However I can't see any obvious differences in the generated asm.
For some reason I don't know yet, the builds produced by GCC do not work.
They compile fine and a quick inspection of the generated file shows no obvious problems and yet when one tries to use it the module gets bricked and a hard reset is required (which makes trial and error debugging quite a challenge).
However, the problem is definitely not with objcopy since when used with the elf generated using armcc it generates exactly the same result as fromelf (md5sum match).
So there must be something wrong with the generated code.
Can't validate linking since the object files generated by armcc don't work with normal ld.
The text was updated successfully, but these errors were encountered: