Page 1 of 1

UMDK debugging features

Posted: Thu Nov 06, 2014 5:50 am
by Dr. MefistO
Please, tell me about GDB-debugging feature: how it will be implemented?

It will be possible to connect my IDA to your UMDK, and debug my ROM? What features will be accessible at all for the romhacker?

Re: UMDK debugging features

Posted: Mon Nov 10, 2014 7:09 pm
by MintyTheCat
Dr. MefistO wrote:Please, tell me about GDB-debugging feature: how it will be implemented?

It will be possible to connect my IDA to your UMDK, and debug my ROM? What features will be accessible at all for the romhacker?
Hello,

Prophet36/Chris McClelland made some videos to show some of the features of UMDK.
Have a look at this:

https://www.youtube.com/watch?v=dLoudQc8L08

I am hoping that many of your questions will be answered by watching the video and having a look at UMDK's GitHub Repository. However, feel free to ask questions that you may still have.

Cheers,

Minty.

Posted: Tue Nov 11, 2014 9:12 am
by Dr. MefistO
I already saw that video. But it has no answers for my questions.

What I want:
IDA has such feature as connecting to GDB server and debugging with it.

Ok, I think all answers will be answered after I will get the device)

Posted: Tue Nov 11, 2014 11:54 am
by MintyTheCat
Dr. MefistO wrote:I already saw that video. But it has no answers for my questions.

What I want:
IDA has such feature as connecting to GDB server and debugging with it.

Ok, I think all answers will be answered after I will get the device)
If you read you will find that UMDK implements debugging through GDB using GDB's remote-debugging protocol - that is stated in the video and indeed given in the project's GitHub Repo.

Chris McClelland does indeed demonstrate that in operation in that video linked through UMDK's GDB-Bridge, GDB and DDD running on a Linux host.

There is also the Trace functionality.

The combination of tracing, single-step debug, register/memory peeking and poking, etc would constitute the facilities of use to Developers and Hackers alike.

UMDK is an on-going project and what will follow will be other tools to interpret the trace-logs amongst other things.

Does that answer your queries?

Posted: Tue Nov 11, 2014 12:23 pm
by Dr. MefistO
I think, it does, but not completely)
Because of my OS is Windows, and I have no ability to test UMDK yet, I just should wait for the device to test it. And there is no answer about IDA.

Posted: Tue Nov 11, 2014 1:10 pm
by MintyTheCat
Dr. MefistO wrote:I think, it does, but not completely)
Because of my OS is Windows, and I have no ability to test UMDK yet, I just should wait for the device to test it. And there is no answer about IDA.
I do not know anything about IDA - you will have to ask someone else.

Yes, you WILL need a Linux machine to use UMDK.

Posted: Tue Nov 11, 2014 1:27 pm
by Dr. MefistO
I think, Linux is not a problem for me.)

Posted: Tue Nov 11, 2014 1:34 pm
by MintyTheCat
Dr. MefistO wrote:I think, Linux is not a problem for me.)
Good man!

Posted: Fri Dec 26, 2014 3:20 pm
by prophet36
I did write a detailed account of how the GDB debugging works on the project homepags at Hackaday.io.

On the question of Windows, it is certainly possible to get UMDK working on Windows with minimal porting effort. The UMDK host-side software uses FPGALink for much of its work, for which Windows is a supported platform. I have a work-in-progress port if anyone wants to take a look. It should be a straightforward job for anyone familiar with coding in C on Windows.