[lowrisc-dev] Re: What are you working on this week?
mahmoud.elmohr at gmail.com
Mon Jun 20 17:09:53 BST 2016
For my project (Porting Arduino Libraries to PULPino) within GSoCI have
ported GPIO, interrupts and this week I have ported Timer functions.
Currently I'm working on UART libraries porting and hope to finish the
Arduino core libraries next week.
Hope everyone doing well too.
2016-06-20 16:36 GMT+02:00 Jeffrey Rogers <jeffreyrogers at college.harvard.edu
> Hi everyone,
> As part of GSoC I'm continuing to work on porting the xv6 teaching
> operating system to RISC-V. Last week I finished up reorganizing the
> codebase to separate out the machine dependent and machine independent code
> and used Jonathan Neuschäfer's UART patch to spike to get output working in
> my kernel. This week I'll continue bringing up the kernel and adding more
> functionality into it, starting with trying to get a console up and running.
> On 6/20/16 08:40, Alex Bradbury wrote:
>> On 13 June 2016 at 15:41, Alex Bradbury <asb at asbradbury.org> wrote:
>>> I've seen this kind of weekly update thread work well in other
>>> communities (notably lobste.rs  and the rust community ) so
>>> thought it would be worth trialling it on lowrisc-dev, particularly
>>> with all the activity that is going on around GSoC.
>>> Use this thread to discuss what you have done recently and are working
>>> on this week with a vague relation to lowRISC, RISC-V, open-source
>>> hardware etc. Please be descriptive and don’t hesitate to champion
>>> your accomplishments or ask for help, advice or other guidance.
>>> : https://lobste.rs/s/nfh5nd/what_are_you_working_on_this_week
>> It's a new week, and there seemed to be some positive feedback so lets
>> give "what are you working on this week" another go. I'll keep it
>> under the same thread for now. A few people dropped me an email to say
>> they'd wanted to take part but the week was almost over by the time
>> they got round to it. Well, here's another chance :)
>> Last week, I spent some time getting up to speed on Linux kernel
>> hacking. I believe I've got a test kernel that should properly
>> initialise the Xilinx Quad SPI device, but there is an outstanding bug
>> with program loading for the next major lowRISC code release that
>> needs to be resolved before I can properly test that. For now,
>> printk() is my debugger. Debugging the program loading issue is the
>> main blocker now I believe.
>> We have a group of four local interns starting here at the lab next
>> week so there has been some miscellaneous work in getting things set
>> up for them, and there's still some more to do - setting up tool
>> install on shared filespace etc. I hope later in the summer they'll be
>> introducing themselves on the list and once they start having results,
>> blogging about what they're working on. One of the products of the
>> internship should be more documentation about how to design, implement
>> and test custom accelerators (including the necessary hardware and
>> software support).
>> That's my bit, now your turn - what are you working on this week?
>> See also recent updates from some of our GSoC students:
More information about the lowrisc-dev