What kind of debugging info do you mean? What else can I get except serial output? Can I make it verbose?
2015-06-25 16:00 GMT+03:00 Gedare Bloom <ged...@gwu.edu>: > Can you add more debugging info? > > I glanced at your code, some comments, make sure you follow the > recommendations in libbsd.txt about modifying code taken from freebsd. > You also might find it more convenient to work on a branch instead of > a master, and to avoid merge commits. > > Gedare > > On Thu, Jun 25, 2015 at 8:50 AM, Yurii Shevtsov <unge...@gmail.com> 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