Hi All,
Congratulations on getting accepted as a mentoring organization.
My name is Ragunath. I am currently pursuing my master's degree in
computer science from IIT Kharagpur, India.
My area of interests are operating systems and embedded systems
development. I am interested in working with
RTEM
Hi All,
I was exploring the beagle code base to find a task to get hands on
experience with RTEMS internals. I found that "Real time Clock (RTC)" support is
missing for beaglebone. I made the effort to add the driver for the device.
Included the patch for the driver. RTEMS already have a RTC frame
Hi,
I would like to know what is the status of running lwIP on beaglebone
black on RTEMS. I understand that there was some considerable amount
of work already done on running lwIP on BBB. It would be really
helpful if I can get the details on what has already been done and
what are the remainin
Hi,
What is the procedure to link a network driver to the application in
rtems libbsd port? The drivers are compiled and available in the
libbsd archive. I dont know how to link the driver to the application.
I followed the RTEMS NETWORKING supplement document and tried defining
the following str
h and the tests.
>
>
> On 06/04/15 21:12, ragu nath wrote:
>>
>> Hi,
>>
>> What is the procedure to link a network driver to the application in
>> rtems libbsd port? The drivers are compiled and available in the
>> libbsd archive. I dont know how to
On Wed, Apr 1, 2015 at 7:48 PM, Joel Sherrill
> wrote:
>> I noticed this wasn't merged.
>>
>> Ben.. ?
>>
>> some comments interspersed.
>>
>> On 3/10/2015 4:21 PM, ragu nath wrote:
>>> Hi All,
>>>
>>> I was exploring the b
Hi All,
I have attached the RTC patch for BBB. I have addressed the comments
given for my earlier submission.
I am having problems with sending patch using git send-email. I
understand this is the preferred way but I not able to send patch
using git send-email. I am behind a http proxy and git wa
Hi All,
My name is ragunath. I am selected for Google Summer of Code 2015 with
RTEMS. I will be working on improving Beagle BSP.
I am in the process of porting ethernet driver for Beaglebone black
from FreeBSD to rtems-libbsd. I would like to know what are the
necessary changes we need to make t
e of minutes with the
> use some hacks to get the FDT provided parameters.
>
> To get an idea how a driver is ported see git log and look at all commits
> containing "if_cgem" in the subject.
>
> Please help to improve the documentation (libbsd.txt) while you work on this
bsp_interrupt_vector_enable in
dispatch function. There is no hang and packets are received.
What can be the correct fix for the issue as there are other
interrupts that are not processed in this way?
Thanks,
Ragunath
On Fri, May 15, 2015 at 12:39 PM, ragu nath wrote:
> Thank you. I will check the git log
currently pending interrupt.
>
>
> On 28/05/15 13:14, ragu nath wrote:
>>
>> Hi Ben,
>>
>> I found the reason for system hang in BBB after link goes up. It is
>> caused by enabling the interrupt before it is processed creating a
>> continuous flow of inter
Hi All,
I am porting ethernet driver for Beaglebone black from FreeBSD. I
would like to know how to execute the following test cases. I would
like to know how to execute the test? what is the expected result?
any setup that needs to be done etc.
1. arphole
2. foobarclient
3. foobarserver
4. medi
Hi Gedare,
I will send them separately.
Thanks,
Ragunath
On Thu, Jun 25, 2015 at 10:29 PM, Gedare Bloom wrote:
> Can you split the commits so that the import from BSD is separate from
> your modifications to it?
>
> On Thu, Jun 25, 2015 at 12:18 PM, ragunath wrote:
>> This patch includes cha
Hi Marcos,
I am working on porting ethernet driver for Beaglebone black from
FreeBSD to rtems-libbsd as part of GSOC 2015. I ported the driver and
got it working.
But there was one issue I faced, similar to the one you mentioned in
our earlier correspondence (regarding lwIP). You mentioned that t
me to the task, so when I reached that stage I just disabled the
> cache.
> I will try to give some time to that to see if i can help you, and of
> course, let me know if you find something.
> Sorry again
>
> On Mon, Jun 29, 2015 at 3:16 PM, ragu nath wrote:
>
>> Hi Marco
Hi Sebatian,
I will try both your suggestions and let you know on the progress.
Thanks,
Ragunath
On Mon, Jun 29, 2015 at 12:49 PM, Sebastian Huber
wrote:
>
>
> On 25/06/15 18:20, ragunath wrote:
>>
>> This patch has two changes that are needed for networking to work in BBB.
>> We disable cache
he lines.
>> FWIW, in a life ago, i got a problem with an eth driver where the
>> descriptors ring was not properly sized (ie no modulus cache line).
>> El 29/6/2015 17:23, "ragu nath" escribió:
>>
>>> Thanks Marcos. I will let you know if there
Hi Sebastian,
I read about rtems_cache_coherent_allocate(). I understand first we
need to add an area to use this.
I added rtems_cache_coherent_add_area(bsp_nocache_heap_begin,(uintptr_t)
bsp_nocache_heap_size); in bsp start.
Is that right? I do not know how bsp_nocache_heap_begin &
bsp_nocache_he
Hi Sebastian,
If we want to use cache flush/invalidate calls, what is the general
method one has to follow?
I saw the if_cgem driver, but it is somewhat different from cpsw
driver. What are all the places which may need these calls?
Thanks,
Ragunath
On Fri, Jul 10, 2015 at 4:29 AM, ragu nath
Hi All,
I have sent the patches for building lwIP from RSB. First patch
contains changes for RTEMS Resource Builder. The second patch is RTEMS
specific changes that will be applied to lwIP base.This patch contains
only lwIP sources. I will be sending another patch for the driver to
be used with l
M, Joel Sherrill
> wrote:
>>
>>
>> On 8/9/2015 4:57 AM, ragu nath wrote:
>>>
>>> Hi All,
>>>
>>> I have sent the patches for building lwIP from RSB. First patch
>>> contains changes for RTEMS Resource Builder. The second patch is RTEMS
&
Hi Yurii,
For RPi USB support, can you pls try including
"default-network-init.h" in the application (I tested with netshell01)
instead of "default-init.h" and see if it works.
If we use default-init.h, nexus.content is empty and device is not probed.
Thanks,
Ragunath
On Mon, Aug 10, 2015 at 7:
Hi All,
I have written a blog explaining how to use lwIP with RTEMS. The BSP
supported is BeagleBone Black(BBB). It basically has four steps
1. Build BBB BSP with cache disabled.
2. Build lwIP library. We can build it using RSB
3. Build driver library using RSB
4. Build the application
All the
Hi Thomas,
There is no need to manually edit the makefile. You can add whatever
files you need from freebsd to libbsd.py file.
I can see, there is already a dev_usb_input module. It is currently
disabled. You can just enable it & add additional files to it if you
need.
Then you run the freebsd-to
Hi Marcos,
Great news! I did not find any solution to the issue. I have a REV C board
from element14. Is this the same board you are using? In my board I saw
the issue.
Does this have anything to do with the patch you submitted [PATCH]
Beaglebone: fix missing clobber in inline assembly.
https:/
>Please tell me so I can check if is the revision, or perhaps is
>>>> >something else in u-boot initialization.
>>>> >
>>>> >
>>>> >For the question Joel asked there is a way:
>>>> >
>>>> >
>>>> h
;
>>>>> >How did you see the revision number? if you are
>>>>> using u-boot you can
>>>>> >pause the start and write printenv and enter to see
>>>>> that:
>>>>> &
On Mon, Sep 21, 2015 at 5:44 PM, ragu nath wrote:
>
>> Hi Marcos,
>>
>> I upgraded the image. I cannot boot the RTEMS image using tftp. Seems
>> there was a bug in u-boot & fixed later. It propagated to BBB image. I am
>> having troube booting with SD card. I
Hi,
lwIP can be built using RTEMS Source builder now. We have RTEMS +
lwIP OS glue(cc.h & sys_arch.c etc) . But it uses posix lib functions
instead of RTEMS native library.
https://github.com/ragunath3252/lwip-nodrv . It's tested and working
but not fully optimized.
https://lists.rtems.org/pip
29 matches
Mail list logo
