-
Notifications
You must be signed in to change notification settings - Fork 171
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
Reading memory results in exception #16
Comments
Ok, I think I managed to get it correct. Maybe it is the fault of python 2.7? |
Interesting bug, thanks for reporting it. Are you getting back the correct data after making your proposed fix? It sounds to me that |
Hi! Sorry for slow response. |
The script should work with both 2.7 and 3.4. |
It is Contiki build, I simply am not allowed to share the specific binaries :( |
I understand, can you share the command you used to try to read the memory? Could have something to do with the length and location. |
Sorry all gone by now. I will try to reproduce it when I have time, I will just try out and experiment with the script. Could you please hold on for now? |
No problem, I'll close this for now, feel free to comment when you come across the problem again. |
When trying to read memory I get "ERROR: ord() expected string of length 1, but int found".
When removing the mdebug at the read section, I get similar error when it tries to write data to file - "ERROR: sequence item 0: expected string, int found".
The text was updated successfully, but these errors were encountered: