Hello Punit,
I was working on porting the MicroMonitor (uMon) bootloader to the BBB last
year's GSoC 2015. There is actually still some work that needs to be
done. At the moment, Ethernet functionality and booting application images
still need to be implemented to get it to the point of making i
Hi,
I am ready with RTEMS hello world on Beagle bone black (
https://www.youtube.com/watch?v=FyOHU02bsvw&index=6&list=PL2muodf7ZnYcS18wkilESuJpZGj4mYSMJ)
and interested to improve BBB BSP . Currently I am testing GPIO and will
work on PWM driver for showcasing on my proposal. But I am afraid that
[ Please excuse the delay. It took a while to get
something worth posting sorted out. ]
On 04/03/2016 14:46, Sambeet Panigrahi wrote:
I wanted to build a hello world image of RTEMS using cmake. Can someone
provide me steps for doing so or point me to the right resources ?
I attach a couple
On 11/03/2016 11:49, Joel Sherrill wrote:
On Thu, Mar 10, 2016 at 6:42 PM, Chris Johns mailto:chr...@rtems.org>> wrote:
On 10/03/2016 09:25, Joel Sherrill wrote:
This was used to open, write, and close the VGA console and
/dev/pcicom1 for testing purposes.
Does this
On Thu, Mar 10, 2016 at 6:42 PM, Chris Johns wrote:
> On 10/03/2016 09:25, Joel Sherrill wrote:
>
>> This was used to open, write, and close the VGA console and
>> /dev/pcicom1 for testing purposes.
>>
>
> Does this do the same thing?
>
> [/] # dd if=text.txt of=/dev/pcicom1
>
>
I didn't mean to
On 10/03/2016 09:25, Joel Sherrill wrote:
This was used to open, write, and close the VGA console and
/dev/pcicom1 for testing purposes.
Does this do the same thing?
[/] # dd if=text.txt of=/dev/pcicom1
Chris
___
devel mailing list
devel@rtems.org
h
updates #2577.
For the mcp750 BSP variant without this option sample executables
sizes were as follows:
textdata bss dec hex filename
188997 29656 48361 267014 41306 ticker.exe
150693 26116 44681 221490 36132 minimum.exe
939941 217971 55585 1
updates #2577.
For the gensh2 BSP variant without this option sample executables
sizes were as follows:
textdata bss dec hex filename
6190675506784 76240 129d0 ticker.exe
2408231342876 30092758c minimum.exe
336698 47742 36256
updates #2577.
---
c/src/lib/libbsp/no_cpu/no_bsp/make/custom/no_bsp.cfg | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/c/src/lib/libbsp/no_cpu/no_bsp/make/custom/no_bsp.cfg
b/c/src/lib/libbsp/no_cpu/no_bsp/make/custom/no_bsp.cfg
index 8c98f8b..944ebd9 100644
--- a/c/src
updates #2577.
For the lm32_evr BSP variant without this option sample executables
sizes were as follows:
textdata bss dec hex filename
1957646892 13077 215733 34ab5 ticker.exe
8421222649169 95645 1759d minimum.exe
1077108 82852 26293
updates #2577.
For the gensh4 BSP variant without this option sample executables
sizes were as follows:
textdata bss dec hex filename
75538 106667264 93468 16d1c ticker.exe
2181061663008 309847908 minimum.exe
424370 69762 20476
---
c/src/lib/libbsp/m32c/m32cbsp/make/custom/m32csim.cfg | 7 ++-
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/c/src/lib/libbsp/m32c/m32cbsp/make/custom/m32csim.cfg
b/c/src/lib/libbsp/m32c/m32cbsp/make/custom/m32csim.cfg
index 491f000..9629e48 100644
--- a/c/src/lib/libbsp/m
updates #2577.
Had to add .rtemsroset to the linkcmds following the arm to get it
to link after turning on the per-secton options.
For the v850e1sim BSP variant without this option sample executables
sizes were as follows:
textdata bss dec hex filename
76940
updates #2577.
For the nios2_iss BSP variant without this option sample executables
sizes were as follows:
textdata bss dec hex filename
19869266726068 211432 339e8 ticker.exe
7540819241892 79224 13578 minimum.exe
1044536 36308 1403
updates #2577.
For the epiphany_sim BSP variant without this option sample
executables sizes were as follows:
textdata bss dec hex filename
1987281792 16576900167774201cc ticker.exe
741361148 16702144167774281d4
updates #2577.
For the simsh1 BSP variant without this option sample executables
sizes were as follows:
textdata bss dec hex filename
7398472207036 88240 158b0 ticker.exe
2128463882856 305287740 minimum.exe
368616 17820 36256
updates #2577.
For the generic_or1k BSP variant without this option sample
executables sizes were as follows:
textdata bss dec hex filename
2550441780 33297600335544241f8 ticker.exe
1884841496 33364448335544281fc
updates #2577.
For the niagara BSP variant without this option sample executables
sizes were as follows:
textdata bss dec hex filename
1436162704 2113472 2259792 227b50 ticker.exe
718721720 2105312 2178904 213f58 minimum.exe
9836003128 2126160
updates #2577.
For the milkymist BSP variant without this option sample executables
sizes were as follows:
textdata bss dec hex filename
1011609044 1 123537 1e291 ticker.exe
3088826769169 42733a6ed minimum.exe
592200 90020 2655
updates #2638.
---
c/src/lib/libbsp/i386/pc386/make/custom/pc386.cfg | 4
1 file changed, 4 insertions(+)
diff --git a/c/src/lib/libbsp/i386/pc386/make/custom/pc386.cfg
b/c/src/lib/libbsp/i386/pc386/make/custom/pc386.cfg
index 9f7428d..af912e7 100644
--- a/c/src/lib/libbsp/i386/pc386/make/c
updates #2577.
For the usiii BSP variant without this option sample executables
sizes were as follows:
textdata bss dec hex filename
1806082752 2113472 2296832 230c00 ticker.exe
1141121760 2105312 2221184 21e480 minimum.exe
10413923168 2126160 31
updates #2577.
For the gensh1 BSP variant without this option sample executables
sizes were as follows:
textdata bss dec hex filename
6358676266788 78000 130b0 ticker.exe
2504231702872 31084796c minimum.exe
337626 47818 36260
updates #2577.
For the m32csim BSP variant without this option sample executables
sizes were as follows:
textdata bss dec hex filename
14314811184664 148930 245c2 ticker.exe
55140 584 876 56600dd18 minimum.exe
26863818046598
This series of patches adds per-function section linking to
every BSP that it didn't obviously break. Obviously breaking
was a significant reduction in the size of the C++ samples.
If C++ was not supported on the target, then checking the
size of other samples.
There should now be no BSP custom f
updates #2577.
For the bf537Stamp BSP variant without this option sample
executables sizes were as follows:
textdata bss dec hex filename
7567218849224 86780 152fc ticker.exe
4966816445964 57276dfbc minimum.exe
4749365964 224
For the epiphany_sim BSP variant without this option sample
executables sizes were as follows:
textdata bss dec hex filename
1987281792 16576900167774201cc ticker.exe
741361148 16702144167774281d4 minimum.exe
83
updates #2577.
For the tms570ls3137_hdk BSP variant without this option,
sample executables sizes were as follows:
textdata bss dec hex filename
637601708 260224 325692 4f83c ticker.exe
401971452 260480 302129 49c31 minimum.exe
557376197
updates #2577.
For the TLL6527M BSP variant without this option sample executables
sizes were as follows:
textdata bss dec hex filename
746961660 71544 147900 241bc ticker.exe
487561420 68348 118524 1cefc minimum.exe
4745205740 84792
updates #2577.
For the lpc32xx_mzx BSP variant without this option, sample executable
sizes were as follows:
textdata bss dec hex filename
599201740 3373440833796068203afe4 ticker.exe
246921088 3377030433796084203aff4
updates #2577.
For the lpc17xx_ea_ram BSP variant:
The size of the sample executables without this option were:
textdata bss dec hex filename
63646 1724 3355459233619962200fffa ticker.exe
21634 1088 3359721633619938200f
updates #2577.
For the eZKit533 BSP variant without this option sample executables
sizes were as follows:
textdata bss dec hex filename
7516016289224 86012 14ffc ticker.exe
4915613885964 56508dcbc minimum.exe
4750805708 22440
updates #2577.
For the xilinx_zynq_a9_qemu BSP variant without this option,
sample executables sizes were as follows:
textdata bss dec hex filename
1381921804 268279008 268419004 fffbfbc ticker.exe
1028851564 268314576 268419025
updates #2577.
For the smdk2410 BSP variant without this option,
sample executables sizes were as follows:
textdata bss dec hex filename
979241980 66992576670924803ffc000 ticker.exe
382561400 67052800670924563ffbfe8 mi
updates #2577.
For the stm32f105rc BSP variant without this option,
sample executables sizes were as follows:
textdata bss dec hex filename
614441724 63880 127048 1f048 ticker.exe
393971480 64104 104981 19a15 minimum.exe
1316362360 6
---
c/src/lib/libbsp/arm/atsam/make/custom/atsamv-testsuite.tcfg | 6 ++
1 file changed, 6 insertions(+)
create mode 100644 c/src/lib/libbsp/arm/atsam/make/custom/atsamv-testsuite.tcfg
diff --git a/c/src/lib/libbsp/arm/atsam/make/custom/atsamv-testsuite.tcfg
b/c/src/lib/libbsp/arm/atsam/mak
updates #2577.
NOTE: In contrast to other BSPs, this was built with SMP enabled to
ensure the _smp variant was built properly.
For the realview_pbx_a9_qemu BSP variant without this option,
sample executable sizes were as follows:
textdata bss dec hex file
updates #2577.
For the lpc2362 BSP variant:
The size of the sample executables without this option were:
textdata bss dec he filename
651101820 31008 97938 17e92 ticker.exe
219061088 31712 54706d5b2 minimum.exe
783761908 30912 96 1b25c
updates #2577.
For the lpc40xx_ea_ram BSP variant without this option, sample executable
sizes were as follows:
textdata bss dec hex filename
638941724 3355433633619954200fff2 ticker.exe
218021088 3359705633619946200ff
updates #2577.
For the raspberrypi BSP variant without this option, sample executable
sizes were as follows:
textdata bss dec hex filename
915161724 134080496 134173736 7ff5428 ticker.exe
578091480 134114460 134173749 7ff5435
updates #2577.
For the rtl22xx BSP variant without this option,
sample executables sizes were as follows:
textdata bss dec hex filename
872231820 436320 525363 80433 ticker.exe
279151216 496224 525355 8042b minimum.exe
409638 12704 103008
I'm glad to hear this. The path of least resistance would be to merge
the driver into the pc386 BSP on rtems.git. That bsp tree is currently
undergoing a lot of activity, but once you get your driver merged I
would imagine it is not too hard to maintain. It would also be of
interest to get instruct
On Thu, Mar 10, 2016 at 11:18 AM, Gedare Bloom wrote:
> Joel should comment on this. He has been making a recent effort at
> unifying the PCI implementations in the BSP layer. However, we also
> have the new "drvmgr" framework in cpukit/libdrvmgr that supports PCI
> plus a lot of other devices an
Joel should comment on this. He has been making a recent effort at
unifying the PCI implementations in the BSP layer. However, we also
have the new "drvmgr" framework in cpukit/libdrvmgr that supports PCI
plus a lot of other devices and busses.
On Tue, Mar 8, 2016 at 12:19 PM, animesh pathak wrot
looks ok
On Mon, Mar 7, 2016 at 10:03 AM, Sebastian Huber
wrote:
> This simplifies the handling with local-only objects.
>
> Update #2555.
> ---
> cpukit/posix/include/rtems/posix/timerimpl.h | 4 +-
> cpukit/posix/src/timerdelete.c| 36 +
> cpukit/posix/src/timerge
On Thu, Mar 10, 2016 at 10:35 AM, Joel Sherrill wrote:
>
>
> On Wed, Mar 9, 2016 at 8:15 PM, Gedare Bloom wrote:
>
>> On Wed, Mar 9, 2016 at 5:24 PM, Joel Sherrill wrote:
>> > ---
>> > c/src/lib/libbsp/shared/console.c | 49
>> ---
>> > 1 file changed, 36 in
On Wed, Mar 9, 2016 at 8:15 PM, Gedare Bloom wrote:
> On Wed, Mar 9, 2016 at 5:24 PM, Joel Sherrill wrote:
> > ---
> > c/src/lib/libbsp/shared/console.c | 49
> ---
> > 1 file changed, 36 insertions(+), 13 deletions(-)
> >
> > diff --git a/c/src/lib/libbsp/sh
On Wed, Mar 9, 2016 at 8:21 PM, Gedare Bloom wrote:
> On Wed, Mar 9, 2016 at 5:24 PM, Joel Sherrill wrote:
> > This patch fundamentally results from enhancements to the pc386 BSP
> > to support systems which do **NOT** have the legacy PCI BIOS. The
> > patch adds support for detecting when legac
Joel might answer about the state of the scheduling simulator.
I believe you eventually have to copy-paste your application into a
form, so it is better if you stick to plain text. I don't even know if
you can put images in. You may optionally link to a generated PDF,
too.
On Thu, Mar 10, 2016 at
Hi,
I've been a little busy with my semester end exams and other things
recently. But I have spent time looking into the RTEMS Priority
Scheduler with Processor Affinities and the paper mentioned in the trac
ticket.
At this point, I have a decent understanding of the paper and its
algorithm
Sorry, I clicked on Reply by mistake instead of Reply All. Here is an offline
exchange with Chris.
---
On 10/03/2016 06:39, Vivek Kukreja wrote:
> Hello Chris, Isaac
> I have run the modified hello world example and created a patch for it. I
> cannot access your git server from my institute pro
50 matches
Mail list logo
