Changes between Version 59 and Version 60 of GSoC/2016


Ignore:
Timestamp:
Jun 15, 2016, 1:54:58 PM (3 years ago)
Author:
Deval Shah
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GSoC/2016

    v59 v60  
    8383== Deval Shah ==
    8484* May 25: My first task is to add USB root hub support. For that, I need USB DWC OTG drivers and hardware specific drivers (for bcm283x) in the right place. USB DWC OTG drivers are already there in the codebase. To continue with Yurii's last year's work, I cherry picked his commits for USB roothub drivers and merged it to the current version of rtems-libbsd. Default testsuits which are related to networking are having compilation/linking errors. Later I realised that the driver (bcm283x) itself is not compiling. So I will now read the documentation regarding adding drivers in rtems-libbsd. That should help me to verify the code or if required write that from scratch. I should be able to add the hardware specific driver before the next status update.
    85 * June 1: I have resolved previous errors in building the drivers. So now the bcm283x_dwcotg driver compiles along with testsuits. Now I tried running the testsuits, it just shows "nexus0: <RTEMS Nexus device>"  and hangs. Also, if I plug-in any usb device to Raspberry pi they are not getting powered on. I asked Yurii, he worked on the same problem last year, but he doesnt remember much about the errors or issues, however I have taken care whatever he has mentioned in his blog. RPI cant work with qemu according to [https://lists.rtems.org/pipermail/devel/2016-May/015101.html this] issue. So only option left is JTAG debugger. Which I have ordered but that would take about a week to get shipped to my place.
    86 * June 8:
     85* June 1: I have resolved previous errors in building the drivers. So now the bcm283x_dwcotg driver compiles along with testsuits. Now I tried running the testsuits, it just shows "nexus0: <RTEMS Nexus device>"  and hangs. Also, if I plug-in any usb device to Raspberry pi they are not getting powered on. I asked Yurii, he worked on the same problem last year, but he doesnt remember much about the errors or issues, however I have taken care whatever he has mentioned in his blog. RPI can't work with qemu according to [https://lists.rtems.org/pipermail/devel/2016-May/015101.html this] issue. So only option left is JTAG debugger. Which I have ordered but that would take about a week to get shipped to my place.
     86* June 8: As per the previous update I am stuck at the point where the testsuits are compiling but not running on the raspberry pi hardware. I had a few options to proceed with JTAG debugger and QEMU. JTAG debugger which I had ordered has come today so I will start working on that asap. I built the testsuits for arm/realview-pbx-qemu and ran them on qemu. I am trying to debug the issue using other BSP which supports QEMU.
    8787
    8888== Wonjun Hwang ==