Re: sparc-erc32 testsuites failures

I have updated the doc to use erc32-sis, and attached the patch file in this mail. Can someone review it. On Mon, Nov 18, 2019 at 12:07 PM Niteesh wrote: > I know this, but the docs are not updated so should I send a pull request? > > > On Mon, Nov 18, 2019 at 12:06 PM Vaibhav Gu

Re: [PATCH] user/start/bsp-test.rst: Changed bsp to erc32-sis.

I am new to this, so can you please elaborate on the steps. On Tue, Nov 19, 2019 at 10:16 PM Gedare Bloom wrote: > Hi Niteesh, > > Can you please provide a patch with your name on the authorship for > tracking copyright purpose? > > On Mon, Nov 18, 2019, 2:29 AM wrote: >

Re: [PATCH] user/start/bsp-test.rst: Changed bsp to erc32-sis.

I actually google about the authorship stuff, do you want me to add the --author command to the commit? On Tue, Nov 19, 2019 at 10:55 PM Niteesh wrote: > I am new to this, so can you please elaborate on the steps. > > On Tue, Nov 19, 2019 at 10:16 PM Gedare Bloom > wrote: >

Re: [PATCH] user/start/bsp-test.rst: Changed bsp to erc32-sis.

> > It's seems that there are many places where the doc has to be updated > about the erc32-sis stuff, so shall I change all of them and send a > commit? ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Interested in BSP's (No idea where to start?)

Hii, everyone I am interested in contributing to RTEMS, specifically to the arm based BSP's. I am a sophomore in electronics and communication engineering interested in operating systems, and systems programming. I have written small drivers and libraries for Arduino, bare metal avr chips to interf

Re: Interested in BSP's (No idea where to start?)

google: 1) Peripheral base address is now moved to 0x7E00 2) There's a mention of ARM's GIC400 @ 0x40041000 but probably is only the distributor since the old CPU interface is still there @ 0x4000 On Tue, Nov 26, 2019 at 7:19 PM Joel Sherrill wrote: > > > On Tue, Nov 26, 2

raspberrypi BSP current status

I am interested in contributing to the raspberry pi BSP. As of now RTEMS only has support for RPi1 and RPi2, but It seems that most of the code for RPi2 should work unmodified for RPi3 and RPi4, I am sure about the peripherals since the base address of the registers haven't changed in the new ones.

Re: raspberrypi BSP current status

On Sat, Nov 30, 2019 at 3:03 AM Christian Mauderer wrote: > On 29/11/2019 21:12, Niteesh wrote: > > I am interested in contributing to the raspberry pi BSP. As of now RTEMS > > only has support for RPi1 and RPi2, but It seems that most of the code > > for RPi2 should work un

raspberry pi simulation

I want to simulate old raspberry pi 1 and 2 using qemu. * qemu-system-arm -kernel hello.exe -cpu cortex-a7 -M raspi2 -m 512 -no-reboot -serial stdio* I use the above command to run the examples, and it does run, but not always sometimes I get this weird output's where my whole screen gets filled

Problem running RTEMS on raspberrypi3

I am trying to get RTEMS examples running on the RPI3, the RPI3 is similar to RPI2 so the examples built for RPI2 should technically run on the RPi3.But they don't :(, I am really sure of what is causing the problem. I followed the steps from http://alanstechnotes.blogspot.com/2013/03/running-your-

Re: Problem running RTEMS on raspberrypi3

On Sun, Dec 15, 2019 at 10:15 PM Christian Mauderer wrote: > Hello Niteesh, > > On 15/12/2019 09:05, Niteesh wrote: > > I am trying to get RTEMS examples running on the RPI3, the RPI3 is > > similar to RPI2 so the examples built for RPI2 should technically run on > &

Re: Problem running RTEMS on raspberrypi3

On Mon, Dec 16, 2019 at 12:53 AM Christian Mauderer wrote: > On 15/12/2019 19:46, Niteesh wrote: > > > > > > On Sun, Dec 15, 2019 at 10:15 PM Christian Mauderer > <mailto:l...@c-mauderer.de>> wrote: > > > > Hello Niteesh, > > > >

Re: Problem running RTEMS on raspberrypi3

On Mon, Dec 16, 2019 at 2:36 AM Christian Mauderer wrote: > > > On 15/12/2019 21:29, Niteesh wrote: > > > > > > On Mon, Dec 16, 2019 at 12:53 AM Christian Mauderer > <mailto:l...@c-mauderer.de>> wrote: > > > > On 15/12/2019 19:46, Niteesh

Re: Problem running RTEMS on raspberrypi3

I got uboot running on my raspi3. But I can't figure out to load and run a custom kernel. Can you explain the steps or point me to some reference. On Mon, Dec 16, 2019 at 5:13 PM Niteesh wrote: > On Mon, Dec 16, 2019 at 2:36 AM Christian Mauderer > wrote: > >> >> >&

Re: [EXTERNAL] Re: Problem running RTEMS on raspberrypi3

use > that UART to talk to the Bluetooth module. The “mini” UART is then used for > the console. > > So, at a minimum, I think the RPI3 needs a different console driver. > > > > https://www.raspberrypi.org/documentation/configuration/uart.md > > > > *From: *devel o

Re: [EXTERNAL] Re: Problem running RTEMS on raspberrypi3

ood to know. I would like to try the Raspberry Pi Zero W and make > sure it works like the Pi Zero without the wireless. > > > > *From: *Niteesh > *Date: *Monday, December 16, 2019 at 8:54 AM > *To: *Alan Cudmore > *Cc: *Christian Mauderer , "rtems-de...@rtems.org" <

Re: Problem running RTEMS on raspberrypi3

should work with that stage 3 loader. I don't think that > U-Boot is necessary. > > On 16/12/2019 14:01, Niteesh wrote: > > I got uboot running on my raspi3. But I can't figure out to load and run > > a custom kernel. Can you explain the steps or point me to some >

Re: Problem running RTEMS on raspberrypi3

000 x28: 3e1567e0 x29: 3e152b20 Code: 0020b048 0020b048 0020b048 0020b048 (e1a05001) Resetting CPU ... On Mon, Dec 16, 2019 at 8:11 PM Niteesh wrote: > But I am not able to boot using the 3 stage bootloader. Can someone try > booting any examples on raspi3 or other newer m

Re: Problem running RTEMS on raspberrypi3

iled at a very > early stage. > > Did you try a go 0x20 instead? Normally the first vector is a reset > vector which jumps to the right start address. The jump can have a mode > with it. So if you directly jump to 0x200080 the core might is in a > wrong mode. > > On 16/

Re: raspberry BSP: Maybe there is a bug in the linker file?

As far as I know, 0x8000 is a fixed address where the bootloader jumps to after loading the application assuming the CPU is in 32bit mode. For 64bit mode, it jumps to 0x8. On Thu, Dec 19, 2019 at 6:58 PM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 19/12/2019 14:24, Chri

Re: raspberry BSP: Maybe there is a bug in the linker file?

I will do it by either today or tomorrow. On Fri, 20 Dec, 2019, 12:03 PM Sebastian Huber, < sebastian.hu...@embedded-brains.de> wrote: > On 19/12/2019 15:28, Niteesh wrote: > > As far as I know, 0x8000 is a fixed address where the bootloader jumps > > to after loading the

Re: raspberry BSP: Maybe there is a bug in the linker file?

these ideas will help in the future. On Fri, Dec 20, 2019 at 2:46 PM Christian Mauderer wrote: > On 20/12/2019 09:22, Christian Mauderer wrote: > > On 20/12/2019 07:33, Sebastian Huber wrote: > >> On 19/12/2019 15:28, Niteesh wrote: > >>> As far as I know, 0x800

Re: raspberry BSP: Maybe there is a bug in the linker file?

seem to jump to bsp_vector_table_begin and hang there (0x00c). On Sat, Dec 21, 2019 at 1:42 AM Christian Mauderer wrote: > On 20/12/2019 19:19, Niteesh wrote: > > How do you test a patch? Do you checkout that particular commit and > > build and the BSP again?. > > Basica

Re: raspberry BSP: Maybe there is a bug in the linker file?

20 PM Christian Mauderer wrote: > On 21/12/2019 08:28, Niteesh wrote: > > Did you take a look at the exception? > > Not yet. > > > I still couldn't get it running on > > the rpi3 using rpi2 bsp. > > Again: It's quite likely that the serial interface is a pro

Re: raspberry BSP: Maybe there is a bug in the linker file?

Looks like there is already framebuffer support for RPi, but still I would like to play with it and add some GUI example as in https://blog.thelunatic.dev/gsoc-final-report/ On Sat, Dec 21, 2019 at 2:32 PM Niteesh wrote: > I am very much interested in taking part in GSOC 2020. I want to

Re: raspberry BSP: Maybe there is a bug in the linker file?

Shall I start writing a driver for raspberrypi3 PL011? On Sat, Dec 21, 2019 at 8:40 PM Christian Mauderer wrote: > On 19/12/2019 15:05, Christian Mauderer wrote: > > On 19/12/2019 14:27, Sebastian Huber wrote: > >> On 19/12/2019 14:24, Christian Mauderer wrote: > >>> Hello, > >>> > >>> triggere

Re: raspberry BSP: Maybe there is a bug in the linker file?

There is already a PL011 driver in the arm shared section. should we just import it? On Sat, Dec 21, 2019 at 10:46 PM Niteesh wrote: > Shall I start writing a driver for raspberrypi3 PL011? > > > On Sat, Dec 21, 2019 at 8:40 PM Christian Mauderer > wrote: > >> On 19/

Re: raspberry BSP: Maybe there is a bug in the linker file?

:26, Niteesh wrote: > > There is already a PL011 driver in the arm shared section. should we > > just import it? > > If you say "import" and you mean "use" and not "copy": yes, that would > be great. > > > > > On Sat, Dec 21, 2019 at 10:

Re: raspberry BSP: Maybe there is a bug in the linker file?

wrote: > I haven't had a look at the different types of UARTS yet. What is the > difference? What do you use as reference? > > If it is just a variant of an existing driver, the existing one should > be extended to support both variants. > > On 21/12/2019 20:45, Niteesh wr

Raspberrypi3: Mini UART driver

The rpi1 and rpi2 use the PL011 UART, whereas, with RPI's equipped with wireless/Bluetooth module, the PL011 is connected to the Bluetooth module, and the mini UART is used as the primary UART. https://www.raspberrypi.org/app/uploads/2012/02/BCM2835-ARM-Peripherals.pdf But from the above doc (PAGE

Re: Raspberrypi3: Mini UART driver

On Sun, Dec 22, 2019 at 8:44 PM Christian Mauderer wrote: > Hello Niteesh, > > thanks for doing that work. > > On 22/12/2019 12:10, Niteesh wrote: > > The rpi1 and rpi2 use the PL011 UART, whereas, with RPI's equipped with > > wireless/Bluetooth module, the PL0

Re: Raspberrypi3: Mini UART driver

tian Mauderer wrote: > On 22/12/2019 19:45, Joel Sherrill wrote: > > > > > > On Sun, Dec 22, 2019, 12:29 PM Niteesh > <mailto:gsnb...@gmail.com>> wrote: > > > > On Sun, Dec 22, 2019 at 8:44 PM Christian Mauderer > > mailto:l...@c-maudere

Re: Raspberrypi3: Mini UART driver

Is the correct port minor number set during the initialization? What is the application want's to access some other port? On Tue, Dec 24, 2019 at 12:16 AM Niteesh wrote: > I would like to clarify my doubts regarding the console driver. I went > through the documentation > for the

Re: Raspberrypi3: Mini UART driver

And finally, how does printf work? It is a macro? In that case, how does any write to a console work? On Tue, Dec 24, 2019 at 12:18 AM Niteesh wrote: > Is the correct port minor number set during the initialization? What is > the application want's to > access some other port? &

Re: Raspberrypi3: Mini UART driver

On Tue, Dec 24, 2019 at 3:20 AM Christian Mauderer wrote: > Hello Niteesh, > > quite a lot of questions. I'll try to answer them. Note that it has been > some time since I had a detailed look at that code so if something I > tell seems odd please don't hesitate to que

Re: Raspberrypi3: Mini UART driver

the console_initialization function. On Tue, Dec 24, 2019 at 2:13 PM Niteesh wrote: > Thank you so much, for such a detailed answer. Now things make really good > sense to me, > going through the code now is just a breeze. But I still have one question > for the newer driver

Re: Raspberrypi3: Mini UART driver

How to handle different serial devices? In other BSPs the uart devices are the same, so they were able to put it under a single array? But here we have 2 uarts and a FB? On Tue, Dec 24, 2019 at 8:18 PM Christian Mauderer wrote: > On 24/12/2019 12:06, Niteesh wrote: > > The curr

Re: Raspberrypi3: Mini UART driver

the reg field point to the correct memory location? for instance in IMX BSP, there is a struct with register field's but none of the define a memory location? On Tue, Dec 24, 2019 at 11:37 PM Niteesh wrote: > How to handle different serial devices? In other BSPs the uart devices are > t

Re: Raspberrypi3: Mini UART driver

I figured the register part, it is setting itself through the FDT. On Tue, Dec 24, 2019 at 11:49 PM Niteesh wrote: > And also the register definitions are in raspberrpi.h file should I move > them to usart.h. > I have a doubt we have a register field in device_context > ty

Re: Raspberrypi3: Mini UART driver

_read_polled, + .set_attributes = usart_set_attributes, + .write = usart_write_support_polled, + .mode = TERMIOS_POLLED +} \ No newline at end of file On Wed, Dec 25, 2019 at 12:36 AM Joel Sherrill wrote: > > > On Tue, Dec 24, 2019, 12:19 PM Niteesh wrote: > >> And also the register defi

Re: Raspberrypi3: Mini UART driver

What about the framebuffer it still uses minor and major's? On Wed, Dec 25, 2019 at 3:20 PM Niteesh wrote: > Just to make sure I am going in the right track. > I moved the uart register definitions to bsp/usart.h into a struct of > uint32_t called usart0_regs > here is git diff

Re: Raspberrypi3: Mini UART driver

On Fri, Dec 27, 2019 at 1:58 AM Christian Mauderer wrote: > Hello Niteesh, > > sorry for not answering earlier. During this time of the year you have > to expect some delays on the mailing list due to public holydays and > vacations. That's okay, I understand. > > On

Re: Raspberrypi3: Mini UART driver

On Fri, Dec 27, 2019 at 1:59 AM Christian Mauderer wrote: > On 25/12/2019 15:32, Niteesh wrote: > > What about the framebuffer it still uses minor and major's? > > I'm not entirely sure but I don't think that it is a problem to mix > legacy and new

Re: Raspberrypi3: Mini UART driver

Does the device's initialization happen in the first_open function for the new interface? Because the old legacy driver call's the initialization function directly. On Fri, Dec 27, 2019 at 2:00 PM Niteesh wrote: > On Fri, Dec 27, 2019 at 1:59 AM Christian Mauderer > wrote: &g

Re: Raspberrypi3: Mini UART driver

I have sent the patch. I also sent a documentation update for the quick-start section a few months ago. But no one took a look at it. Can you have a look at it? https://www.mail-archive.com/devel@rtems.org/msg20965.html ___ devel mailing list devel@rtems

Re: Raspberrypi3: Mini UART driver

Is there something else that I could work on? I am interested in taking part GSOC of 2020. And I want to learn as much as possible. On Fri, Dec 27, 2019 at 5:07 PM Christian Mauderer wrote: > On 27/12/2019 12:20, Niteesh wrote: > > I have sent the patch. I also sent a documentation u

Re: Raspberrypi3: Mini UART driver

On Sat, 28 Dec, 2019, 3:51 AM Christian Mauderer, wrote: > On 27/12/2019 19:06, Niteesh wrote: > > Is there something else that I could work on? I am interested in taking > > part > > GSOC of 2020. And I want to learn as much as possible. > > Do you search tasks speci

Re: [PATCH] Raspberrypi: updated the console interface.

If possible it would be nice if you could > fix it anyway. In that case maybe in an extra commit. At least the PL011 works on a Pi2 on real hardware too. I haven't tested > the framebuffer yet. I'm still trying to find out how to select it > before or after the patch. > >

Re: [PATCH] Raspberrypi: updated the console interface.

On Sat, Dec 28, 2019 at 3:20 PM Christian Mauderer wrote: > Missed your question further below in my first mail. > > On 28/12/2019 10:45, Christian Mauderer wrote: > > On 28/12/2019 09:38, Niteesh wrote: > >> I didn't get any of these warnings, which command did yo

Re: [PATCH v2] Raspberrypi: updated the console interface.

con = dev->context; console_instance(con, c); } console_instance is the function pointer, which is assigned to arm_pl011_write_polled by default, or to fbcons_write_polled, if frame buffer is decided to be used. On Sat, Dec 28, 2019 at 8:50 PM Christian Mauderer wrote: > On 28/12/2019 14:

Re: [PATCH v2] Raspberrypi: updated the console interface.

On Sat, Dec 28, 2019 at 11:12 PM Christian Mauderer wrote: > On 28/12/2019 17:22, Niteesh wrote: > > I think you misunderstood, I was talking about the casting in the > > rtems_termios_device_handler > > Yes, I misunderstood you there. > > > const rtems_ter

Re: [PATCH v2] Raspberrypi: updated the console interface.

? Currently, the console_select has 2 functions, bsp_Is_Available and bsp_console_select. On Sat, Dec 28, 2019 at 11:30 PM Niteesh wrote: > On Sat, Dec 28, 2019 at 11:12 PM Christian Mauderer > wrote: > >> On 28/12/2019 17:22, Niteesh wrote: >> > I think you misunderstood,

Re: [PATCH v2] Raspberrypi: updated the console interface.

Is bsp_console_select legacy? And the new way will be by linking the correct serial device to /dev/console in console_initialization, right? If so, shall I add one? On Sat, Dec 28, 2019 at 11:50 PM Niteesh wrote: > I am sorry if this question sounds silly, but how can I access

Re: [PATCH v2] Raspberrypi: updated the console interface.

:48, Niteesh wrote: > > Is bsp_console_select legacy? And the new way will be by linking > > the correct serial device to /dev/console in console_initialization, > right? > > If so, shall I add one? > > The function is only called from legacy-console.c. So yes: This function

Re: [PATCH v2] Raspberrypi: updated the console interface.

Where does qemu place the dtb file? we can pass the dtb file to the kernel using -dtb, but not sure where it puts it? googled a lot but couldn't find it. I also tried running u-boot, it successfully ran on raspi3 in 64bit mode. I couldn't get it running on raspi2. The qemu raspi3 doesn't support n

Re: [PATCH v3] Raspberrypi: updated the console interface.

I am sorry, I sent the previous without testing and building, so it might contain some errors. Just tell me if you are happy with the code, I will fix all the error's and send in a new patch. On Sun, Dec 29, 2019 at 8:04 PM G S Niteesh wrote: > The patch updates the older console interf

Re: [PATCH v3] Raspberrypi: updated the console interface.

Where does RTEMS except the DTB file to be present? On Sun, Dec 29, 2019 at 8:27 PM Niteesh wrote: > I am sorry, I sent the previous without testing and building, so it might > contain some errors. > Just tell me if you are happy with the code, I will fix all the error's >

Re: [PATCH v3] Raspberrypi: updated the console interface.

arm_pl011_context pl011_context; rpi_fb_context fb_context; char uart_instance[20]; static void output_char_serial(char c) { arm_pl011_write_polled(&pl011_context.base, c); } void output_char_fb(char c) { fbcons_write_polled(&fb_context.base, c); } static void *get_reg_of_node(const void *fdt,

Re: [PATCH v3] Raspberrypi: updated the console interface.

I am not happy with my code at all, I can please provide some suggestions. On Mon, Dec 30, 2019 at 12:17 AM Niteesh wrote: > arm_pl011_context pl011_context; > rpi_fb_context fb_context; > char uart_instance[20]; > > > static void output_char_serial(char c) > { >

Re: What do you want to study in GSOC 2020?

On Mon, Dec 30, 2019 at 4:44 AM Peter Dufault wrote: > > Niteesh, what do you want to study? Go over what most interests you most > about working in a real-time environment like RTEMS, and not about working > on the RPI, and look at the earlier GSOC projects. Propose an ideal p

Re: [PATCH v3] Raspberrypi: updated the console interface.

orm. But that's most > likely not the suggestion you searched for ;-) > > On 29/12/2019 19:48, Niteesh wrote: > > I am not happy with my code at all, I can please provide some > suggestions. > > > > On Mon, Dec 30, 2019 at 12:17 AM Niteesh > <mailto:gsnb...@g

Re: [PATCH v3] Raspberrypi: updated the console interface.

, 30 Dec, 2019, 1:20 PM Niteesh, wrote: > On Mon, 30 Dec, 2019, 2:07 AM Christian Mauderer, > wrote: > >> I assume you want suggestions regarding this code rather than the >> original patch? >> >> One suggestion: If you post code please try to use a mail prog

Re: What do you want to study in GSOC 2020?

On Mon, Dec 30, 2019 at 7:14 PM Christian Mauderer wrote: > On 30/12/2019 07:25, Niteesh wrote: > > > > > > On Mon, Dec 30, 2019 at 4:44 AM Peter Dufault > <mailto:dufa...@hda.com>> wrote: > > > > > > Niteesh, what do you want to study?

Re: [PATCH v3] Raspberrypi: updated the console interface.

On Mon, Dec 30, 2019 at 6:56 PM Christian Mauderer wrote: > On 30/12/2019 09:21, Niteesh wrote: > > I just looked at the dts files for rpi4, the uart 0, uart 1 are the > > same, the additional 4 uarts are in different pins and can be used > > simultaneously. They are all p

Re: [PATCH v4] Raspberrypi: updated the console interface.

about qemu4 rsb package how is it different from the official qemu? On Mon, Dec 30, 2019 at 11:53 PM G S Niteesh wrote: > The patch updates the older console interface used by the BSP, > to newer one. It also replaces the custom usart(PL011) driver > with arm-pl011. The fb function

Re: [PATCH v4] Raspberrypi: updated the console interface.

Any other suggestions with the code or are happy with it? On Tue, Dec 31, 2019 at 1:13 AM Christian Mauderer wrote: > On 30/12/2019 19:32, Niteesh wrote: > > Just to make sure that console_initialize and uart_probe are being > > called, I manually initialized the pl011 c

Re: [PATCH v4] Raspberrypi: updated the console interface.

On Tue, Dec 31, 2019 at 1:13 AM Christian Mauderer wrote: > On 30/12/2019 19:32, Niteesh wrote: > > Just to make sure that console_initialize and uart_probe are being > > called, I manually initialized the pl011 context to print something on > > serial. But they never got

Re: [PATCH v4] Raspberrypi: updated the console interface.

, one way of fixing this would be to add uart_probe into output_char just like in imx, or we could move the printing to somewhere else. On Tue, Dec 31, 2019 at 4:08 PM Christian Mauderer wrote: > > > On 31/12/2019 11:37, Christian Mauderer wrote: > > On 31/12/2019 06:11, Niteesh wro

Re: [PATCH v4] Raspberrypi: updated the console interface.

Good news, The FDT works. For testing purposes, I used a different DTB file provided by raspberrpi foundation. It has a different structure than the DTB from FreeBSD, so I modified the initialization code a little bit, but anyhow it works, the registers are initialized from the DTB file. But they a

Re: [PATCH v4] Raspberrypi: updated the console interface.

How to turn off optimizations, while debugging some of the variables get optimized out. On Wed, Jan 1, 2020 at 12:02 PM Niteesh wrote: > Good news, The FDT works. For testing purposes, I used a different DTB > file provided by > raspberrpi foundation. It has a different structure tha

Re: [PATCH v5] Raspberrypi: updated the console interface.

Christian, did you take a look at this? On Wed, 1 Jan, 2020, 2:45 PM G S Niteesh, wrote: > Replaced the older console api with newer FDT based > console driver. > Replaces the custom pl011 driver with RTEMS arm-pl011 > driver. > --- > bsps/arm/raspberrypi/console/cons

Re: [PATCH v5] Raspberrypi: updated the console interface.

to get a good direction. Most of the points I found are > only small stuff. > > On 01/01/2020 10:14, G S Niteesh wrote: > > Replaced the older console api with newer FDT based > > console driver. > > Replaces the custom pl011 driver with RTEMS arm-pl011 > > dri

Re: [PATCH] bsp/raspberry: Enabled FDT support for console.

On Fri, Jan 3, 2020 at 2:26 AM Christian Mauderer wrote: > Sorry, it seems I missed some parts in the last mail. Beneath that I > caused a misunderstanding again. > > On 02/01/2020 20:08, G S Niteesh wrote: > > Replaced the older console api with newer FDT based > > cons

Re: [PATCH] bsp/raspberry: Enabled FDT support for console.

On Fri, Jan 3, 2020 at 1:51 PM Christian Mauderer wrote: > On 03/01/2020 04:50, Niteesh wrote: > > On Fri, Jan 3, 2020 at 2:26 AM Christian Mauderer > <mailto:l...@c-mauderer.de>> wrote: > > > > Sorry, it seems I missed some parts in the last mail

Re: [PATCH] bsp/raspberrypi: Updated the console API.

Great, please do have a look at the FDT patch I sent today. I would like to work on something else now, do you have something interesting for me to do? On Fri, Jan 3, 2020 at 3:39 PM Christian Mauderer wrote: > Hello Niteesh, > > looks good to me. The UART works for a Pi1 and a

Re: [PATCH] bsp/raspberrypi: Updated the console API.

On Fri, Jan 3, 2020 at 3:48 PM Christian Mauderer wrote: > On 03/01/2020 11:11, Niteesh wrote: > > Great, please do have a look at the FDT patch I sent today. > > The FDT patch looks OK too. I thought it's clear when I said that I'll > push it together with this on

Re: [PATCH] bsp/raspberrypi: Updated the console API.

qemu-system-aarch64 doesn't support elf formats too. I tried running them but the qemu is stuck at 0x200. Should I change the cpu type to armv7, but by default Rpi3 should run 32bit applications, but not sure about qemu. On Fri, Jan 3, 2020 at 6:01 PM Niteesh wrote: > On Fri, Jan 3, 2

Re: What do you want to study in GSOC 2020?

019 at 2:47 PM Christian Mauderer > wrote: > > > > On 30/12/2019 15:45, Niteesh wrote: > > > On Mon, Dec 30, 2019 at 7:14 PM Christian Mauderer > > <mailto:l...@c-mauderer.de>> wrote: > > > > > > On 30/12/2019 07:25, Niteesh wrote: > > >

Re: [PATCH] bsp/raspberrypi: Updated the console API.

On Fri, Jan 3, 2020 at 7:32 PM Vijay Kumar Banerjee < vijaykumar9...@gmail.com> wrote: > Hi Niteesh, > A few formatting suggestions: > >> >> diff --git a/bsps/arm/raspberrypi/console/console-config.c >> b/bsps/arm/raspberrypi/console/console-config.c >&

Re: What do you want to study in GSOC 2020?

On Fri, Jan 3, 2020 at 7:30 PM Christian Mauderer wrote: > On 03/01/2020 13:49, Niteesh wrote: > > I have gone through previous year works and selected a few topics which > > I found > > interesting. > > 1. Basic Support for Trace Compass #3696 > > <https:/

Re: What do you want to study in GSOC 2020?

shot https://ibb.co/cJbFHqz But it's stuck there, maybe an exception was raised because I didn't modify the address for another device but not sure! Can you think of something which could have caused it? On Fri, Jan 3, 2020 at 11:07 PM Niteesh wrote: > On Fri, Jan 3, 2020 at 7:3

Re: What do you want to study in GSOC 2020?

On Sat, Jan 4, 2020 at 1:29 AM Christian Mauderer wrote: > On 03/01/2020 18:37, Niteesh wrote: > > On Fri, Jan 3, 2020 at 7:30 PM Christian Mauderer > <mailto:l...@c-mauderer.de>> wrote: > > > > On 03/01/2020 13:49, Niteesh wrote: > > > I

Re: What do you want to study in GSOC 2020?

On Sat, Jan 4, 2020 at 3:34 AM Christian Mauderer wrote: > On 03/01/2020 20:17, Niteesh wrote: > > Finally, I am able to load IMAGES into Rpi3 using u-boot. But didn't > > check whether FDT works. I added the AUX driver from my bare-metal > > project for testing. I&

Re: What do you want to study in GSOC 2020?

mes on the board and no issues till now. On Sat, Jan 4, 2020 at 8:47 AM Niteesh wrote: > On Sat, Jan 4, 2020 at 3:34 AM Christian Mauderer > wrote: > >> On 03/01/2020 20:17, Niteesh wrote: >> > Finally, I am able to load IMAGES into Rpi3 using u-boot. But didn't >&g

Re: [PATCH] Updated docs to use the standalone SIS simulator, instead of GDB inbuilt SIS for the erc32 BSP.

Just a reminder, it's almost been a week since I sent the patch. I also sent it a month ago, but it slipped from everyone's eyes. On Thu, Jan 2, 2020 at 9:45 PM Gedare Bloom wrote: > looks good to me. > > On Fri, Dec 27, 2019 at 5:02 AM G S Niteesh wrote: > > &g

Raspberrypi3: AUX Uart driver

We could now run RTEMS on Rpi3. I tried examples from the samples section and they run fine. But still, a lot of functionality has to tested since it uses the RPI2 BSP. To test these examples I used a simple driver for the AUX. The documentation from BCM link

Re: [PATCH] doc/raspberrypi: Added instructions for raspberrypi

I have added basic instructions, just let me know if you need any other section. On Sun, Jan 5, 2020 at 6:17 PM G S Niteesh wrote: > Added instructions to run examples on raspberrypi. > --- > user/bsps/arm/raspberrypi.rst | 75 ++- > 1 file

Re: [PATCH v2] doc/raspberrypi: Added instructions for raspberrypi

> > > On 05/01/2020 20:19, G S Niteesh wrote: > > > Added instructions to run examples on raspberrypi. > > > --- > > > user/bsps/arm/raspberrypi.rst | 74 ++- > > > 1 file changed, 73 insertions(+), 1 deletion(-) > > &g

Re: [PATCH v2] bsp/raspberrypi: Updated the console API.

e one extra header in bsp/fbcons.h. But that has been > a hidden bug anyway. > > On 04/01/2020 20:50, G S Niteesh wrote: > > Replaces the legacy termios API with new termios API (#3034) > > Replaces the custom PL011 serial driver with RTEMS arm-pl011. > > Update #3034 >

Re: [PATCH v2] doc/raspberrypi: Added instructions for raspberrypi

I didn't use the QEMU build from RSB, I built it from the source directly for another project I'll try QEMU from RSB, and will also add instructions for it in a couple of days. On Tue, Jan 7, 2020 at 1:00 AM Gedare Bloom wrote: > On Mon, Jan 6, 2020 at 11:25 AM Niteesh wrote: &

Re: [PATCH v2] bsp/raspberrypi: Updated the console API.

You said that the FB was not working, was it because of this bug? or else I want to take a look at it. On Tue, Jan 7, 2020 at 11:03 PM Niteesh wrote: > Great, thank you it wouldn't have been possible without your help and > support. > And thanks for patiently answering my quest

Re: Raspberrypi3: AUX Uart driver

this will be really helpful. On Sun, Jan 5, 2020 at 12:57 AM Christian Mauderer wrote: > On 04/01/2020 09:32, Niteesh wrote: > > We could now run RTEMS on Rpi3. I tried examples from the samples > > section and they run > > fine. But still, a lot of functionality has t

Re: [PATCH v2] doc/raspberrypi: Added instructions for raspberrypi

I can't build QEMU using RSB, there seems to be a problem with GLib(see attachment) but I had no problem building it from the source. Should I just mention build qemu from source? On Tue, Jan 7, 2020 at 11:12 PM Niteesh wrote: > I didn't use the QEMU build from RSB, I built it fr

Re: [PATCH v2] doc/raspberrypi: Added instructions for raspberrypi

how to automate > testing the Pi's. > >> Jiri. >> >> >> On 1/12/20 4:48 PM, Niteesh wrote: >> >> I can't build QEMU using RSB, there seems to be a problem with GLib(see >> attachment) >> but I had no problem building it from the source. Sh

Re: Raspberrypi3: AUX Uart driver

On Sun, Jan 12, 2020 at 11:42 PM Christian Mauderer wrote: > Hello Niteesh, > > On 12/01/2020 16:06, Niteesh wrote: > > The only issue, I faced while using this driver is the baud divisor is > > calculated > > by CLOCK_FREQ/(BAUD_RATE * 16) (*ns16550-context.c:68)*

Re: Raspberrypi3: AUX Uart driver

word from the binary file to the RAM? English is not my native language, and it is really hard for me to express my question's so please if you don't understand the question do let me know. On Mon, Jan 13, 2020 at 1:56 AM Niteesh wrote: > On Sun, Jan 12, 2020 at 11:42 PM Chris

Re: Raspberrypi3: AUX Uart driver

On Mon, Jan 13, 2020 at 1:38 PM Christian Mauderer < christian.maude...@embedded-brains.de> wrote: > On 12/01/2020 21:26, Niteesh wrote: > > On Sun, Jan 12, 2020 at 11:42 PM Christian Mauderer > <mailto:l...@c-mauderer.de>> wrote: > > > > Hello N

Re: Raspberrypi3: AUX Uart driver

The ns16550_context already has a field named baud_divisor, so if the user passes value for it, then we can skip the GetBaudDivisor function and use that value instead. Is this approach okay? On Mon, Jan 13, 2020 at 3:46 PM Niteesh wrote: > On Mon, Jan 13, 2020 at 1:38 PM Christian Maude

Re: Raspberrypi3: AUX Uart driver

On Tue, Jan 14, 2020 at 1:57 PM Christian Mauderer < christian.maude...@embedded-brains.de> wrote: > On 13/01/2020 19:04, Niteesh wrote: > > The ns16550_context already has a field named baud_divisor, so if the > > user passes > > value for it, then we can skip the GetB

Re: Raspberrypi3: AUX Uart driver

I am finished with code, I tested it in QEMU emulator raspi2but it doesn't work when testing on real rpi3. I don't know if the problem is with loading the FDT or with my code? How do I send the code, so that you can take a look at it? On Tue, Jan 14, 2020 at 8:04 PM Niteesh wrote: >

  1   2   3   4   5   >