On 25-06-2015 14:33, Gedare Bloom wrote:
Ask what other folks using the RPi are doing.
I do not know if anyone using the Pi with RTEMS currently has a debugger
working. Last year Alan posted in his blog [1] a configuration using a
FT2232H mini module and OpenOCD that connects to the Pi through JTAG,
however although we get a JTAG connection, any code that is sent to the
Pi fails to be tranferred. I have checked his wiring, and pinpointed one
of the possible reasons for the fail to be in the JTAG setup program
(the JTAG interface has to be configured on GPIO, but also pull
resistors have to be disabled, as well as possibly some other details
that are vaguely referred on the Internet). Another point of possible
failure may be in the configurations used with OpenOCD (which are
adapted from another ftdi device), or that something is missing in the
JTAG wiring. I checked this again before GSOC started, but without much
progress.
[1] -
http://alanstechnotes.blogspot.pt/2014/05/a-low-cost-jtag-debugger-for-raspberry.html
On Thu, Jun 25, 2015 at 9:24 AM, Yurii Shevtsov <unge...@gmail.com> wrote:
How to set a break point? Is there any other way of debugging except
printfs and tracing?
2015-06-25 16:00 GMT+03:00 Sebastian Huber <sebastian.hu...@embedded-brains.de>:
I would set a break point to nexus_probe(). In this loop
SET_FOREACH(nd, nexus) {
device_add_child(dev, nd->name, nd->unit);
}
your device must get added. I would also set break points to the probe and
attach functions of your device.
On 25/06/15 14:50, Yurii Shevtsov wrote:
This is ping message, with small update: the problem is not on the
linking stage, driver is linked to testsuite (checked with objdump)
2015-06-21 17:57 GMT+03:00 Yurii Shevtsov <unge...@gmail.com>:
Hello)
Now I have apps from libbsd testsuite running. But DWC OTG driver doesn't
loads.
I added this lines to init01/test_main.c:
+SYSINIT_NEED_USB_CORE;
+SYSINIT_DRIVER_REFERENCE(bcm283x_dwcotg, nexus);
(I know it's bad hardcode)
If I run it. I get only this:
nexus0: <RTEMS Nexus device>
devctl: +nexus0 at on root0
devctl: !system=IFNET subsystem=lo0 type=ATTACH
Of course, I modified rtemsbsd/include/machine/rtems-bsd-sysinit.h and
rtemsbsd/include/bsp/nexus-devices.h (took vlues from working DTS) and
did other nexus-related changes to drivers. You can find changes in my
repo https://github.com/gtament/rtems-libbsd/
So I need some kind of code review, please.
P.S. All testsuites (netshell01, usb01) with shell hangs without any
output.
Thanks in advance!
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.hu...@embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
