Re: [GSOC] GPIO status and I2C start

Hi André, I have a couple of SPI devices to try now. I have the SPI FRAM chip: https://www.adafruit.com/product/1897 and something that could be interesting, an SPI based LCD/touchscreen: https://www.adafruit.com/products/1601 I can also verify that the RTEMS BSP works fine on the new Raspberry

Re: [GSOC] GPIO status and I2C start

Hi Pavel, Thanks for the feedback, we will definitely get the parameter change in when the code is submitted. Alan On Thu, Aug 21, 2014 at 8:20 AM, Pavel Pisa ppisa4li...@pikron.com wrote: Hello everybody, I am happy that the common GPIO API for RTEMS is developed but I have some concerns

TOD/RTC questions

I am testing out the Raspberry Pi I2C interface by implementing a DS1307 RTC driver. I started with the libchip/rtc/ds1375.c driver, since it is very close to the 1307. In the Raspberry Pi BSP, I added code to i2c_init.c to create a raw device node for the RTC device, then I added the

Re: TOD/RTC questions

. Thanks, Alan On 8/28/2014 1:26 PM, Joel Sherrill wrote: On 8/28/2014 12:16 PM, Alan Cudmore wrote: I am testing out the Raspberry Pi I2C interface by implementing a DS1307 RTC driver. I started with the libchip/rtc/ds1375.c driver, since it is very close to the 1307. In the Raspberry Pi BSP

Re: [PATCH] Add GPIO, I2C and SPI support for the RPi BSP

I'm going to try to look at the Pi BSP warnings soon. I can try to help address some of the issues with this patch as well. What is the desired cut off date for 4.11? Alan On Fri, Oct 31, 2014 at 11:41 AM, Pavel Pisa ppisa4li...@pikron.com wrote: Hello Andre, On Friday 31 of October 2014

[PATCH] libbsp ARM: create abort.h to eliminate warnings Created libbsp/arm/shared/abort/abort.h Edited abort.c and simple_abort.c to include abort.h Changed Raspberry Pi BSP to use abort.c instead of

Signed-off-by: Alan Cudmore alan.cudm...@gmail.com --- c/src/lib/libbsp/arm/raspberrypi/Makefile.am | 2 +- c/src/lib/libbsp/arm/shared/abort/abort.c| 28 +--- c/src/lib/libbsp/arm/shared/abort/abort.h| 57 c/src/lib/libbsp/arm/shared/abort

Re: [PATCH] libbsp ARM: create abort.h to eliminate warnings Created libbsp/arm/shared/abort/abort.h Edited abort.c and simple_abort.c to include abort.h Changed Raspberry Pi BSP to use abort.c instea

OK, that makes sense. I'll fix it and resubmit the patch. Any other ARM BSPs? Alan On Nov 3, 2014 2:03 AM, Sebastian Huber sebastian.hu...@embedded-brains.de wrote: On 03/11/14 02:59, Alan Cudmore wrote: -libbsp_a_SOURCES += ../shared/abort/simple_abort.c +libbsp_a_SOURCES += ../shared/abort

Re: [PATCH] Add GPIO, I2C and SPI support for the RPi BSP

This is a tough problem. We have plenty of inexpensive SPI and I2C devices to mix and match with low cost boards such as the Pi and Beaglebone, but it could all become obsolete quickly. If we put a bunch of SPI and I2C drivers in the RTEMS repo, then how do we test and maintain them without

Re: [PATCH] libbsp ARM: create abort.h to eliminate warnings Created libbsp/arm/shared/abort/abort.h Edited abort.c and simple_abort.c to include abort.h Changed Raspberry Pi BSP to use abort.c instea

On 11/5/2014 9:39 AM, Sebastian Huber wrote: On 05/11/14 15:35, Alan Cudmore wrote: If the ARM BSPs that do not use the shared start.S include the code, but never call it, I can remove it, if that is what is best. We could even remove abort.c and simple_abort.c completely. Just let me know

Re: [PATCH] Add GPIO, I2C and SPI support for the RPi BSP

? Thanks, Alan On Wed, Dec 10, 2014 at 7:41 PM, Andre Marques andre.lousa.marq...@gmail.com wrote: On 12/10/14 22:36, Chris Johns wrote: On 11/12/2014 5:27 am, Alan Cudmore wrote: Andre, Thanks for submitting this. I think we need one minor change: Could you remove the include and the call

Re: [PATCH] Add GPIO, I2C and SPI support for the RPi BSP

: On 17/12/2014 8:43 am, Alan Cudmore wrote: Thanks Sebastian and Chris , I will look at converting the Pi I2C code to this new interface. What Zync boards does RTEMS run on? Will it run on the Micro Zed? I have it running on custom hardware. The I2C module is hard IP in the PS so it should run

Re: [PATCH] Add GPIO, I2C and SPI support for the RPi BSP

: On 22/12/14 22:17, Alan Cudmore wrote: Why was the Linux API chosen over FreeBSD? Wouldn't we want to keep going down the *BSD path to provide drivers and libraries? We also looked at the FreeBSD, OpenBSD and NetBSD I2C stuff, but the Linux I2C API appeared to be the best and most widely

Re: BSP requests.

Raspberry Pi times on my PC ( 6 core AMD, 8GB RAM, SSD , Ubuntu 14.04 ) : Standard build system: Bootstrap : 7m4s Configure step: 8s Build: 3m15s Size of RTEMS Tree after bootstrap: 308Mbytes Waf build: configure: ~4s build with tests: 29s Size of RTEMS tree : 188Mbytes

Re: BSP requests.

, 2015 at 10:24 PM, Chris Johns chr...@rtems.org wrote: On 10/02/2015 2:16 pm, Alan Cudmore wrote: Thanks for getting the BSPs in. I wanted to try to compare the old and new build systems on the raspberry Pi 2, but I'm still working on getting the tools to build. Chris may have a clue about

Re: BSP requests.

Thanks for getting the BSPs in. I wanted to try to compare the old and new build systems on the raspberry Pi 2, but I'm still working on getting the tools to build. Chris may have a clue about this: The compiler build finishes ( much faster than the RPI 1 ) but the rtems tools build fails. This

Re: RTEMS for ARM Cortex-M1 ?

Thanks for the info.. so it sounds like a new BSP and some changes to the ARMV7-M code in score. The project will also look at some other fpga based cpus. I'm glad to see the openrisc and microblaze work going on. Alan On Feb 14, 2015 8:29 AM, Sebastian Huber sebastian.hu...@embedded-brains.de

[PATCH] preliminary Raspberry Pi Model 2 support

--- c/src/lib/libbsp/arm/raspberrypi/configure.ac | 8 +++ .../libbsp/arm/raspberrypi/include/raspberrypi.h | 26 +- .../arm/raspberrypi/make/custom/raspberrypi.cfg| 15 + .../arm/raspberrypi/make/custom/raspberrypi.inc| 18 +++

Re: [PATCH] preliminary Raspberry Pi Model 2 support

raspberrypi.cfg - Raspberry Pi 1 specific rule/optons raspberrypi2.cfg -- Raspberry Pi 2 specific rule/options I tested hello, ticker, unlimited, and paranoia on both the Pi ( Model A+ ) and Pi 2. Alan On Sun, Mar 15, 2015 at 12:04 PM, Alan Cudmore alan.cudm...@gmail.com wrote: --- c/src/lib/libbsp/arm

Re: New Pi Quad Core

@rtems.org, Alan Cudmore alan.cudm...@gmail.com Hi I am going to go back on what I said earlier. The online discussion seems to indicate that the BCM2836 has the same peripherals as the BCM2835 on the previous Pi Models. But they are at physical address 0x3F00 rather than the 0x2000

Re: problem when runing rpi sample on gdb simu

Hi, As far as I know, the raspberry Pi binaries will not run on the arm GDB sim. There may be a suitable QEMU based Raspberry Pi simulator. That would be a good option to try. Alan On Wed, Mar 11, 2015 at 9:42 PM, QIAO YANG yangqiao0...@me.com wrote: Hello , I was wondering if the raspberry

Re: GSOC2015 idea Raspberry Pi BSP

On 3/5/2015 11:46 AM, Joel Sherrill wrote: On 3/5/2015 10:40 AM, Alan Cudmore wrote: The list below is still pretty good. Items 1 - 3 were done by Andre last summer, but we still don't have them in the git repository. The RTEMS I2C API has changed and we were going to try to move the I2C

Re: GSOC2015 idea Raspberry Pi BSP

The list below is still pretty good. Items 1 - 3 were done by Andre last summer, but we still don't have them in the git repository. The RTEMS I2C API has changed and we were going to try to move the I2C implementation to the new Linux based API. I still think that having complete Raspberry

Re: [PATCH] [RPI BSP] mailbox

Hi Qiao, Functionally, this code looks good to me. It builds without warnings for the Pi and Pi2, and I was able to make the calls to init the frame buffer on the Pi B+. When you did the frame buffer test, what was your MMU table entry for the mailbox/framebuffer? Thanks, Alan On Apr 19,

Re: [RPI BSP] resume, plan and questions for fb, fbcon gtk

Hi YANG Qiao and fellow mentors, On May 4, 2015, at 7:08 PM, QIAO YANG yangqiao0...@me.com wrote: Hello everyone, Since I haven't yet received any respond of my last mail and I've now got the names of mentors who would instruct me, I create a new thread for a simple resume and post my

Re: [RPI BSP] Framebuffer test

Hi everyone, A while back, I experimented with different graphics demos on the Pi. I integrated some of this code into the RKI image and was able to draw simple graphics under RTEMS: https://www.cl.cam.ac.uk/projects/raspberrypi/tutorials/os/screen01.html There are some other neat demos available

Re: [PATCH] Add hardware FPU flags for Raspberry Pi 2 BSP

This patch adds hardware FPU support for the RPI 2. Builds and runs examples on the Pi2. My RKI image whetstone command is significantly faster. Alan On Tue, Apr 7, 2015 at 4:06 PM, Alan Cudmore alan.cudm...@gmail.com wrote: --- c/src/lib/libbsp/arm/raspberrypi/make/custom/raspberrypi2.cfg

Re: GSoC 2015: Raspberry Pi 2 Support

. I get a feeling it has got to do with this mm_config_table. Updates from the github code and blog might help in further discussion. Link to github code:https://github.com/krohini1593/rtems/tree/rohini Link to Blog Thanks! On Mon, Jun 15, 2015 at 8:29 PM, Alan Cudmore

Re: GSoC 2015: Raspberry Pi 2 Support

from 13 and the no of dhrystones per second also increased. But this is a change only in the config.txt not actually in the boot code. Thanks Rohini On Wed, Jun 3, 2015 at 7:12 AM, Alan Cudmore alan.cudm...@gmail.com wrote: The caches are being enabled on the RPI 1 BSP

Re: Pre-branching Testing Request

Hi Joel, I cloned RSB, built a new copy of ARM and SPARC tools, cloned rtems.git, built for leon3, sis, raspberrypi, and raspberrypi2 I tried a hello and ticker on gdb/sis I ran my RKI image, hello, ticker, paranoia, and unlimited on the Rasberry Pi 2, Raspberry Pi B+, and Raspberry Pi A+ I

Re: RKI Image for Raspberry PI 2

A couple of days ago, I created a new Ubuntu 16.04 virtual machine, built the RSB toolchain ( same version as in your log ) and built the RKI image for sparc/sis, raspberrypi, and raspberrypi2. They all work for me. I used these options to build RTEMS: ../../rtems-git/configure

Re: RKI Image for Raspberry PI 2

. My old firmware did have a config.txt entry : arm_control=0x1000 This did not have an effect on the new firmware tests. Alan > On May 26, 2016, at 3:10 AM, Pavel Pisa <ppisa4li...@pikron.com> wrote: > > Hello Alan, > > thanks for the report. > > On Thursday 2

Re: RKI Image for Raspberry PI 2

nse, since the official firmware is on github as well ) Alan On Wed, May 25, 2016 at 9:30 PM, Alan Cudmore <alan.cudm...@gmail.com> wrote: > A couple of days ago, I created a new Ubuntu 16.04 virtual machine, built > the RSB toolchain ( same version as in your log ) and built the RKI

Re: [PATCH v2 0/7] Raspberry Pi VideoCore support for console on HDMI output

al and graphic output > and direct boot and boot over U-boot. > Reported to work on RPi2 by Alan Cudmore with older > firmware. Problem with newer firmware stays same > as for RTEMS mainline. > Tested by me to run with and without graphic output > on QEMU but due lacks of bcm2835 t

Re: Raspberry pi not working with latest compiler and rtems-git

2 works too, but with the older firmware. I still need to debug that. At least I can get back to trying the recently submitted SPI code. Thanks, Alan > On Jun 21, 2016, at 7:24 PM, Pavel Pisa <ppisa4li...@pikron.com> wrote: > > Hello Alan, > > On Wednesday 22 of Ju

Raspberry pi not working with latest compiler and rtems-git

I refreshed my RSB build and pulled the latest rtems git changes. ( as of today ) and the Raspberry Pi BSPs are not working. I built the sparc/sis RSB and BSP and my tests run fine on that. I will troubleshoot in the next day or so and try to find the error. What is the best ARM simulator BSP to

Re: Raspberry pi not working with latest compiler and rtems-git

Hi Pavel, The HDMI Console! I do have it enabled, so I’m sure that’s it. You saved me a lot of time. Thanks, Alan > On Jun 21, 2016, at 4:53 PM, Pavel Pisa <ppisa4li...@pikron.com> wrote: > > Hello Alan, > > On Tuesday 21 of June 2016 20:41:43 Alan Cudmore wrote: >&

Re: [PATCH 3/3] [raspberrypi] Allow only read or write for SPI 3-wire mode

> On Jun 12, 2016, at 2:45 PM, Jan Sommer wrote: > > --- > c/src/lib/libbsp/arm/raspberrypi/spi/spi.c | 5 + > 1 file changed, 5 insertions(+) > > diff --git a/c/src/lib/libbsp/arm/raspberrypi/spi/spi.c > b/c/src/lib/libbsp/arm/raspberrypi/spi/spi.c > index

Re: Participation in GSoC 2016

Hi Deval, Your proposal looks good. I would suggest adding a step where you build a known BSP with BSD lib support. It will help you become familiar with the development process. You should also address which Raspberry Pi model you will support. Now that there are so many Raspberry Pi models, it

Re: Participation in GSoC 2016

BSP is the one use. I have run some of the SMP examples on qemu with the arm/realview_pbx_a9_qemu_smp BSP and it worked well for me. Alan On Wed, Mar 23, 2016 at 9:03 AM, Deval Shah <deval.ma...@gmail.com> wrote: > On Tue, Mar 22, 2016 at 10:04 PM, Alan Cudmore <alan.cudm...@gmail.

Re: RKI Build Error - rtems_clock_get not available on 4.12

lopment/rtems/4.12/lib/gcc/arm-rtems4.12/6.0.0/../../../../arm-rtems4.12/bin/ld: > failed to merge target specific data of file > /home/dipupo/development/rtems/kernel/builds/b-rpi/arm-rtems4.12/raspberrypi/lib/librtemsbsp.a(libbsp_a-bootcard.o) > > Kindly advice. > > Regards,

Re: GSoC 2016: Low Level Peripherals & SD Card Support for Raspberry Pi

Chris: The Model B V1.2 should work fine. I think I have one of each model Raspberry Pi, so I could test just about any Pi code. I just got my development environment up to date and tested the single core Pi ( A+ ) and Pi Zero. I verified 4.11 and 4.12 work. I also updated my RKI image (

Re: [PATCH 4/4] arm/raspberrypi: add VideoCore framebuffer without initialization

I applied the 4 patches ( I had to use the “patch” command, I could not get “git apply” to work for some reason ) It runs on the Raspberry Pi A+ ( 256MB RAM, single core ) , but it did not boot on the Raspberry Pi 2. I commented out the calls to rpi_init_cmdline() and it booted on the Pi 2

Re: RKI Build Error - rtems_clock_get not available on 4.12

I pushed changes to the RKI repo. I can build it with RTEMS 4.12 tools and the RTEMS Git head now, but I have not tested it. I did not get the link error below. Alan > On Apr 22, 2016, at 1:49 PM, Alan Cudmore <alan.cudm...@gmail.com> wrote: > > Hi, > I’ll take a lo

Re: RKI Image for Raspberry PI 2

Hi, You might need to edit the Makefile for the Raspberry Pi 2. I don't know if passing in the command line variables are enough. The RKI waf build has recently been updated, and I just tested it to make sure it builds. I also have a rki-drivers branch where I am starting to integrate i2c

Re: RKI Image for Raspberry PI 2

m not sure if it is the right tool. > Other option is to use Linux kernel sources for bzImage decompressor > shim. > > It is a question for the other developers and contributors > who worked on RETEM for RPi2 already. I have not been in contact > with them, my last GSoC student and I have tested RTEMS > only on RPi version 1. > > Probably Alan Cudmore knows more about BSP state and testing > on RPi2. > > best wishes, > > Pavel > > > > > > > ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Re: RKI Build Error - rtems_clock_get not available on 4.12

I should be able to update my RKI repository soon.. I’m building the latest tools and RTEMS repo now. Alan > On Apr 21, 2016, at 6:14 AM, Pavel Pisa wrote: > > Hello Habeeb, > > rtems_clock_get() has been obsoleted long time ago > and has been removed in > >

Re: RSB toolchain builds on Windows 10/Windows Subsystem for Linux

Sure. I did not take any notes when I did the first install and build, I'm going to reinstall the linux environment and document what I had to do. Alan On Tue, Aug 9, 2016 at 8:06 PM, Chris Johns <chr...@rtems.org> wrote: > On 09/08/2016 23:51, Alan Cudmore wrote: > >> I t

Re: Updates and Problems on "Raspberry Pi USB and Ethernet Support" Project

Hi Deval, What code do I need to add to try your test? I am using the items git head kernel, and your rtems-libbsd RaspberryPi_USB branch. When I run init01 on my Pi Zero, I get the output below. Alan *** LIBBSD INIT 1 TEST *** nexus0: bcm283x_dwcotg0: on nexus0 usbus0 on bcm283x_dwcotg0

Re: [PATCH 00/10] HYP mode boot and cache manager updates for ARM and RaspberryPi specially.

again with known firmware is a great step. Alan > On Jul 4, 2016, at 10:20 PM, Joel Sherrill <j...@rtems.org> wrote: > > > On Jul 4, 2016 8:40 PM, "Alan Cudmore" <alan.cudm...@gmail.com > <mailto:alan.cudm...@gmail.com>> wrote: >

Re: Porting to a NXP K6x series chip

For the RAM, maybe 128k can be used for the workspace,heap, and initial stack, and the other 128k bank can be used for data. If you get this working, I would not mind trying to port it to the Teensy 3.6 board, which has a similar CPU: https://www.pjrc.com/store/teensy36.html Alan On Fri, Feb

Re: Building toolset for Beaglebone with RSB fails (for me).

I need to do the same for the Pi. I also noticed the Pi BSP Readme is out of date. Joel, where would we put instructions in the Sphinx documentation for the Pi and BB? Alan On Fri, Feb 10, 2017 at 3:24 PM, Joel Sherrill wrote: > GCC does not keep snapshots forever. Ben's

Re: [PATCH 00/10] Raspberry Pi 2 (BCM2836) SMP support

Hi Pavel, I applied your patches, and verified that my apps still work on the Raspberry Pi 1 ( Pi Zero ). Now I am moving to the Pi 2 for some tests. When building for the Pi 2, I need to use the —enable-smp configure switch, correct? When I build the raspberrypi2 BSP with —enable-smp and

Re: [PATCH 00/10] Raspberry Pi 2 (BCM2836) SMP support

> > On Sunday 04 of September 2016 16:38:36 Alan Cudmore wrote: >> Hi Pavel, >> I applied your patches, and verified that my apps still work on the >> Raspberry Pi 1 ( Pi Zero ). Now I am moving to the Pi 2 for some tests. >> >> When building for the P

Re: [PATCH] cpukit: Add nxp-sc16is752 serial device driver

ep 2016 um 20:53 schrieb Alan Cudmore alan.cudm...@gmail.com: > >> I applied this patch and tried building the raspberrypi BSP and got this >> error: >> ../../../../../../../rtems-src/rtems/c/src/../../cpukit/dev/serial/nxp-sc16is752.c:17:27: >> fatal error: bsp

Raspberry Pi libbsd experiments

This message is just FYI. I just wanted to document some of the tests I ran on the Pi with Deval's last GSOC rtems-libbsd branch for the Raspberry Pi. https://github.com/deval-maker/rtems-libbsd/tree/RPi_USB_Ethernet There are definitely some timing issues.. When I run ping01, I need a delay

Re: [PATCH] cpukit: Add nxp-sc16is752 serial device driver

I applied this patch and tried building the raspberrypi BSP and got this error: ../../../../../../../rtems-src/rtems/c/src/../../cpukit/dev/serial/nxp-sc16is752.c:17:27: fatal error: bsp/atsam-spi.h: No such file or directory #include Will this only build for the atsam BSP? I am interested in

[PATCH] Add Windows Subsystem for Linux to RSB Doc

doc/source-builder.txt | 56 +++--- 1 file changed, 44 insertions(+), 12 deletions(-) diff --git a/doc/source-builder.txt b/doc/source-builder.txt index 3bcc397..d676e63 100644 --- a/doc/source-builder.txt +++ b/doc/source-builder.txt @@ -39,7 +39,7 @@

Re: Bacport of ARM cache, RTL and TMS570 to RTEMS 4.11 Was: Simple question about RTL

y Tim Tian > on Zynq BSP more than month ago. I have proposed > 4.11 update series at September 9. > > https://github.com/ppisa/rtems/tree/4.11-arm-update > > Code has been tested by Alan Cudmore and more RPi > versions and correction of Zynq problem has been reported >

Re: Status of libbsd on Pi and Beagle

Libbsd on the Pi still needs some work. To me it looked like it was getting close, but there were some timing issues preventing it from working. I documented my status when I left off here: https://lists.rtems.org/pipermail/devel/2016-September/016092.html

Re: Status of libbsd on Pi and Beagle

<j...@rtems.org> wrote: > > I recall you had luck running on a Pi2. Did anyone ever try a Pi3? > > On Wed, Nov 30, 2016 at 3:23 PM, Alan Cudmore <alan.cudm...@gmail.com > <mailto:alan.cudm...@gmail.com>> wrote: > Libbsd on the Pi still needs some work. To me

Re: BSP for Xilinx Zynq UltraScale+ MPSoC platform

I would like to see both R5 and A53 support. Having RTEMS on the R5 could allow it to be used for OpenAMP communication with the A53. Normally the OpenAMP port for the Xilinx board uses bare metal or FreeRTOS on the R5. For the A53, is there a reason for choosing Aarch32 vs Aarch64 for the RTEMS

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

"set scheduler-locking on" in GDB works! I was able to run RPI2 hello.exe So I consider your instructions ready to go in the repo. More Pi 2 SMP debugging when I get the time.. Thanks! Alan On Thu, Feb 13, 2020 at 12:30 PM G. S. Niteesh wrote: > > On Thu, Feb 13, 2020 at 10:57

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

Hi Niteesh, I have followed your instructions for getting RTEMS running on the Pi 1 and 2. SMP currently is not working on the 2 for me, but that is not a problem with these instructions. I started to try running on QEMU following your instructions but have not been able to get time to complete my

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

, 2020 at 12:12 PM G. S. Niteesh wrote: > > On Thu, Feb 13, 2020 at 10:40 PM Alan Cudmore wrote: >> >> Hi Niteesh, >> I have followed your instructions for getting RTEMS running on the Pi >> 1 and 2. SMP currently is not working on the 2 for me, but that is not >&g

Device Tree Blob for Beaglebone Black?

I have been trying to bring up RTEMS with rtems-libbsd on the beaglebone black (latest master). I can run the regular RTEMS samples on the board, and a couple of the rtems-libbsd testsuite examples run as well. The samples such as ping01 and usb01 get a fatal exception in the function

Re: Device Tree Blob for Beaglebone Black?

with that dtb? I tried master, and then the "5-freebsd-12" branch. Thanks, Alan On Sun, Feb 23, 2020 at 11:32 AM Christian Mauderer wrote: > > On 23/02/2020 17:07, Alan Cudmore wrote: > > I have been trying to bring up RTEMS with rtems-libbsd on the > > beaglebone blac

Re: Device Tree Blob for Beaglebone Black?

wrote: > > > > > On Mon, Feb 24, 2020 at 8:16 PM Alan Cudmore wrote: >> >> Hi Vijay, >> My uEnv.txt was very similar, but I did not have the "fdt addr >> 0x8800" command. But that did not seem to help. I still get a >> fatal exception when tr

Re: Link issue on xilinx_zynq_a9_qemu BSP on rtems-libbsd head

Hi Lou, Did you ever solve this problem? I just tried linking an out of tree program for the beaglebone black BSP and have the same undefined symbols. The testsuite links correctly and the symbols are in the testsuite binaries, but not in libbsd.a doing a grep of the rtems-libbsd source there is

Re: Link issue on xilinx_zynq_a9_qemu BSP on rtems-libbsd head

wrote: > > On 28/02/2020 04:40, Alan Cudmore wrote: > > Hi Lou, > > Did you ever solve this problem? > > I just tried linking an out of tree program for the beaglebone black > > BSP and have the same undefined symbols. The testsuite links correctly > > and the s

Re: Device Tree Blob for Beaglebone Black?

I noticed that the Zephyr RTOS (https://www.zephyrproject.org) uses a device tree based initialization for all of its BSPs. For example, here is the top level device tree source for the Adafruit Trinket M0, which is a very small Atmel Cortex M0 based board:

Re: Device Tree Blob for Beaglebone Black?

ge command? It seems that the RTEMS executable considers the start of RAM to be 0x8000. It might be good to have an image I can try. Thanks for the help! Alan On Mon, Feb 24, 2020 at 12:57 AM Vijay Kumar Banerjee wrote: > > > > On Sun, Feb 23, 2020 at 11:46 PM Alan Cudmore wro

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

I believe we can discard this. I am running all of my recent tests with the 0x20 RAM origin. Thanks, Alan On Tue, Feb 11, 2020 at 2:06 AM Sebastian Huber wrote: > > Hello, > > I guess that after all the Raspberry Pi changes this patch can be discarded? > > On 20/12/2019 07:32, Sebastian

Re: [PATCH v3 2/2] bsp/raspberrypi: Mini UART driver

, 2020 at 10:58 AM G. S. Niteesh wrote: > > On Sun, Feb 16, 2020 at 8:37 PM Alan Cudmore wrote: >> >> Hi Niteesh, >> I can try this patch on my Pi 3. Which BSP should I use? Is there any >> special setup or BSP configuration needed? >> Thanks, >> A

Re: [PATCH v3 2/2] bsp/raspberrypi: Mini UART driver

gt; Thanks, > Niteesh. > > On Sun, Feb 16, 2020 at 10:51 PM Alan Cudmore wrote: >> >> I'm definitely using the kernel_address, but letting the firmware >> decide what image to boot. For me kernel.img is the single core ARM >> images. kernel7.img is used for the raspberry p

Re: [PATCH v3 2/2] bsp/raspberrypi: Mini UART driver

Hi Niteesh, I can try this patch on my Pi 3. Which BSP should I use? Is there any special setup or BSP configuration needed? Thanks, Alan On Sun, Feb 16, 2020 at 2:35 AM G. S. Niteesh wrote: > > Hii, > This is a reminder message since this patch has been unnoticed for a while. > I have tested it

Re: [PATCH v3 2/2] bsp/raspberrypi: Mini UART driver

It > should be at least necessary to define the start address. > > > > > Thanks, > > Niteesh > > > > On Sun, Feb 16, 2020 at 9:58 PM Alan Cudmore > <mailto:alan.cudm...@gmail.com>> wrote: > > > > I tried running my raspberrypi

Re: Raspberry Pi test report

can try the Pi 3 out whenever it is ready. Thanks for all of the recent RPI updates! Alan On Wed, Jan 8, 2020 at 10:26 AM Alan Cudmore wrote: > The Debian Linux variant for the Raspberry Pi (Raspbian) is still 32 bit > for both the Pi 3 and 4, so I would think 32 bit ports would run o

Re: Cheap Small PC for RTEMS testing

I wonder if any of these boards would be compatible: https://up-board.org/ The Up Board that has the same form factor as a raspberry Pi looks like it is $100 US: https://up-shop.org/up-boards/272-up-board.html A google shows this x86 32 bit processor, which is interesting:

Re: Raspberry Pi test report

I can try QEMU. Is there a quick pointer to the QEMU parameters needed to run a Pi2 image? Alan On Tue, Jan 21, 2020 at 3:22 PM Christian Mauderer wrote: > > Does the same error occur on the Pi2 Qemu? In that case you could use it > for proper debugging. > > On 21/01/2020 03:3

RE: Re: Raspberry Pi test report

  From: Christian MaudererSent: Sunday, January 19, 2020 2:49 PMTo: Alan Cudmore; Christian Mauderer; gsnb...@gmail.comCc: rtems-de...@rtems.orgSubject: Re: Raspberry Pi test report On 19/01/2020 20:42, Alan Cudmore wrote:> I tried the latest RTEMS master on my collection of single core R

Re: Re: Raspberry Pi test report

One clue for the Raspberry Pi 2 SMP problem: The regular samples work (hello.exe, ticker.exe, unlimited.exe) If I add #define CONFIGURE_MAXIMUM_PROCESSORS 4 to the init.c for hello, it does not work. On Mon, Jan 20, 2020 at 11:52 AM Alan Cudmore wrote: > Sorry for duplicate or incorrec

RE: Re: Raspberry Pi test report

Sorry for duplicate or incorrectly formatted messages. I need to setup an e-mail client to just send plain text. . See my replies below: From: Christian MaudererSent: Sunday, January 19, 2020 2:49 PMTo: Alan Cudmore; Christian Mauderer; gsnb...@gmail.comCc: rtems-de...@rtems.orgSubject: Re

Re: Raspberry Pi test report

are not occurring? Alan On Mon, Jan 20, 2020 at 6:25 PM Chris Johns wrote: > > On 21/1/20 10:20 am, Alan Cudmore wrote: > > As it turns out the latest RTEMS master may need some of the dtb > > and/or overlay files in the raspberry pi SD card. But the updated > > instruction

Re: Raspberry Pi test report

; What is your debugging setup? It would be really helpful for my future works > on Rpi3. > > Thanks, > Niteesh > > On Tue, 21 Jan, 2020, 7:23 AM Alan Cudmore, wrote: >> >> A little more information on my Raspberry Pi 2 SMP tests: >> >> The BSP startup is gett

Re: Raspberry Pi test report

during initialization. On Mon, Jan 20, 2020 at 5:06 PM Chris Johns wrote: > > On 6/1/20 9:42 am, Alan Cudmore wrote: > > I finally found the time to try the latest RTEMS head on my collection of > > Raspberry Pi models. > > The last time I tried to run RTEMS on a Pi, I had

Re: Raspberry Pi test report

-A allows 32-bit applications to be executed in > a 64-bit OS, and a 32-bit OS to be under the control > of a 64-bit hypervisor." > > So I'm not sure in which situations we will run into problems. Maybe on > interrupts? > > Best regards > > Christian > >

Re: Pi Zero Automated Testing/TFTP/Uboot

Unfortunately, The Raspberry Pi Zero (1.3) does not have a network interface, it just has the MicroSD card and the interfaces exposed on the 40 Pin GPIO header. (SPI, I2C, GPIO, UART, etc) The Raspberry Pi Zero W adds the Wi-Fi/bluetooth module that the RPi 3 has, but I'm guessing that won't work

Raspberry Pi test report

I finally found the time to try the latest RTEMS head on my collection of Raspberry Pi models. The last time I tried to run RTEMS on a Pi, I had trouble with the current version of the Raspberry Pi Firmware, so I had to go back to a specific tag on the Rasberry Pi firmware repository to get RTEMS

Re: RTEMS Release Snapshot: 5.0.0-m2004 (02 Apr 2020)

and support for them. I > wonder if we need a way to assist capturing this for our users. > > You may need to add something to the site's README to provide beginner > steps. > > Chris > > On 2020-04-07 11:44, Alan Cudmore wrote: > > Chris, > > I tested this re

Re: RTEMS Release Snapshot: 5.0.0-m2004 (02 Apr 2020)

Chris, I tested this release on the Raspberry Pi (Zero), Raspberry Pi 2, Beaglebone Black with LibBSD, xilinx_zynq_a9_qemu, and partially on the leon3. ( samples all work on Leon3 QEMU, but I'm still configuring my application ) To help generate tools and BSPs for releases like this, I created a

Re: RTEMS Release Snapshot: 5.0.0-m2004 (02 Apr 2020)

9, 2020 at 7:51 AM Sebastian Huber wrote: > > Hello Alan, > > On 08/04/2020 17:48, Alan Cudmore wrote: > > Regarding the LEON3: I am noticing something with the release that I > > don't understand yet. > > > > I am able to build and run a number of ARM BSPs inc

RE: Re: Improve the Raspberry Pi BSP

This is probably not a comprehensive list, but currently all models except the Pi 4 are working thanks to Niteesh’s work on the uart for the Pi 3 and Zero W. I believe there is some support for GPIO, and I2C.I’m not sure about the state of SPI.There is also support for the graphics console, but I

Re: Improve the Raspberry Pi BSP

wrote: > > > > On Wed, 18 Mar, 2020, 9:03 PM Gedare Bloom, wrote: >> >> On Wed, Mar 18, 2020 at 8:41 AM Denil Verghese wrote: >> > >> > >> > >> > On Wed, 18 Mar, 2020, 7:43 PM Alan Cudmore, wrote: >> >> >> >&g

Re: RTEMS 5.1 pc686 BSP malloc_info problem?

Thanks for all of the help, and thanks for the patch Chris! I was hoping to submit a patch this weekend, so you just gave me back some time :) Alan On Thu, Oct 15, 2020 at 2:08 AM Chris Johns wrote: > > On 13/10/20 4:13 am, Joel Sherrill wrote: > > On Mon, Oct 12, 2020 at 11:15 AM

Re: RTEMS 5.1 pc686 BSP malloc_info problem?

On Thu, Oct 15, 2020 at 11:19 AM Gedare Bloom wrote: > > On Thu, Oct 15, 2020 at 6:35 AM Joel Sherrill wrote: > > > > > > > > On Thu, Oct 15, 2020, 7:15 AM Alan Cudmore wrote: > >> > >> Thanks for all of the help, and thanks for the patch Chris!

Re: RTEMS 5.1 pc686 BSP malloc_info problem?

On Thu, Oct 15, 2020 at 3:03 PM Chris Johns wrote: > > On 16/10/20 5:22 am, Alan Cudmore wrote: > > On Thu, Oct 15, 2020 at 11:19 AM Gedare Bloom wrote: > >> > >> On Thu, Oct 15, 2020 at 6:35 AM Joel Sherrill wrote: > >>> > >>> > &g

Re: RTEMS 5.1 pc686 BSP malloc_info problem?

> but it was very much likely a few days after that when I pushed it. > > --joel >> >> >> On Sun, Oct 4, 2020 at 2:06 PM Alan Cudmore wrote: >> > >> > Hi, >> > I have a problem in RTEMS 5.1 where the pc686 running on QEMU seems to >>

RTEMS 5.1 pc686 BSP malloc_info problem?

Hi, I have a problem in RTEMS 5.1 where the pc686 running on QEMU seems to block or spin when trying to acquire a lock for the malloc_info call. The CPU utilization goes up to 100 (on the QEMU host) leading me to think the calling task is spinning waiting on the lock. Tasks with lower priority

Re: RTEMS 5.1 pc686 BSP malloc_info problem?

ch. Also, thanks for the idea of using RTEMS_DEBUG Sebastian, I need to upgrade my RTEMS toolbox with the latest techniques. Alan On Sun, Oct 11, 2020 at 6:20 PM Chris Johns wrote: > > On 10/10/20 7:35 am, Alan Cudmore wrote: > > After doing a lot of tracing through my application, i

Re: RTEMS 5.1 pc686 BSP malloc_info problem?

into other memory, or is this last write needed before the function updates? If this looks like a bug, should I write a ticket and provide a patch? Thanks, Alan On Mon, Oct 5, 2020 at 1:06 PM Joel Sherrill wrote: > > > > On Mon, Oct 5, 2020 at 11:07 AM Alan Cudmore wrote: >>

  1   2   3   >