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

There is a whitespace error: > git am ~/\[PATCH\ v5\]\ Raspberrypi:\ updated\ the\ console\ interface..eml Applying: Raspberrypi: updated the console interface. /home/christian/rtems/rtems-bbb/.git/modules/rtems/rebase-apply/patch:732: trailing whitespace. * @name Bus to Physical address

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

On 02/01/2020 14:24, Niteesh wrote: > Christian, did you take a look at this? Not yet. I'm not always reachable during my vacation. This is only hobby time ;-) I'll try to take a look soon. > > On Wed, 1 Jan, 2020, 2:45 PM G S Niteesh, > wrote: > > Replaced the

Re: Pi2 and Pi3 on qemu

On 30/12/2019 17:14, Joel Sherrill wrote: > Hi > > It has been great watching the traffic over the holidays on the Pi. > Thanks guys. > > I recently checked the board models supported by the qemu built by the > qemu4 rsb package. It has Pi2 and Pi3.  > > 1. The Pi3 may help when debugging. > >

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

On 01/01/2020 07:38, Niteesh wrote: > How to turn off optimizations, while debugging some of the variables get > optimized out. First: Great that it works now. Regarding optimization: Do a export CFLAGS_OPTIMIZE_V="-O0 -g" before configure and make. Alternatively change it in

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

what is necessary to get the polled > uart working. > That one will only be called if you have an exception at > a very early > stage. In that case you are working in an exception context. > > > >

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

init_context_pl011 since it's is > only initializing > the pl011 context, rather than registering it. > > On Tue, Dec 31, 2019 at 6:32 PM Christian Mauderer <mailto:l...@c-mauderer.de>> wrote: > > On 31/12/2019 13:22, Niteesh wrote: > > It wo

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

st like in imx, or we could move the printing to somewhere > else. That might would be a good idea regardless whether the print is moved or not. It would allow an early exception to print anything. > > On Tue, Dec 31, 2019 at 4:08 PM Christian Mauderer <mailto:l...@c-mauderer.de>&

Re: Error while building the rtems-libbsd

om further above. As a workaround could you try to use python3? Some string handling is different there so it might work or give a better error message. Just use python3 ./waf ... instead of only "waf" in every waf command line. > > On Mon, Dec 30, 2019 at 7:19 PM Chri

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

On 31/12/2019 11:37, Christian Mauderer wrote: > On 31/12/2019 06:11, Niteesh wrote: >> On Tue, Dec 31, 2019 at 1:13 AM Christian Mauderer > <mailto:l...@c-mauderer.de>> wrote: >> >> On 30/12/2019 19:32, Niteesh wrote: >> > Just to make s

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

On 31/12/2019 06:11, Niteesh wrote: > On Tue, Dec 31, 2019 at 1:13 AM Christian Mauderer <mailto:l...@c-mauderer.de>> wrote: > > On 30/12/2019 19:32, Niteesh wrote: > > Just to make sure that console_initialize and uart_probe are being > > called, I

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

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: > > > > > > On Mon, Dec 30, 2019 at 4:44 AM Peter Dufault <mailt

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

On 30/12/2019 20:43, 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 called. C

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

On 30/12/2019 16:02, Niteesh wrote: > On Mon, Dec 30, 2019 at 6:56 PM Christian Mauderer <mailto:l...@c-mauderer.de>> 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 > >

Re: Error while building the rtems-libbsd

On 28/12/2019 18:43, Utkarsh Rai wrote: > Hi, > While building the rtems-libbsd as described here > >  I > was able to successfully configure the waf file as:- > waf configure >

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

some of the previous GSOC projects, BSP development > and real-time tracing are what I find interesting. While also converting > the console driver of rpi to FDT based one, *Christian Mauderer > *explained how  > FDT worked in FreeBSD and Linux, and RTEMS lacked that infrastruct

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

> On Mon, 30 Dec, 2019, 2:07 AM Christian Mauderer, > mailto:l...@c-mauderer.de>> 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 ma

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

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 program that keeps the indentation. It's hard to read in this form. But that's most likely not the suggestion you searched for ;-) On 29/12/2019 19:48,

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

On 29/12/2019 18:44, Niteesh wrote: > Where does RTEMS except the DTB file to be present? See my mail in the other thread regarding that. You might have to add a define in the configure.ac. > > On Sun, Dec 29, 2019 at 8:27 PM Niteesh > wrote: > > I am sorry, I

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

On 29/12/2019 15:23, Niteesh wrote: > 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'm not really sure where qemu places a dtb. Maybe it helps if I describe roughly how it would work

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

On 29/12/2019 11:04, Niteesh wrote: > On Sun, Dec 29, 2019 at 2:33 PM Christian Mauderer <mailto:l...@c-mauderer.de>> wrote: > > On 29/12/2019 07:09, Niteesh wrote: > > Is there any way to test and debug this? Maybe using GDB to > > see if a p

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

relevant register functions in the console initialization. - After that you parse the command line and create the link. I think that is basically what you described already just with a few more words ;-) > > On Sun, Dec 29, 2019 at 2:11 AM Christian Mauderer <mailto:l...@c-mauderer

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

is no longer used. I expect that it will be mainly the files containing the table based selection and console selection code. > > On Sun, Dec 29, 2019 at 12:27 AM Christian Mauderer <mailto:l...@c-mauderer.de>> wrote: > > On 28/12/2019 19:48, Niteesh wrote: >

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 <mailto:gsnb...@gmail.com>> wrote: > > On Sat, Dec 28, 2019 at 11:12 PM Christian Mauderer > mailt

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

h <mailto:gsnb...@gmail.com>> wrote: > > On Sat, Dec 28, 2019 at 11:12 PM Christian Mauderer > mailto:l...@c-mauderer.de>> wrote: > > On 28/12/2019 17:22, Niteesh wrote: > > I think you misunderstood, I was talking about the casting in the >

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

value of BSP_output_char (one of the wrappers) - Call the right function with a fixed parameter So it's a bit shorter and beneath that you save a global variable. > > On Sat, Dec 28, 2019 at 8:50 PM Christian Mauderer <mailto:l...@c-mauderer.de>> wrote: > > On 28/12/2019

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

On 28/12/2019 14:10, 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's signatures where also changed > to accommodate with interface update. > Update #3034 > --- >

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

On 28/12/2019 13:41, Niteesh wrote: > On Sat, Dec 28, 2019 at 3:20 PM Christian Mauderer <mailto:l...@c-mauderer.de>> wrote: > > Missed your question further below in my first mail. > > On 28/12/2019 10:45, Christian Mauderer wrote: > > On 28/12/2019 09

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

And I think you can add an "Update #3034" to your commit message: https://devel.rtems.org/ticket/3034 It's a bit hidden but the old driver uses "rtems_termios_open" via the legacy-console.c. You removed that from the build for raspberry. On 28/12/2019 10:50, Christian Maud

Re: Raspberrypi3: Mini UART driver

On 28/12/2019 07:12, Niteesh wrote: > > > On Sat, 28 Dec, 2019, 3:51 AM Christian Mauderer, <mailto:l...@c-mauderer.de>> wrote: > > On 27/12/2019 19:06, Niteesh wrote: > > Is there something else that I could work on? I am interested in > taking &

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

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 you use? > > Just the usual make in the build directory. I configured with the &

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

the warnings might are a bit hidden. Also note that you only get them if the file is recompiled. So either you have to change something or remove the console-config.o and fbcons.o object file to trigger them on a re-make. > > On Sat, Dec 28, 2019 at 3:48 AM Christian Mauderer <mailto:l...

Re: Raspberrypi3: Mini UART driver

o warm up? > > On Fri, Dec 27, 2019 at 5:07 PM Christian Mauderer <mailto:l...@c-mauderer.de>> wrote: > > On 27/12/2019 12:20, Niteesh wrote: > > I have sent the patch. I also sent a documentation update for the > > quick-start section > > a few months

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

Hello, git complained about some whitespaces when applying the patch: git am \[PATCH\]\ Raspberrypi:\ updated\ the\ console\ interface..eml Applying: Raspberrypi: updated the console interface. /home/christian/rtems/rtems-bbb/.git/modules/rtems/rebase-apply/patch:96: trailing

Re: raspberry pi: Problems with the dynamic work area

, Christian Mauderer wrote: > Hello, > > the patch > > > https://git.rtems.org/rtems/commit/?id=a4d7e4cee77d16b0e34ef543f0804e7eb2954137 > > introduced some problems. It tries to adapt the work area based on the > size of the available memory. In theory this is a good id

Re: Raspberrypi3: Mini UART driver

On 27/12/2019 12:20, Niteesh wrote: > 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? I'll try to have a look at it soon. > >

Re: Raspberrypi3: Mini UART driver

BCM2835_UART0_ILPR       (BCM2835_UART0_BASE + 0x20) > -#define BCM2835_UART0_IBRD       (BCM2835_UART0_BASE + 0x24) > -#define BCM2835_UART0_FBRD       (BCM2835_UART0_BASE + 0x28) > -#define BCM2835_UART0_LCRH       (BCM2835_UART0_BASE + 0x2C) > -#define BCM2835

Re: Raspberrypi3: Mini UART driver

On 27/12/2019 10:42, Niteesh wrote: > On Fri, Dec 27, 2019 at 2:53 PM Christian Mauderer <mailto:l...@c-mauderer.de>> wrote: > > Hello Niteesh, > > let me repeat two important questions: > > - How do you plan to test the changes? Simulator i

Re: Raspberrypi3: Mini UART driver

-> last_close is _not_ called - close(fd2) -> last_close is called - fd1 = open("/dev/ttyX") -> first_open is called again > > On Fri, Dec 27, 2019 at 2:00 PM Niteesh <mailto:gsnb...@gmail.com>> wrote: > > On Fri, Dec 27, 2019 at 1:59 AM Chri

Re: Raspberrypi3: Mini UART driver

On 27/12/2019 09:30, Niteesh wrote: > On Fri, Dec 27, 2019 at 1:59 AM Christian Mauderer <mailto:l...@c-mauderer.de>> wrote: > > On 25/12/2019 15:32, Niteesh wrote: > > What about the framebuffer it still uses minor and major's? > > I'm not e

Re: Raspberrypi3: Mini UART driver

wrote: > On Fri, Dec 27, 2019 at 1:58 AM Christian Mauderer <mailto:l...@c-mauderer.de>> 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 h

Re: Raspberrypi3: Mini UART driver

usart.h > > I have a doubt we have a register field in device_context > typedef struct {  > > rtems_termios_device_context base;  > > const char *device_name;  > > volatile some_chip_registers *regs; &

Re: Raspberrypi3: Mini UART driver

s_termios_device_context base;  > > const char *device_name;  > > volatile some_chip_registers *regs; > > } my_driver_context; > > How does the reg field point to the correct memory location? for > instance in IMX BSP, >

Re: Raspberrypi3: Mini UART driver

egacy one, how do you want me to proceed, > shall I rewrite the legacy to a > the new one, this is will be a great learning experience for me also > and we also get the BSP updated to the latest interface. > > > On Tue, Dec 24, 2019 at 3:20 AM Christian Mauderer > ma

Re: Raspberrypi3: Mini UART driver

nction install the serial driver using > rtems_termios_device_install but there seems to be > no such function in the raspberry pi? But there is a entry in > console_fns for init function, but then how does it > gets called? >

Re: Raspberrypi3: Mini UART driver

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-mauderer.de>> wrote: > > Hello Niteesh,

raspberry pi: Problems with the dynamic work area

0fcec757576876aa Mon Sep 17 00:00:00 2001 From: Christian Mauderer Date: Sat, 21 Dec 2019 16:23:29 +0100 Subject: [PATCH] bsp/raspberrypi: Fix size of work area. The calculation for the real memory size (based on the board revision) should be done based on the real SDRAM start address (which is 0x

Re: Raspberrypi3: Mini UART driver

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 PL011 is connected to the Bluetooth > module, and the mini UART is used as the primary UART. In my opinion it

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

PS: Please create a new mailing list thread for discussing details regarding the UART driver. The subject of this one just isn't correct any more. On 22/12/2019 09:50, Christian Mauderer wrote: > Hello Niteesh, > > thanks for the detailed information. I agree that this is a c

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

DTR or RI signals > > https://www.raspberrypi.org/app/uploads/2012/02/BCM2835-ARM-Peripherals.pdf > the official doc from broadcom, this is what I used while developing > drivers for bare metal project. > > > > On Sun, Dec 22, 2019 at 1:56 AM Christian Mauderer <ma

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

n place instead of using the > appropriate function, for example > the usart_set_baud is empty and the baud rate is set directly in the > init function. > What do you think about these changes? Should we change them also? > On Sun, Dec 22, 2019 at 12:25 AM Christian Maude

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

Niteesh <mailto:gsnb...@gmail.com>> wrote: > > Shall I start writing a driver for raspberrypi3 PL011? > > > On Sat, Dec 21, 2019 at 8:40 PM Christian Mauderer > mailto:l...@c-mauderer.de>> wrote: > > On 19/12/2019 15:05, Christian Mauderer wro

Re: [PATCH] bsp/raspberrypi: Fix linker command file

With some further tests that is not absolutely necessary like I first thought. The raspberry bootloader has a configuration option for setting the start address: If the following line is added to the config.txt we can leave the address at 0x0020: kernel_address=0x0020 See

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

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, >>> >>> triggered by the discussion regarding RTEMS on raspberrypi 3 I did some >>> tests. I haven

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

bone as a reference. > On Sat, Dec 21, 2019 at 2:20 PM Christian Mauderer > mailto:l...@c-mauderer.de>> wrote: > > On 21/12/2019 08:28, Niteesh wrote: > > Did you take a look at the exception? > > Not yet. > >

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

db with set scheduler-locking on. I seem to jump > to bsp_vector_table_begin and hang there (0x00c). I thought you don't have a debugger connected? How do you run it with gdb? > > > On Sat, Dec 21, 2019 at 1:42 AM Christian Mauderer <mailto:l...@c-mauderer.de>> wrote: &

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

commit that introduced the second bug. > @Christian Mauderer <mailto:l...@c-mauderer.de>  how did you build it > for the rpi1? Did you follow the steps as in previous threads? Basically the same steps like for every BSP: 1. Build a recent toolchain using RSB. 2. Build the BSP. 3. Te

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

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, 0x8000 is a fixed address where the bootloader jumps >>> to after loading the application assuming the CPU is in 32b

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

On 20/12/2019 07:33, Sebastian Huber 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 application assuming the CPU is in 32bit mode. >> For 64bit mode, it jumps to 0x8. > > Would you mind testing

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

On 19/12/2019 14:27, Sebastian Huber wrote: > On 19/12/2019 14:24, Christian Mauderer wrote: >> Hello, >> >> triggered by the discussion regarding RTEMS on raspberrypi 3 I did some >> tests. I haven't been able to start a RTEMS on my Pi 1 if I trie

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

Hello, triggered by the discussion regarding RTEMS on raspberrypi 3 I did some tests. I haven't been able to start a RTEMS on my Pi 1 if I tried a version after commit c5fd79cd4704a4270ba0114a1009ab8556f997c9 from 29.07.2019. Right before it everything works as expected. The commit changes the

Re: [rtems-tools] record does not compile with llvm9

On 18/12/2019 07:04, Sebastian Huber wrote: > On 17/12/2019 15:48, l...@c-mauderer.de wrote: >> It compiles on llvm9 but I didn't test it on llvm7 or 8. Beneath that >> it's an untested change. > > It works on llvm7. Please check it in. > Thanks. I pushed it.

Re: Problem running RTEMS on raspberrypi3

to > load the kernel img. > No success in following these steps.  > I think this is maybe because of the different start addresses. The > default kernel load address for raspberry pi is 0x8000 in 32bit mode > and 0x8 in 64bit mode. > but RTEMS has a start address of 0x2

Re: Problem running RTEMS on raspberrypi3

default kernel load address for raspberry pi is 0x8000 in 32bit mode and > 0x8 in 64bit mode. > but RTEMS has a start address of 0x200080. > > > On Mon, Dec 16, 2019 at 7:51 PM Christian Mauderer <mailto:l...@c-mauderer.de>> wrote: > > I think I have guided y

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

__ __ > > *From: *Niteesh mailto:gsnb...@gmail.com>> > *Date: *Monday, December 16, 2019 at 8:54 AM > *To: *Alan Cudmore <mailto:alan.p.cudm...@nasa.gov>> > *Cc: *Christian Mauderer <mailto:l...@c-mauderer.de>>, "rtems-de...@rtems.org &g

Re: Problem running RTEMS on raspberrypi3

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

Re: Problem running RTEMS on raspberrypi3

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

Re: Problem running RTEMS on raspberrypi3

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 wrote: > > > > > > On Sun, Dec 15, 2019 at 10:15 PM Christia

Re: Problem running RTEMS on raspberrypi3

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, > > On 15/12/2019 09:05, Niteesh wrote: > > I am trying to get RTEMS examples running on t

Re: Problem running RTEMS on raspberrypi3

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 > the RPi3.But they don't :(, I am really sure of what is causing the problem. Note that there are at

Re: Query related to PRU drivers of BeagleBone Black

Hello Utkarsh Rai, I haven't followed the project tightly. So I can't tell much regarding 2 and 3. I added Nils (who did the GSoC 2019 project) to CC so maybe he can give you some more details. Regarding 1: In RTEMS we generally prefer the FreeBSD code due to the BSD license. Most code in Linux

[PATCH rtems-littelvgl] lv_conf.h: Enable user data.

This is usefull for passing driver objects arround and it doesn't add too much overhad for drivers that don't need it. Therefore enabling it by default seems like the better choice. --- lv_conf.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lv_conf.h b/lv_conf.h index

Re: raspberrypi BSP current status

On 30/11/2019 19:11, Niteesh wrote: > On Sat, Nov 30, 2019 at 3:03 AM Christian Mauderer <mailto:l...@c-mauderer.de>> wrote: > > On 29/11/2019 21:12, Niteesh wrote: > > I am interested in contributing to the raspberry pi BSP. As of now > RTEMS >

Re: raspberrypi BSP current status

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 unmodified for RPi3 and RPi4, I am sure about the > peripherals since the base address of

Re: Hello World Patch

re too! Thank you for your time :D > > On Tuesday, 19 November, 2019, 12:08:40 am IST, Christian Mauderer > wrote: > > > Hello Shubham Bhagat, > > it really depends a lot on what interests you. Independent what you pick > ask on the mailing list and maybe ask people that

Re: Hello World Patch

'll connect there soon. Thanks! > On Monday, 18 November, 2019, 2:21:16 am IST, Christian Mauderer > wrote: > > > Hello Shubham Bhagat, > > sorry, I missed the IRC question: In my experience our community doesn't > have lot of active people in IRC. You can try to mention so

Re: Hello World Patch

and if I see the message from my chat program (most of the time when it's evening in Germany). Best regards Christian On 16/11/2019 08:54, Christian Mauderer wrote: > Hello Shubham Bhagat, > > sounds like a good plan. Like I said: If you want to look around a bit > without picking a f

Re: Hello World Patch

some OS org to improve my understanding of OS and get some experience > along the way. RTEMS participating in GSOC is only like a cherry > topping. Thank you for your help! I will stay connected. Is the IRC only > active during GSOC? > On Thursday, 14 November, 2019, 12:13:44 am IST, Chr

Re: Hello World Patch

Hello Shubham Bhagat, welcome to RTEMS and congratulations for completing the Hello World task. You are quite early for GSoC 2020. So just to be sure let me ask: Do you plan to participate as a GSoC student or do you want to start just out of interest outside of a program like GSoC? If you want

Re: [PATCH 12/13] ada/samples: Avoid build system defined defines

.c > new file mode 100644 > index 00..ea6db06eab > --- /dev/null > +++ b/testsuites/ada/samples/base_mp/node2/init.c > @@ -0,0 +1,2 @@ > +#define CONFIGURE_MP_NODE_NUMBER 2 > +#include "../../../support/init.c" > -- embedded brains GmbH Herr Christian Maudere

Re: [PATCH 05/13] spfatal16: Remove obsolete test program

RTEMS_TOO_MANY > - > -#define CONFIGURE_APPLICATION_PREREQUISITE_DRIVERS \ > - CONSUME_SEMAPHORE_DRIVERS > - > -void force_error() > -{ > - /* This fatal error depends on the Termios device configuration */ > - TEST_END(); > - rtems_test_exit(0); > -} > -- embedded bra

Re: [PATCH rtems-littelvgl] Allow to build without drivers.

On 06/11/2019 00:35, Chris Johns wrote: > On 5/11/19 10:56 pm, Christian Mauderer wrote: >> This is for example usefull if you want to build without libbsd. > > Ok to push. > > Thanks > Chris > Thanks. Pushed it. -- ---

[PATCH rtems-littelvgl] Allow to build without drivers.

This is for example usefull if you want to build without libbsd. --- lvgl.py | 8 +--- wscript | 7 +++ 2 files changed, 12 insertions(+), 3 deletions(-) diff --git a/lvgl.py b/lvgl.py index 6d83c63..5452ed0 100644 --- a/lvgl.py +++ b/lvgl.py @@ -30,7 +30,7 @@ import os import re

Re: [PATCH] libdebugger/arm: Fix build for atsam.

whether there should be some (global) volatile arm_switch_reg that has to be read on EXCEPTION_ENTRY_EXC and EXCEPTION_EXIT_EXC on Cortex-M targets? Did the debugger support ever work on some Cortex-M target? Best regards Christian On 15/10/2019 17:09, Christian Mauderer wrote: > -

[PATCH 3/3] bsp/atsam: Use PIO for SC16IS752.

This allows to mix SC16IS752 chips with other interrupts. --- bsps/arm/atsam/include/bsp/sc16is752.h | 3 +++ bsps/arm/atsam/spi/sc16is752.c | 44 ++ 2 files changed, 26 insertions(+), 21 deletions(-) diff --git a/bsps/arm/atsam/include/bsp/sc16is752.h

[PATCH 1/3] bsps/atsam: Improve case for level triggered IRQs.

For level triggered interrupts currently the handler would have been called two times (assuming no one cleared the mask in a handler which would have been bad because the handler couldn't process all other that got cleared by accident). This patch allows the handler only to return if nothing is

[PATCH 2/3] bsp/atsam: Add additional PIO helper.

--- .../contrib/libraries/libchip/source/pio_it.c | 46 ++ bsps/arm/atsam/include/libchip/include/pio_it.h| 13 ++ 2 files changed, 59 insertions(+) diff --git a/bsps/arm/atsam/contrib/libraries/libchip/source/pio_it.c

[PATCH] libdebugger/arm: Fix build for atsam.

--- cpukit/libdebugger/rtems-debugger-arm.c | 9 +++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/cpukit/libdebugger/rtems-debugger-arm.c b/cpukit/libdebugger/rtems-debugger-arm.c index 3d5dea0ab7..a6aaca31f2 100644 --- a/cpukit/libdebugger/rtems-debugger-arm.c +++

Re: Testing the interrupt extension API?

wasteful. > I don't remember the exact controller but I think I once found a watchdog that could only be enabled. Of course Watchdogs cause resets most of the time and not interrupts that can be processed by software. So I'm not sure whether it's relevant. Best regards Christian -- -

Re: BSP for Microchip ATSAMA5D27-SOM1-EK1

On 04/10/2019 20:38, dufa...@hda.com wrote: >> On Oct 4, 2019, at 08:59 , Christian Mauderer wrote: >> >> >> That's great news. I'm quite sure we tried some external oscillators >> back then too without luck. Might I ask which types (drive strength, >> ppm,

Re: BSP for Microchip ATSAMA5D27-SOM1-EK1

On 04/10/2019 14:17, dufa...@hda.com wrote: > > >> On Nov 25, 2018, at 14:45 , Christian Mauderer > <mailto:l...@c-mauderer.de>> wrote: >> >> Thomas mentioned already the bug that has been reported to Microchip. >> Please note that I had two more pro

Re: [PATCH] bsps/beagle: update i2c section

Hello Vijay, thanks for the update. I pushed it. Best regards Christian On 24/09/2019 20:44, Vijay Kumar Banerjee wrote: > --- > user/bsps/arm/beagle.rst | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-) > > diff --git a/user/bsps/arm/beagle.rst b/user/bsps/arm/beagle.rst > index

Re: [PATCH v2] bsps/beagle: register i2c device at initialization

Thanks for the patch. Now it's OK and I pushed it (with an indentation fix). Best regards Christian On 19/09/2019 20:56, Vijay Kumar Banerjee wrote: > > > > On Fri, Sep 20, 2019 at 12:08 AM Christian Mauderer <mailto:l...@c-mauderer.de>> wrote: > > On 19

Re: [PATCH v2] bsps/beagle: register i2c device at initialization

On 19/09/2019 19:48, Vijay Kumar Banerjee wrote: > > > > On Thu, Sep 19, 2019 at 10:05 PM Christian Mauderer <mailto:l...@c-mauderer.de>> wrote: > > Hello Vijay, > > sorry for being picky: What happens if something goes wrong during that

Re: [PATCH v2] bsps/beagle: register i2c device at initialization

Hello Vijay, sorry for being picky: What happens if something goes wrong during that initialization? For example: If the system has a configuration where /dev/i2c0 can't be created. In that case it will just silently fail to create the i2c-0 which maybe leads to odd errors later. There's already

Re: [PATCH 1/1] bsps/beagle: register i2c device at initialization

Hello Vijay, I tried it and the patch works. But there is a point that might could be improved: My application can still call bbb_register_i2c_0(). If I do that it returns an error code. That's better than if it would just initialize the bus twice. But it's not very clear from a user

Re: [PATCH 0/1] Add i2c in Beagle initialization

On 18/09/2019 06:42, Chris Johns wrote: > On 18/9/19 8:03 am, Vijay Kumar Banerjee wrote: >> The following patch adds i2c device initialization in BBB. >> The intention is to have th i2c-0 device created during >> initialization so that the libbsd applications can use the >> RTEMS i2c device on

Re: [PATCH] Add lvgl_hello: Sample Hello world app using littleVGL and libbsd

On 17/09/2019 21:04, Vijay Kumar Banerjee wrote: > > > > On Tue, Sep 17, 2019 at 2:21 PM Christian Mauderer <mailto:l...@c-mauderer.de>> wrote: > > On 17/09/2019 08:46, Vijay Kumar Banerjee wrote: > > > > > > On Th

Re: [PATCH] Add lvgl_hello: Sample Hello world app using littleVGL and libbsd

On 17/09/2019 08:46, Vijay Kumar Banerjee wrote: > > > On Thu, Sep 12, 2019 at 2:37 PM Christian Mauderer > <mailto:christian.maude...@embedded-brains.de>> wrote: > > > > On 12/09/2019 10:28, Vijay Kumar Banerjee wrote: > > > > &g

Re: [PATCH] update rtems_waf

On 17/09/2019 08:51, Vijay Kumar Banerjee wrote: > > > > On Fri, Sep 13, 2019 at 9:00 AM Chris Johns > wrote: > > On 11/9/19 6:14 pm, Vijay Kumar Banerjee wrote: > > ping :) > > Sorry about the delay. OK to push. > > Hi, > Thanks for the review! > Can

Re: [PATCH] Add lvgl_hello: Sample Hello world app using littleVGL and libbsd

On 12/09/2019 10:28, Vijay Kumar Banerjee wrote: > > > > On Wed, Sep 11, 2019 at 4:38 PM Christian Mauderer > <mailto:christian.maude...@embedded-brains.de>> wrote: > > On 11/09/2019 10:48, Vijay Kumar Banerjee wrote: > > > >  H

<    5   6   7   8   9   10   11   12   13   14   >