-
Notifications
You must be signed in to change notification settings - Fork 41
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
Support for STM32 F767ZI #4
Conversation
Are you saying the LEDs cannot be turned on after calling The next step would be to add |
So, I have checked that all steps from The problem is with Do you have any ideas how can I check why this function is not called? |
We are getting closer! It's Can you send me your ELF file. It should be in |
Thanks for help! I found out that In meantime, this is my |
Are you building Baremetal_Example.elf in Debug or Release build? I was trying to disassemble it to check the code flow but I could not get the symbols. |
My mistake. Now I have built Baremetal_Example with Debug flag: link I am using This is the full output of building process:
|
I do not know if I have done anything wrong but I can get the list of symbols from the ELF. Both ELF files you gave have the same size. Maybe send me the disassembly to make it faster. To disassemble your ELF file: |
Sure, here is the link to the disassembled file: link |
Hmm, I had the same output. If it was a debug build I would expect to see symbols and C code as part of the disassembly. |
Yes, I got |
I am not sure why the disassembly code is not how it should be. Anyway, let's try something else for now.
And replace it by:
And try again... |
I have tried, but the result is the same (I think). I have uploaded bin file to nucleo board and result is the same. Here's the disassembled file: link |
Can you send me the exact command line you are typing (and ideally the same source code your are using). |
This is the command that I use: This is a patch file that reflects all changes I have made: patch |
Are you building Baremetal_Example.elf in Debug or Release build? I was On 27 October 2016 at 14:08, Lukasz Sergiusz Michalik <
|
Looks like your comment is a repeat of previous comments. Was it wrongly send? I don't know if you wanted to add something else :) |
Sorry, I tried to reply directly from the email and not from the github interface. I noticed there was a lag (the message did not appear in the github discussion). So I am guessing it is the email I sent 2 hours ago. I will try to build the code later (probably tonight) and see if I can notice something. |
My hack was not fully correct, it should have been:
I do not have I have not seen anything suspicious in my disassembly file.
The fact you cannot produce a clear disassembly file worry me a bit. Maybe your I have attached my built files |
I have flashed your build to the device but the problem still remains.
I got a strange serial output - but just once (I run this code in the endless loop): I think the problem with a disassembly in my case is a MacOS which might be missing proper debug flags in kernel config. I will try with a linux virtual machine tomorrow to confirm this case. |
Ensure you do not have Hardware control flow on your serial terminal. The debug flag are nothing to do with the kernel config but with the cross-compilation toolchain. |
I am using screen to get serial data. It works well with STM32 L467RG so I assume that it should be the same with F767ZI. Now I am preparing linux. I will let you know if I have found something. You are right with the debug flag - I was thinking about something else, sorry. |
By the way - are you eager to communicate in more flexible way? It takes some time to reply here. |
I have compared a disassembled files for F7xx and L4xx but I didn't find anything interesting. Maybe I just don't know what I am looking for. I have verified if everything is fine with my F767ZI board through mbed online compiler and I got a correct serial output from there. Do you have any other ideas what I should be looking for? |
It is a really old discontinued PR. |
I don't have a HW debugger, unfortunately. I can get LED2 on, but nothing more. I have even tried to turn on/off LED2 within a few iterations but without success.
So, LED works, but nothing more. I can turn on and off three LEDs available on board but if I use "puts" or "printf" function then nothing more works.
I have squashed all commits into, reverted changes to /CMakeLists.txt and done other suggestions.