Updated on 5/18/2015: See this new post that has been updated for a Debian Jessie host, the latest BeagleBone Black sources and the latest stable eclipse packages.
I'm using Robert Nelson's debian wiki and Linaro and help from a few other sites (links are in the pdf).
Here is a google drive link to the shared pdf:
https://drive.google.com/file/d/0B5EnqQWuojyCb0J3bDFLNzhMc2M/edit?usp=sharing
Update from Charles Hamilton's comment:
"on page 25 of the pdf, you have the BBB address as 192.168.2.7, and it should be 192.168.7.2."
Here is the end result showing the bbb_hellow_world.c debug session.
4 comments:
Phenomenal, Aaron!
After much hair loss and nearly throwing in the towel while trying some of the other guides for Eclipse/BBB remote debugging, yours wins the prize for clarity and accuracy.
One small error to fix: on page 25 of the pdf, you have the BBB address as 192.168.2.7, and it should be 192.168.7.2.
Well done, and many, many thanks.
Charles
New York, NY
I have eclipse running and gdb, has anyone successfully debugged the PRU in this environment? My host machine is 64bit Debian Wheezy.
Bob Bailey>has anyone successfully debugged the PRU in this environment?
What type of debugging? I think PRU debugging is very limited. Here are some PRU debug tips from TI
http://processors.wiki.ti.com/index.php/PRU_Debugging
I wrote PRU code for the OMAP L138 TI code composer studio, I used an XDS100v2 JTAG emulator for programming but I don't think it will step through PRU code. I used a logic analyzer to look at output pins so I could get the timing correct for my code, I was reading an absolute encoder.
Post a Comment