Genode on i.MX6Q Sabre Lite

Discussion:

Yevgeny Lavrov

2017-03-01 19:28:12 UTC

Hello

Is there anything from Genode that I can try on i.MX6Q Sabre Lite
development board? So far I've already attempted *log* image that I've
obtained from compiling Genode for i.MX6 based Wandboard. The fastboot
option that gets executed after *$ make run/log *resulted in nothing, so
I've also tried to copy the created images onto SD Card and run them
directly on the board.

Steps:
Once in u-boot prompt

=> fatload mmc 0 0x30000000 image.elf
reading
image.elf

1716880 bytes read in 107 ms (15.3 MiB/s)
=> bootelf 0x30000000
## Starting application at 0x10001000 ...

Then the terminal hangs w/o any output.

Same thing happens when executing uImage
=> fatload mmc 0 0x30000000 uImage
reading uImage
594679 bytes read in 48 ms (11.8 MiB/s)
=> bootm 0x30000000

Terminal hangs once it reaches: Starting kernel ...

Any suggestions on what's wrong?

Thank you

Stefan Kalkowski

2017-03-02 09:53:17 UTC

Permalink

Hi,

well, just because both boards Wandboard and i.MX 6Q Sabre Lite are
using the same system-on-chip (SoC) does not mean they are identical. So
if you are hesitant to start instrumenting the startup code, e.g., via
additional log() calls, you can at least compare the high level
description of the boards. One main issue is which memory slots are used
by which board, and which UART within the SoC is used for the serial
line connector of the board.

One thing that was striking me first when looking at high-level
description of the Sabre Lite board is that is has just 1 GB of RAM,
whereby the Wandboard has 2 GB. This is obviously an issue. When
lowering the RAM size for your setup you potentially will get one step
ahead. But if they are using different UARTs you will not see any log
message anyway. In that case you have to check whether both boards use
the same UART.

Regards
Stefan

Post by Yevgeny Lavrov
Hello
Is there anything from Genode that I can try on i.MX6Q Sabre Lite
development board? So far I've already attempted *log* image that I've
obtained from compiling Genode for i.MX6 based Wandboard. The fastboot
option that gets executed after *$ make run/log *resulted in nothing, so
I've also tried to copy the created images onto SD Card and run them
directly on the board.
Once in u-boot prompt
=> fatload mmc 0 0x30000000 image.elf
reading
image.elf
1716880 bytes read in 107 ms (15.3 MiB/s)
=> bootelf 0x30000000
## Starting application at 0x10001000 ...
Then the terminal hangs w/o any output.
Same thing happens when executing uImage
=> fatload mmc 0 0x30000000 uImage
reading uImage
594679 bytes read in 48 ms (11.8 MiB/s)
=> bootm 0x30000000
Terminal hangs once it reaches: Starting kernel ...
Any suggestions on what's wrong?
Thank you
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
genode-main mailing list
https://lists.sourceforge.net/lists/listinfo/genode-main

--
Stefan Kalkowski
Genode Labs

https://github.com/skalk · http://genode.org/

Yevgeny Lavrov

2017-03-22 07:14:15 UTC

Permalink

Hi

Thanks for the hint. You're correct about the UART, they are different.
Wand uses UART1 = 0x02020000 while Sabre Lite uses UART2 which is 0x021e800.
I tried Genode 15.02 from the institute of Madras:
https://github.com/iitmadras/genode/tree/hw_sabrelite_tz_support, simple
run/printf for now, and it works. I currently use it as a reference. After
comparing board_base.h files for i.MX6 platform, I noticed that
specifically for Sabre Lite the values in the board_base.h from Madras are
set to:

UART_1_IRQ = 57,
UART_1_MMIO_BASE = 0x021e8000,

while for Wandboard, they are the same as in Genode 17.02.

I don't think that adjusting UART will be as simple as copying these values
over to Genode 17.02 /repos/base/include/spec/imx6/drivers/board_base.h So
if there are any other files involved, would you please tell me what those
files are so I know exactly what to look for?

How would I lower the RAM size for my build, and what files are involved?

Thank you

On Thu, Mar 2, 2017 at 4:53 AM, Stefan Kalkowski <

Post by Stefan Kalkowski
Hi,
well, just because both boards Wandboard and i.MX 6Q Sabre Lite are
using the same system-on-chip (SoC) does not mean they are identical. So
if you are hesitant to start instrumenting the startup code, e.g., via
additional log() calls, you can at least compare the high level
description of the boards. One main issue is which memory slots are used
by which board, and which UART within the SoC is used for the serial
line connector of the board.
One thing that was striking me first when looking at high-level
description of the Sabre Lite board is that is has just 1 GB of RAM,
whereby the Wandboard has 2 GB. This is obviously an issue. When
lowering the RAM size for your setup you potentially will get one step
ahead. But if they are using different UARTs you will not see any log
message anyway. In that case you have to check whether both boards use
the same UART.
Regards
Stefan

------------------

--
Stefan Kalkowski
Genode Labs
https://github.com/skalk Â· http://genode.org/
------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
genode-main mailing list
https://lists.sourceforge.net/lists/listinfo/genode-main

Stefan Kalkowski

2017-03-22 10:56:03 UTC

Permalink

Hi,

Post by Yevgeny Lavrov
Hi
Thanks for the hint. You're correct about the UART, they are different.
Wand uses UART1 = 0x02020000 while Sabre Lite uses UART2 which is 0x021e800.
I tried Genode 15.02 from the institute of
Madras:|https://github.com/iitmadras/genode/tree/hw_sabrelite_tz_support
<https://github.com/iitmadras/genode/tree/hw_sabrelite_tz_support>|,
simple run/printf for now, and it works. I currently use it as a
reference. After comparing board_base.h files for i.MX6 platform, I
noticed that specifically for Sabre Lite the values in the board_base.h
UART_1_IRQ = 57,
UART_1_MMIO_BASE = 0x021e8000,
while for Wandboard, they are the same as in Genode 17.02.
I don't think that adjusting UART will be as simple as copying these
values over to Genode 17.02
/repos/base/include/spec/imx6/drivers/board_base.h So if there are any
other files involved, would you please tell me what those files are so I
know exactly what to look for?

well, if you just want to adjust the code to replace the Wandboard
definitions with your i.MX 6Q Sabre Lite, it is actually that simple.
You only have to change the settings in above mentioned file with in the
17.02 release.

If you want to add support of your board beside of the Wandboard
support, you will have to insert a new layer of board definition. But
being in your position I would first change the current Wandboard
settings to see whether it works in general.

Post by Yevgeny Lavrov
How would I lower the RAM size for my build, and what files are involved?

It is the very same file. You have to change the value of RAM0_SIZE.

Regards
Stefan

Post by Yevgeny Lavrov
Thank you
On Thu, Mar 2, 2017 at 4:53 AM, Stefan Kalkowski
Hi,
well, just because both boards Wandboard and i.MX 6Q Sabre Lite are
using the same system-on-chip (SoC) does not mean they are identical. So
if you are hesitant to start instrumenting the startup code, e.g., via
additional log() calls, you can at least compare the high level
description of the boards. One main issue is which memory slots are used
by which board, and which UART within the SoC is used for the serial
line connector of the board.
One thing that was striking me first when looking at high-level
description of the Sabre Lite board is that is has just 1 GB of RAM,
whereby the Wandboard has 2 GB. This is obviously an issue. When
lowering the RAM size for your setup you potentially will get one step
ahead. But if they are using different UARTs you will not see any log
message anyway. In that case you have to check whether both boards use
the same UART.
Regards
Stefan

nothing, so

Post by Yevgeny Lavrov
I've also tried to copy the created images onto SD Card and run them
directly on the board.
Once in u-boot prompt
=> fatload mmc 0 0x30000000 image.elf
reading
image.elf
1716880 bytes read in 107 ms (15.3 MiB/s)
=> bootelf 0x30000000
## Starting application at 0x10001000 ...
Then the terminal hangs w/o any output.
Same thing happens when executing uImage
=> fatload mmc 0 0x30000000 uImage
reading uImage
594679 bytes read in 48 ms (11.8 MiB/s)
=> bootm 0x30000000
Terminal hangs once it reaches: Starting kernel ...
Any suggestions on what's wrong?
Thank you

------------------------------------------------------------------------------

<https://lists.sourceforge.net/lists/listinfo/genode-main>
--
Stefan Kalkowski
Genode Labs
https://github.com/skalk · http://genode.org/
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
genode-main mailing list
https://lists.sourceforge.net/lists/listinfo/genode-main
<https://lists.sourceforge.net/lists/listinfo/genode-main>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
genode-main mailing list
https://lists.sourceforge.net/lists/listinfo/genode-main

--
Stefan Kalkowski
Genode Labs

https://github.com/skalk · http://genode.org/

Yevgeny Lavrov

2017-03-23 03:10:39 UTC

Permalink

I've made the necessary changes to UART variables, and lowered the amount
of RAM by making RAM0_SIZE = 0x20000000. After executing the image.elf on
Sabre Lite, I got the following output:

## Starting application at 0x10001000
...

:virt_alloc: Allocator 0x200f40b4
dump:

Block: [0x1000,0x10001000] size=0x10000000 avail=0x10000000
max_avail=0x10000000

Block: [0x105ad000,0x20001000] size=0xfa54000 avail=0xfa54000
max_avail=0xbfe5b000

Block: [0x201a4000,0x201a5000] size=0x1000 avail=0x0
max_avail=0x0

Block: [0x201a5000,0xe0000000] size=0xbfe5b000 avail=0xbfe5b000
max_avail=0xbfe5b000

Block: [0xf0004000,0xf0005000] size=0x1000 avail=0x0
max_avail=0xbfe5b000

Block: [0xf0007000,0xf0008000] size=0x1000 avail=0x0
max_avail=0x0

Block: [0xf0009000,0xf000a000] size=0x1000 avail=0x0
max_avail=0xffe5000

Block: [0xf000a000,0xfffef000] size=0xffe5000 avail=0xffe5000
max_avail=0xffe5000

=> mem_size=4018765824 (3832 MB) / mem_avail=4018749440 (3832
MB)

:phys_alloc: Allocator 0x200f3048
dump:

Block: [0x1061f000,0x10620000] size=0x1000 avail=0x0
max_avail=0x0

Block: [0x10620000,0x10621000] size=0x1000 avail=0x0
max_avail=0x1f9dd000

Block: [0x10621000,0x10622000] size=0x1000 avail=0x0
max_avail=0x0

Block: [0x10622000,0x10623000] size=0x1000 avail=0x0
max_avail=0x1f9dd000

Block: [0x10623000,0x30000000] size=0x1f9dd000 avail=0x1f9dd000
max_avail=0x1f9dd000

=> mem_size=530452480 (505 MB) / mem_avail=530436096 (505
MB)

:io_mem_alloc: Allocator 0x200f512c
dump:

Block: [0x0,0x1061f000] size=0x1061f000 avail=0x1061f000
max_avail=0xcfffffff

Block: [0x30000000,0xffffffff] size=0xcfffffff avail=0xcfffffff
max_avail=0xcfffffff

=> mem_size=3764514815 (3590 MB) / mem_avail=3764514815 (3590
MB)

:io_port_alloc: Allocator 0x200f6198
dump:

=> mem_size=0 (0 MB) / mem_avail=0 (0
MB)

:irq_alloc: Allocator 0x200f7204
dump:

Block: [0x0,0x1] size=0x1 avail=0x1
max_avail=0x1

Block: [0x2,0x1d] size=0x1b avail=0x1b
max_avail=0x3e2

Block: [0x1e,0x400] size=0x3e2 avail=0x3e2
max_avail=0x3e2

=> mem_size=1022 (0 MB) / mem_avail=1022 (0
MB)

:rom_fs: ROM
modules:

ROM: [101a6000,101a6158)
config

ROM: [10182000,101a2178)
init

ROM: [10105000,101819a4) ld.lib.so

ROM: [101a3000,101a5598)
test-log

kernel
initialized

Genode
17.02

504 MiB RAM assigned to
init

[init -> test-log] hex range:
[0e00,1680)

[init -> test-log] empty hex range: [0abc0000,0abc0000)
(empty!)

[init -> test-log] hex range to limit:
[f8,ff]

[init -> test-log] invalid hex range: [f8,08)
(overflow!)

[init -> test-log] negative hex char:
0xfe

[init -> test-log] positive hex char:
0x02

[init -> test-log] multiarg string: "parent ->
child.7"

[init -> test-log] String(Hex(3)):
0x3

[init -> test-log] Test done.

Is this the desired output from "log"?

Thanks

On Wed, Mar 22, 2017 at 6:56 AM, Stefan Kalkowski <

Post by Yevgeny Lavrov
Hi,

Post by Yevgeny Lavrov
Hi
Thanks for the hint. You're correct about the UART, they are different.
Wand uses UART1 = 0x02020000 while Sabre Lite uses UART2 which is

0x021e800.

Post by Yevgeny Lavrov
I tried Genode 15.02 from the institute of
Madras:|https://github.com/iitmadras/genode/tree/hw_sabrelite_tz_support
<https://github.com/iitmadras/genode/tree/hw_sabrelite_tz_support>|,
simple run/printf for now, and it works. I currently use it as a
reference. After comparing board_base.h files for i.MX6 platform, I
noticed that specifically for Sabre Lite the values in the board_base.h
UART_1_IRQ = 57,
UART_1_MMIO_BASE = 0x021e8000,
while for Wandboard, they are the same as in Genode 17.02.
I don't think that adjusting UART will be as simple as copying these
values over to Genode 17.02
/repos/base/include/spec/imx6/drivers/board_base.h So if there are any
other files involved, would you please tell me what those files are so I
know exactly what to look for?

well, if you just want to adjust the code to replace the Wandboard
definitions with your i.MX 6Q Sabre Lite, it is actually that simple.
You only have to change the settings in above mentioned file with in the
17.02 release.
If you want to add support of your board beside of the Wandboard
support, you will have to insert a new layer of board definition. But
being in your position I would first change the current Wandboard
settings to see whether it works in general.

Post by Yevgeny Lavrov
How would I lower the RAM size for my build, and what files are involved?

It is the very same file. You have to change the value of RAM0_SIZE.
Regards
Stefan

identical. So

Post by Yevgeny Lavrov
if you are hesitant to start instrumenting the startup code, e.g.,

via

Post by Yevgeny Lavrov
additional log() calls, you can at least compare the high level
description of the boards. One main issue is which memory slots are

used

Post by Yevgeny Lavrov
by which board, and which UART within the SoC is used for the serial
line connector of the board.
One thing that was striking me first when looking at high-level
description of the Sabre Lite board is that is has just 1 GB of RAM,
whereby the Wandboard has 2 GB. This is obviously an issue. When
lowering the RAM size for your setup you potentially will get one

step

Post by Yevgeny Lavrov
ahead. But if they are using different UARTs you will not see any log
message anyway. In that case you have to check whether both boards

use

Post by Yevgeny Lavrov
the same UART.
Regards
Stefan

Post by Yevgeny Lavrov
Hello
Is there anything from Genode that I can try on i.MX6Q Sabre Lite
development board? So far I've already attempted *log* image that

I've

Post by Yevgeny Lavrov

Post by Yevgeny Lavrov
obtained from compiling Genode for i.MX6 based Wandboard. The

fastboot

Post by Yevgeny Lavrov

Post by Yevgeny Lavrov
option that gets executed after *$ make run/log *resulted in

nothing, so

Post by Yevgeny Lavrov
I've also tried to copy the created images onto SD Card and run

them

Post by Yevgeny Lavrov

Post by Yevgeny Lavrov
directly on the board.
Once in u-boot prompt
=> fatload mmc 0 0x30000000 image.elf
reading
image.elf
1716880 bytes read in 107 ms (15.3 MiB/s)
=> bootelf 0x30000000
## Starting application at 0x10001000 ...
Then the terminal hangs w/o any output.
Same thing happens when executing uImage
=> fatload mmc 0 0x30000000 uImage
reading uImage
594679 bytes read in 48 ms (11.8 MiB/s)
=> bootm 0x30000000
Terminal hangs once it reaches: Starting kernel ...
Any suggestions on what's wrong?
Thank you

------------------------------------------------------------

------------------

Post by Yevgeny Lavrov

<https://lists.sourceforge.net/lists/listinfo/genode-main>
--
Stefan Kalkowski
Genode Labs
https://github.com/skalk Â· http://genode.org/
------------------------------------------------------------

------------------

Post by Yevgeny Lavrov
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
genode-main mailing list
https://lists.sourceforge.net/lists/listinfo/genode-main
<https://lists.sourceforge.net/lists/listinfo/genode-main>
------------------------------------------------------------

------------------

--
Stefan Kalkowski
Genode Labs
https://github.com/skalk Â· http://genode.org/
------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
genode-main mailing list
https://lists.sourceforge.net/lists/listinfo/genode-main

Stefan Kalkowski

2017-03-23 08:15:39 UTC

Permalink

Hi,

Post by Yevgeny Lavrov
I've made the necessary changes to UART variables, and lowered the
amount of RAM by making RAM0_SIZE = 0x20000000. After executing the
## Starting application at 0x10001000
...
:virt_alloc: Allocator 0x200f40b4
Block: [0x1000,0x10001000] size=0x10000000 avail=0x10000000
max_avail=0x10000000
Block: [0x105ad000,0x20001000] size=0xfa54000 avail=0xfa54000
max_avail=0xbfe5b000
Block: [0x201a4000,0x201a5000] size=0x1000 avail=0x0
max_avail=0x0
Block: [0x201a5000,0xe0000000] size=0xbfe5b000 avail=0xbfe5b000
max_avail=0xbfe5b000
Block: [0xf0004000,0xf0005000] size=0x1000 avail=0x0
max_avail=0xbfe5b000
Block: [0xf0007000,0xf0008000] size=0x1000 avail=0x0
max_avail=0x0
Block: [0xf0009000,0xf000a000] size=0x1000 avail=0x0
max_avail=0xffe5000
Block: [0xf000a000,0xfffef000] size=0xffe5000 avail=0xffe5000
max_avail=0xffe5000
=> mem_size=4018765824 (3832 MB) / mem_avail=4018749440 (3832
MB)
:phys_alloc: Allocator 0x200f3048
Block: [0x1061f000,0x10620000] size=0x1000 avail=0x0
max_avail=0x0
Block: [0x10620000,0x10621000] size=0x1000 avail=0x0
max_avail=0x1f9dd000
Block: [0x10621000,0x10622000] size=0x1000 avail=0x0
max_avail=0x0
Block: [0x10622000,0x10623000] size=0x1000 avail=0x0
max_avail=0x1f9dd000
Block: [0x10623000,0x30000000] size=0x1f9dd000 avail=0x1f9dd000
max_avail=0x1f9dd000
=> mem_size=530452480 (505 MB) / mem_avail=530436096 (505
MB)
:io_mem_alloc: Allocator 0x200f512c
Block: [0x0,0x1061f000] size=0x1061f000 avail=0x1061f000
max_avail=0xcfffffff
Block: [0x30000000,0xffffffff] size=0xcfffffff avail=0xcfffffff
max_avail=0xcfffffff
=> mem_size=3764514815 (3590 MB) / mem_avail=3764514815 (3590
MB)
:io_port_alloc: Allocator 0x200f6198
=> mem_size=0 (0 MB) / mem_avail=0 (0
MB)
:irq_alloc: Allocator 0x200f7204
Block: [0x0,0x1] size=0x1 avail=0x1
max_avail=0x1
Block: [0x2,0x1d] size=0x1b avail=0x1b
max_avail=0x3e2
Block: [0x1e,0x400] size=0x3e2 avail=0x3e2
max_avail=0x3e2
=> mem_size=1022 (0 MB) / mem_avail=1022 (0
MB)
:rom_fs: ROM
ROM: [101a6000,101a6158)
config
ROM: [10182000,101a2178)
init
ROM: [10105000,101819a4) ld.lib.so
<http://ld.lib.so>
ROM: [101a3000,101a5598)
test-log
kernel
initialized
Genode
17.02
504 MiB RAM assigned to
init
[0e00,1680)
[init -> test-log] empty hex range: [0abc0000,0abc0000)
(empty!)
[f8,ff]
[init -> test-log] invalid hex range: [f8,08)
(overflow!)
0xfe
0x02
[init -> test-log] multiarg string: "parent ->
child.7"
0x3
[init -> test-log] Test done.
Is this the desired output from "log"?
Thanks

Exactly!

Regards Stefan

Post by Yevgeny Lavrov
On Wed, Mar 22, 2017 at 6:56 AM, Stefan Kalkowski
Hi,

<https://github.com/iitmadras/genode/tree/hw_sabrelite_tz_support>

Post by Yevgeny Lavrov
<https://github.com/iitmadras/genode/tree/hw_sabrelite_tz_support

<https://github.com/iitmadras/genode/tree/hw_sabrelite_tz_support>>|,

Post by Yevgeny Lavrov
simple run/printf for now, and it works. I currently use it as a
reference. After comparing board_base.h files for i.MX6 platform, I
noticed that specifically for Sabre Lite the values in the board_base.h
UART_1_IRQ = 57,
UART_1_MMIO_BASE = 0x021e8000,
while for Wandboard, they are the same as in Genode 17.02.
I don't think that adjusting UART will be as simple as copying these
values over to Genode 17.02
/repos/base/include/spec/imx6/drivers/board_base.h So if there are any
other files involved, would you please tell me what those files are so I
know exactly what to look for?

well, if you just want to adjust the code to replace the Wandboard
definitions with your i.MX 6Q Sabre Lite, it is actually that simple.
You only have to change the settings in above mentioned file with in the
17.02 release.
If you want to add support of your board beside of the Wandboard
support, you will have to insert a new layer of board definition. But
being in your position I would first change the current Wandboard
settings to see whether it works in general.

Post by Yevgeny Lavrov
How would I lower the RAM size for my build, and what files are involved?

It is the very same file. You have to change the value of RAM0_SIZE.
Regards
Stefan

Post by Yevgeny Lavrov
Thank you
On Thu, Mar 2, 2017 at 4:53 AM, Stefan Kalkowski
Hi,
well, just because both boards Wandboard and i.MX 6Q Sabre

Lite are

Post by Yevgeny Lavrov
using the same system-on-chip (SoC) does not mean they are

identical. So

Post by Yevgeny Lavrov
if you are hesitant to start instrumenting the startup code,

e.g., via

Post by Yevgeny Lavrov
additional log() calls, you can at least compare the high level
description of the boards. One main issue is which memory

slots are used

Post by Yevgeny Lavrov
by which board, and which UART within the SoC is used for the

serial

Post by Yevgeny Lavrov
line connector of the board.
One thing that was striking me first when looking at high-level
description of the Sabre Lite board is that is has just 1 GB

of RAM,

Post by Yevgeny Lavrov
whereby the Wandboard has 2 GB. This is obviously an issue. When
lowering the RAM size for your setup you potentially will get

one step

Post by Yevgeny Lavrov
ahead. But if they are using different UARTs you will not see

any log

Post by Yevgeny Lavrov
message anyway. In that case you have to check whether both

boards use

Post by Yevgeny Lavrov
the same UART.
Regards
Stefan

Post by Yevgeny Lavrov
Hello
Is there anything from Genode that I can try on i.MX6Q Sabre

Lite

Post by Yevgeny Lavrov

Post by Yevgeny Lavrov
development board? So far I've already attempted *log* image

that I've

Post by Yevgeny Lavrov

Post by Yevgeny Lavrov
obtained from compiling Genode for i.MX6 based Wandboard.

The fastboot

Post by Yevgeny Lavrov

Post by Yevgeny Lavrov
option that gets executed after *$ make run/log *resulted in

nothing, so

Post by Yevgeny Lavrov
I've also tried to copy the created images onto SD Card and

run them

Post by Yevgeny Lavrov

------------------------------------------------------------------------------

Post by Yevgeny Lavrov

<https://lists.sourceforge.net/lists/listinfo/genode-main>

Post by Yevgeny Lavrov
<https://lists.sourceforge.net/lists/listinfo/genode-main

<https://lists.sourceforge.net/lists/listinfo/genode-main>>

Post by Yevgeny Lavrov
--
Stefan Kalkowski
Genode Labs
https://github.com/skalk · http://genode.org/
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
genode-main mailing list
https://lists.sourceforge.net/lists/listinfo/genode-main

<https://lists.sourceforge.net/lists/listinfo/genode-main>

Post by Yevgeny Lavrov
<https://lists.sourceforge.net/lists/listinfo/genode-main

<https://lists.sourceforge.net/lists/listinfo/genode-main>>

Post by Yevgeny Lavrov
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
genode-main mailing list
https://lists.sourceforge.net/lists/listinfo/genode-main

<https://lists.sourceforge.net/lists/listinfo/genode-main>
--
Stefan Kalkowski
Genode Labs
https://github.com/skalk · http://genode.org/
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
genode-main mailing list
https://lists.sourceforge.net/lists/listinfo/genode-main
<https://lists.sourceforge.net/lists/listinfo/genode-main>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
genode-main mailing list
https://lists.sourceforge.net/lists/listinfo/genode-main

--
Stefan Kalkowski
Genode Labs

https://github.com/skalk · http://genode.org/

Yevgeny Lavrov

2017-03-27 07:14:26 UTC

Permalink

Excellent :) Thank you for guiding me through it. Is there anything else in
Genode, other than log that I can try on Sabre Lite to make sure that it
works?
My current goal is to get Genode running on top of seL4 micro kernel on ARM
platform. I'm aware that Genode/seL4 support for ARM is scheduled for
August 2017, but maybe there's anything that I can start experimenting with
now?

Thank you

On Thu, Mar 23, 2017 at 4:15 AM, Stefan Kalkowski <

Post by Stefan Kalkowski
Hi,

Exactly!
Regards Stefan

Post by Yevgeny Lavrov
On Wed, Mar 22, 2017 at 6:56 AM, Stefan Kalkowski
Hi,

Post by Yevgeny Lavrov
Hi
Thanks for the hint. You're correct about the UART, they are

different.

Post by Yevgeny Lavrov

Post by Yevgeny Lavrov
Wand uses UART1 = 0x02020000 while Sabre Lite uses UART2 which is

0x021e800.

Post by Yevgeny Lavrov

Post by Yevgeny Lavrov
I tried Genode 15.02 from the institute of
Madras:|https://github.com/iitmadras/genode/tree/hw_

sabrelite_tz_support

Post by Yevgeny Lavrov
<https://github.com/iitmadras/genode/tree/hw_sabrelite_tz_support>

Post by Yevgeny Lavrov
<https://github.com/iitmadras/genode/tree/hw_sabrelite_tz_support

<https://github.com/iitmadras/genode/tree/hw_sabrelite_tz_support

Post by Yevgeny Lavrov
|,
simple run/printf for now, and it works. I currently use it as a
reference. After comparing board_base.h files for i.MX6 platform, I
noticed that specifically for Sabre Lite the values in the

board_base.h

Post by Yevgeny Lavrov

Post by Yevgeny Lavrov
UART_1_IRQ = 57,
UART_1_MMIO_BASE = 0x021e8000,
while for Wandboard, they are the same as in Genode 17.02.
I don't think that adjusting UART will be as simple as copying

these

Post by Yevgeny Lavrov

Post by Yevgeny Lavrov
values over to Genode 17.02
/repos/base/include/spec/imx6/drivers/board_base.h So if there

are any

Post by Yevgeny Lavrov

Post by Yevgeny Lavrov
other files involved, would you please tell me what those files

are so I

Post by Yevgeny Lavrov

Post by Yevgeny Lavrov
know exactly what to look for?

the

Post by Yevgeny Lavrov
17.02 release.
If you want to add support of your board beside of the Wandboard
support, you will have to insert a new layer of board definition. But
being in your position I would first change the current Wandboard
settings to see whether it works in general.

Post by Yevgeny Lavrov
How would I lower the RAM size for my build, and what files are

involved?

Post by Yevgeny Lavrov
It is the very same file. You have to change the value of RAM0_SIZE.
Regards
Stefan

Post by Yevgeny Lavrov
Thank you
On Thu, Mar 2, 2017 at 4:53 AM, Stefan Kalkowski
Hi,
well, just because both boards Wandboard and i.MX 6Q Sabre

Lite are

Post by Yevgeny Lavrov
using the same system-on-chip (SoC) does not mean they are

identical. So

Post by Yevgeny Lavrov
if you are hesitant to start instrumenting the startup code,

e.g., via

Post by Yevgeny Lavrov
additional log() calls, you can at least compare the high level
description of the boards. One main issue is which memory

slots are used

Post by Yevgeny Lavrov
by which board, and which UART within the SoC is used for the

serial

Post by Yevgeny Lavrov
line connector of the board.
One thing that was striking me first when looking at high-level
description of the Sabre Lite board is that is has just 1 GB

of RAM,

Post by Yevgeny Lavrov
whereby the Wandboard has 2 GB. This is obviously an issue.

When

Post by Yevgeny Lavrov

Post by Yevgeny Lavrov
lowering the RAM size for your setup you potentially will get

one step

Post by Yevgeny Lavrov
ahead. But if they are using different UARTs you will not see

any log

Post by Yevgeny Lavrov
message anyway. In that case you have to check whether both

boards use

Post by Yevgeny Lavrov
the same UART.
Regards
Stefan

Post by Yevgeny Lavrov
Hello
Is there anything from Genode that I can try on i.MX6Q Sabre

Lite

Post by Yevgeny Lavrov

Post by Yevgeny Lavrov
development board? So far I've already attempted *log* image

that I've

Post by Yevgeny Lavrov

Post by Yevgeny Lavrov
obtained from compiling Genode for i.MX6 based Wandboard.

The fastboot

Post by Yevgeny Lavrov

Post by Yevgeny Lavrov
option that gets executed after *$ make run/log *resulted in

nothing, so

Post by Yevgeny Lavrov
I've also tried to copy the created images onto SD Card and

run them

Post by Yevgeny Lavrov

------------------------------------------------------------

------------------

Post by Yevgeny Lavrov

Post by Yevgeny Lavrov
Check out the vibrant tech community on one of the world's

most

Post by Yevgeny Lavrov

Post by Yevgeny Lavrov
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
genode-main mailing list
https://lists.sourceforge.net/lists/listinfo/genode-main

<https://lists.sourceforge.net/lists/listinfo/genode-main>

Post by Yevgeny Lavrov
<https://lists.sourceforge.net/lists/listinfo/genode-main

<https://lists.sourceforge.net/lists/listinfo/genode-main>>

Post by Yevgeny Lavrov
--
Stefan Kalkowski
Genode Labs
https://github.com/skalk Â· http://genode.org/
------------------------------------------------------------

------------------

Post by Yevgeny Lavrov

<https://lists.sourceforge.net/lists/listinfo/genode-main>

Post by Yevgeny Lavrov
<https://lists.sourceforge.net/lists/listinfo/genode-main

<https://lists.sourceforge.net/lists/listinfo/genode-main>>

Post by Yevgeny Lavrov
------------------------------------------------------------

------------------

Post by Yevgeny Lavrov

------------------

Post by Yevgeny Lavrov
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
genode-main mailing list
https://lists.sourceforge.net/lists/listinfo/genode-main
<https://lists.sourceforge.net/lists/listinfo/genode-main>
------------------------------------------------------------

------------------

--
Stefan Kalkowski
Genode Labs
https://github.com/skalk Â· http://genode.org/
------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
genode-main mailing list
https://lists.sourceforge.net/lists/listinfo/genode-main

Stefan Kalkowski

2017-03-27 07:41:28 UTC

Permalink

Hi,

Post by Yevgeny Lavrov
Excellent :) Thank you for guiding me through it. Is there anything else
in Genode, other than log that I can try on Sabre Lite to make sure that
it works?

The following run-scripts run successfully each night on the Wandboard,
and therefore should succeed on your board too:

affinity
blk_cache
bomb
clipboard
cpu_quota
cpu_sampler
ds_ownership
fault_detection
fpu
fs_log
init
ldso
libc_getenv
libc_pipe
libc_vfs
libc_vfs_block
libc_vfs_ext2
libc_vfs_fs
libc_vfs_ram
moon
new_delete
nic_loopback
noux
part_blk
pthread
ram_fs_chunk
reconstructible
report_rom
resource_request
resource_yield
rm_fault
rom_blk
rom_filter
rump_ext2
rust
sd_card_bench
signal
sub_rm
synced_interface
trace
util_mmio
xml_generator
xml_node

However, the only test here that deals with hardware beside the CPU or
timer is the sd_card_bench test. There is almost no peripheral device
driver support available for Genode on i.MX6 except the SD-card driver.
So if you want to run more sophisticated setups including graphics,
network, or input you could concentrate on writing or porting related
drivers first.

Best regards
Stefan

Post by Yevgeny Lavrov
My current goal is to get Genode running on top of seL4 micro kernel on
ARM platform. I'm aware that Genode/seL4 support for ARM is scheduled
for August 2017, but maybe there's anything that I can start
experimenting with now?
Thank you
On Thu, Mar 23, 2017 at 4:15 AM, Stefan Kalkowski
Hi,

Post by Yevgeny Lavrov
I've made the necessary changes to UART variables, and lowered the
amount of RAM by making RAM0_SIZE = 0x20000000. After executing the
## Starting application at 0x10001000
...
:virt_alloc: Allocator 0x200f40b4
Block: [0x1000,0x10001000] size=0x10000000 avail=0x10000000
max_avail=0x10000000
Block: [0x105ad000,0x20001000] size=0xfa54000 avail=0xfa54000
max_avail=0xbfe5b000
Block: [0x201a4000,0x201a5000] size=0x1000 avail=0x0
max_avail=0x0
Block: [0x201a5000,0xe0000000] size=0xbfe5b000 avail=0xbfe5b000
max_avail=0xbfe5b000
Block: [0xf0004000,0xf0005000] size=0x1000 avail=0x0
max_avail=0xbfe5b000
Block: [0xf0007000,0xf0008000] size=0x1000 avail=0x0
max_avail=0x0
Block: [0xf0009000,0xf000a000] size=0x1000 avail=0x0
max_avail=0xffe5000
Block: [0xf000a000,0xfffef000] size=0xffe5000 avail=0xffe5000
max_avail=0xffe5000
=> mem_size=4018765824 (3832 MB) / mem_avail=4018749440 (3832
MB)
:phys_alloc: Allocator 0x200f3048
Block: [0x1061f000,0x10620000] size=0x1000 avail=0x0
max_avail=0x0
Block: [0x10620000,0x10621000] size=0x1000 avail=0x0
max_avail=0x1f9dd000
Block: [0x10621000,0x10622000] size=0x1000 avail=0x0
max_avail=0x0
Block: [0x10622000,0x10623000] size=0x1000 avail=0x0
max_avail=0x1f9dd000
Block: [0x10623000,0x30000000] size=0x1f9dd000 avail=0x1f9dd000
max_avail=0x1f9dd000
=> mem_size=530452480 (505 MB) / mem_avail=530436096 (505
MB)
:io_mem_alloc: Allocator 0x200f512c
Block: [0x0,0x1061f000] size=0x1061f000 avail=0x1061f000
max_avail=0xcfffffff
Block: [0x30000000,0xffffffff] size=0xcfffffff avail=0xcfffffff
max_avail=0xcfffffff
=> mem_size=3764514815 (3590 MB) / mem_avail=3764514815 (3590
MB)
:io_port_alloc: Allocator 0x200f6198
=> mem_size=0 (0 MB) / mem_avail=0 (0
MB)
:irq_alloc: Allocator 0x200f7204
Block: [0x0,0x1] size=0x1 avail=0x1
max_avail=0x1
Block: [0x2,0x1d] size=0x1b avail=0x1b
max_avail=0x3e2
Block: [0x1e,0x400] size=0x3e2 avail=0x3e2
max_avail=0x3e2
=> mem_size=1022 (0 MB) / mem_avail=1022 (0
MB)
:rom_fs: ROM
ROM: [101a6000,101a6158)
config
ROM: [10182000,101a2178)
init
ROM: [10105000,101819a4) ld.lib.so <http://ld.lib.so>
<http://ld.lib.so>
ROM: [101a3000,101a5598)
test-log
kernel
initialized
Genode
17.02
504 MiB RAM assigned to
init
[0e00,1680)
[init -> test-log] empty hex range: [0abc0000,0abc0000)
(empty!)
[f8,ff]
[init -> test-log] invalid hex range: [f8,08)
(overflow!)
0xfe
0x02
[init -> test-log] multiarg string: "parent ->
child.7"
0x3
[init -> test-log] Test done.
Is this the desired output from "log"?
Thanks

Exactly!
Regards Stefan

Post by Yevgeny Lavrov
On Wed, Mar 22, 2017 at 6:56 AM, Stefan Kalkowski
Hi,

Post by Yevgeny Lavrov
Hi
Thanks for the hint. You're correct about the UART, they are

different.

Post by Yevgeny Lavrov

Post by Yevgeny Lavrov
Wand uses UART1 = 0x02020000 while Sabre Lite uses UART2

which is 0x021e800.

Post by Yevgeny Lavrov

Post by Yevgeny Lavrov
I tried Genode 15.02 from the institute of

Madras:|https://github.com/iitmadras/genode/tree/hw_sabrelite_tz_support
<https://github.com/iitmadras/genode/tree/hw_sabrelite_tz_support>
<https://github.com/iitmadras/genode/tree/hw_sabrelite_tz_support
<https://github.com/iitmadras/genode/tree/hw_sabrelite_tz_support>>
<https://github.com/iitmadras/genode/tree/hw_sabrelite_tz_support
<https://github.com/iitmadras/genode/tree/hw_sabrelite_tz_support>
<https://github.com/iitmadras/genode/tree/hw_sabrelite_tz_support
<https://github.com/iitmadras/genode/tree/hw_sabrelite_tz_support>>>|,

Post by Yevgeny Lavrov

Post by Yevgeny Lavrov
simple run/printf for now, and it works. I currently use it as a
reference. After comparing board_base.h files for i.MX6

platform, I

Post by Yevgeny Lavrov

Post by Yevgeny Lavrov
noticed that specifically for Sabre Lite the values in the

board_base.h

Post by Yevgeny Lavrov

Post by Yevgeny Lavrov
UART_1_IRQ = 57,
UART_1_MMIO_BASE = 0x021e8000,
while for Wandboard, they are the same as in Genode 17.02.
I don't think that adjusting UART will be as simple as

copying these

Post by Yevgeny Lavrov

Post by Yevgeny Lavrov
values over to Genode 17.02
/repos/base/include/spec/imx6/drivers/board_base.h So if

there are any

Post by Yevgeny Lavrov

Post by Yevgeny Lavrov
other files involved, would you please tell me what those

files are so I

Post by Yevgeny Lavrov

Post by Yevgeny Lavrov
know exactly what to look for?

well, if you just want to adjust the code to replace the Wandboard
definitions with your i.MX 6Q Sabre Lite, it is actually that

simple.

Post by Yevgeny Lavrov
You only have to change the settings in above mentioned file

with in the

Post by Yevgeny Lavrov
17.02 release.
If you want to add support of your board beside of the Wandboard
support, you will have to insert a new layer of board

definition. But

Post by Yevgeny Lavrov
being in your position I would first change the current Wandboard
settings to see whether it works in general.

Post by Yevgeny Lavrov
How would I lower the RAM size for my build, and what files

are involved?

Post by Yevgeny Lavrov
It is the very same file. You have to change the value of

RAM0_SIZE.

Post by Yevgeny Lavrov
Regards
Stefan

Post by Yevgeny Lavrov
Thank you
On Thu, Mar 2, 2017 at 4:53 AM, Stefan Kalkowski
Hi,
well, just because both boards Wandboard and i.MX 6Q Sabre

Lite are

Post by Yevgeny Lavrov
using the same system-on-chip (SoC) does not mean they are

identical. So

Post by Yevgeny Lavrov
if you are hesitant to start instrumenting the startup code,

e.g., via

Post by Yevgeny Lavrov
additional log() calls, you can at least compare the

high level

Post by Yevgeny Lavrov

Post by Yevgeny Lavrov
description of the boards. One main issue is which memory

slots are used

Post by Yevgeny Lavrov
by which board, and which UART within the SoC is used

for the

Post by Yevgeny Lavrov
serial

Post by Yevgeny Lavrov
line connector of the board.
One thing that was striking me first when looking at

high-level

Post by Yevgeny Lavrov

Post by Yevgeny Lavrov
description of the Sabre Lite board is that is has just 1 GB

of RAM,

Post by Yevgeny Lavrov
whereby the Wandboard has 2 GB. This is obviously an

issue. When

Post by Yevgeny Lavrov

Post by Yevgeny Lavrov
lowering the RAM size for your setup you potentially

will get

Post by Yevgeny Lavrov
one step

Post by Yevgeny Lavrov
ahead. But if they are using different UARTs you will

not see

Post by Yevgeny Lavrov
any log

Post by Yevgeny Lavrov
message anyway. In that case you have to check whether both

boards use

Post by Yevgeny Lavrov
the same UART.
Regards
Stefan

Post by Yevgeny Lavrov
Hello
Is there anything from Genode that I can try on i.MX6Q

Sabre

Post by Yevgeny Lavrov
Lite

Post by Yevgeny Lavrov

Post by Yevgeny Lavrov
development board? So far I've already attempted *log*

image

Post by Yevgeny Lavrov
that I've

Post by Yevgeny Lavrov

Post by Yevgeny Lavrov
obtained from compiling Genode for i.MX6 based Wandboard.

The fastboot

Post by Yevgeny Lavrov

Post by Yevgeny Lavrov
option that gets executed after *$ make run/log

*resulted in

Post by Yevgeny Lavrov

Post by Yevgeny Lavrov
nothing, so

Post by Yevgeny Lavrov
I've also tried to copy the created images onto SD

Card and

Post by Yevgeny Lavrov
run them

Post by Yevgeny Lavrov

------------------------------------------------------------------------------

Post by Yevgeny Lavrov

Post by Yevgeny Lavrov
Check out the vibrant tech community on one of the

world's most

Post by Yevgeny Lavrov

Post by Yevgeny Lavrov
engaging tech sites, SlashDot.org!

http://sdm.link/slashdot

Post by Yevgeny Lavrov

Post by Yevgeny Lavrov
_______________________________________________
genode-main mailing list
https://lists.sourceforge.net/lists/listinfo/genode-main

<https://lists.sourceforge.net/lists/listinfo/genode-main>

Post by Yevgeny Lavrov
<https://lists.sourceforge.net/lists/listinfo/genode-main

<https://lists.sourceforge.net/lists/listinfo/genode-main>>

Post by Yevgeny Lavrov

Post by Yevgeny Lavrov
<https://lists.sourceforge.net/lists/listinfo/genode-main

<https://lists.sourceforge.net/lists/listinfo/genode-main>

Post by Yevgeny Lavrov
<https://lists.sourceforge.net/lists/listinfo/genode-main

<https://lists.sourceforge.net/lists/listinfo/genode-main>>>

Post by Yevgeny Lavrov

<https://lists.sourceforge.net/lists/listinfo/genode-main>

Post by Yevgeny Lavrov
<https://lists.sourceforge.net/lists/listinfo/genode-main

<https://lists.sourceforge.net/lists/listinfo/genode-main>>

Post by Yevgeny Lavrov

Post by Yevgeny Lavrov
<https://lists.sourceforge.net/lists/listinfo/genode-main

<https://lists.sourceforge.net/lists/listinfo/genode-main>

Post by Yevgeny Lavrov
<https://lists.sourceforge.net/lists/listinfo/genode-main

<https://lists.sourceforge.net/lists/listinfo/genode-main>>>

Post by Yevgeny Lavrov

<https://lists.sourceforge.net/lists/listinfo/genode-main>

Post by Yevgeny Lavrov
<https://lists.sourceforge.net/lists/listinfo/genode-main

<https://lists.sourceforge.net/lists/listinfo/genode-main>>

Post by Yevgeny Lavrov
--
Stefan Kalkowski
Genode Labs
https://github.com/skalk · http://genode.org/
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
genode-main mailing list
https://lists.sourceforge.net/lists/listinfo/genode-main

<https://lists.sourceforge.net/lists/listinfo/genode-main>

Post by Yevgeny Lavrov
<https://lists.sourceforge.net/lists/listinfo/genode-main

<https://lists.sourceforge.net/lists/listinfo/genode-main>>
------------------------------------------------------------------------------

<https://lists.sourceforge.net/lists/listinfo/genode-main>
--
Stefan Kalkowski
Genode Labs
https://github.com/skalk · http://genode.org/
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
genode-main mailing list
https://lists.sourceforge.net/lists/listinfo/genode-main
<https://lists.sourceforge.net/lists/listinfo/genode-main>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
genode-main mailing list
https://lists.sourceforge.net/lists/listinfo/genode-main

--
Stefan Kalkowski
Genode Labs

https://github.com/skalk · http://genode.org/

Yevgeny Lavrov

2017-03-29 08:53:20 UTC

Permalink

Thank you for providing me this list, Stefan. I ran every single script
from this list on my Sabre Lite, and the majority of them succeeded, except
the following three: bomb, part_blk, and sd_card_bench.
The sd_card_bench gave me the following msg:

[init] child "timer" announces service "Timer"
[init -> sd_card_bench] Error: command timed out
[init -> sd_card_bench] Error: Send_if_cond command failed
[init -> sd_card_bench] Error: Uncaught exception of type
'Sd_card::Host_controller::Detection_failed'
[init -> sd_card_bench] Warning: abort called - thread: ep
[init] child "sd_card_bench" exited with exit value 1

Can it be caused by the wrong values of SDHC_IRQ and SDHC_MMIO_BASE in
imx6/drivers/board_base.h?

Just to make sure. When a test module exits with "exit value 0", does it
mean that the test module succeeded, or something else?

And if it is possible, can you please suggest me a starting point for
Genode/seL4 on i.MX6? I'm currently going through files in repos/base-sel4
directory and trying to make sense out of it. I'm still quite new to ARM
platforms, as well as Genode and seL4 kernel, so I would greatly appreciate
any thoughts or ideas of where to begin.

Thank you

Martin Stein

2017-03-29 13:06:42 UTC

Permalink

Hi Yevgeny,

Post by Yevgeny Lavrov
Thank you for providing me this list, Stefan. I ran every single script
from this list on my Sabre Lite, and the majority of them succeeded,
except the following three: bomb, part_blk, and sd_card_bench.
[init] child "timer" announces service "Timer"
[init -> sd_card_bench] Error: command timed out
[init -> sd_card_bench] Error: Send_if_cond command failed
[init -> sd_card_bench] Error: Uncaught exception of type
'Sd_card::Host_controller::Detection_failed'
[init -> sd_card_bench] Warning: abort called - thread: ep
[init] child "sd_card_bench" exited with exit value 1
Can it be caused by the wrong values of SDHC_IRQ and SDHC_MMIO_BASE in
imx6/drivers/board_base.h?

I don't think that this is the problem. At this point, you have already
reset the component (excludes wrong MMIO base) and IRQs are not needed
for Send_if_cond (we poll for completion). It's more likely that there's
a problem with card initialization. Could you please print out
completion state in [1] like...

error("command timed out irqstat: ", read<Irqstat>());

... and send the result? This might give a glue about whats happened.

Post by Yevgeny Lavrov
Just to make sure. When a test module exits with "exit value 0", does it
mean that the test module succeeded, or something else?

This depends on the surrounding test environment (eg. the parent
component of the test component or the run script that runs the scenario
with the test component). If "Init" is the parent, it simply prints out
"child X exited with value Y". We sometimes use this in run scripts to
determine if a test succeeded, but there's no general heuristic about that.

Post by Yevgeny Lavrov
And if it is possible, can you please suggest me a starting point for
Genode/seL4 on i.MX6? I'm currently going through files in
repos/base-sel4 directory and trying to make sense out of it. I'm still
quite new to ARM platforms, as well as Genode and seL4 kernel, so I
would greatly appreciate any thoughts or ideas of where to begin.

Unfortunately, I'm not that familiar with base-sel4. Maybe someone else
can answer this?

Cheers,
Martin

[1] os/src/drivers/sd_card/spec/imx/driver.cc:132

r***@mpi-sws.org

2017-03-29 17:44:16 UTC

Permalink

Hi all,
I am booting Android on an IMX53 Sabre tablet. The last few lines seen on
serial port as android boots up normally and the screen gets suspended due

warning: `rild' uses 32-bit capabilities (legacy support in use)
pmem: request for physical address of pmem region from process 2262.
request_suspend_state: on (3->0) at 12032459753 (2000-01-03
01:08:28.336600001 UTC)
Unhandled fault: external abort on non-linefetch (0x1018) at 0x40a85054
Unhandled fault: external abort on non-linefetch (0x1018) at 0x40a85054
Unhandled fault: external abort on non-linefetch (0x1018) at 0x41063054
Unhandled fault: external abort on non-linefetch (0x1018) at 0x41100054
Unhandled fault: external abort on non-linefetch (0x1018) at 0x41152054
Unhandled fault: external abort on non-linefetch (0x1018) at 0x411ef054
Unhandled fault: external abort on non-linefetch (0x1018) at 0x41352054
Unhandled fault: external abort on non-linefetch (0x1018) at 0x413ef054
Unhandled fault: external abort on non-linefetch (0x1018) at 0x41452054
Unhandled fault: external abort on non-linefetch (0x1018) at 0x414ef054
Not all allocated memory blocks were freed. Doing it now.
Freeing list entry #0, gpuaddr=84456000
Freeing list entry #2, gpuaddr=84467000
Freeing list entry #3, gpuaddr=84499000
Freeing list entry #6, gpuaddr=8449a000
Freeing list entry #7, gpuaddr=844ba000
Freeing list entry #8, gpuaddr=844da000
Freeing list entry #77, gpuaddr=844ea000
Freeing list entry #84, gpuaddr=8449c000
request_suspend_state: mem (0->3) at 75724147503 (2000-01-03
01:09:32.028284751 UTC)
isl29023 2-0044: isl29023 early_syspend
mag3110 1-000e: mag3110 early_syspend
PM: Syncing filesystems ... done.
dvfs: disable dvfs before suspend
Freezing user space processes ... (elapsed 0.01 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
Suspending console(s) (use no_console_suspend to debug)

Now I wanted to trap external aborts to monitor. In initialization of

mrc p15, 0, r4, c1, c1, 0
mcr p15, 0, r4, c1, c1, 0
.global tz_monitor
.align 5
@ Monitor

An example exception handler function just prints a statement and looks as

.global _monitor_prefetch
push {lr}
bl monitor_prefetch
pop {lr}
movs pc, lr
void monitor_prefetch(void) {
printf("In Monitor's Prefetch Handler\n");
}

But the external abort as seen with the Android boot previously does not
come to the monitor (the print statement doesn't happen). I get the

warning: `rild' uses 32-bit capabilities (legacy support in use)
pmem: request for physical address of pmem region from process 2262.
request_suspend_state: on (3->0) at 12005333628 (2000-01-03
00:38:52.322241626 UTC)
Bad mode in prefetch abort handler detected
Internal error: Oops - bad mode: 0 [#1] PREEMPT
last sysfs file: /sys/devices/platform/pwm-backlight.0/backlight/pwm-
backlight.0/brightness
CPU: 0 Not tainted (2.6.35.3-01265-g8f56f17 #6)
PC is at 0x77802570
LR is at 0xafd0bf6c
pc : [<77802570>] lr : [<afd0bf6c>] psr: 200001d6
sp : ce0e7fb0 ip : 8151c780 fp : 00000001
r10: 00000000 r9 : 40a85000 r8 : 00000002
r7 : 4090ae64 r6 : 8151c890 r5 : 00000018 r4 : 40207000
r3 : 40a85000 r2 : 00000001 r1 : 60000010 r0 : 00000000
Flags: nzCv IRQs off FIQs off Mode UK6_32 ISA ARM Segment user
Control: 10c5387d Table: 83668019 DAC: 00000015
Process Binder Thread # (pid: 2307, stack limit = 0xce0e62e8)
Stack: (0xce0e7fb0 to 0xce0e8000)
7fa0: 00000000 60000010 00000001
40a85000
7fc0: 40207000 00000018 8151c890 4090ae64 00000002 40a85000 00000000
00000001
7fe0: 8151c780 ce0e7fb0 afd0bf6c 77802570 200001d6 ffffffff ffc75a9a
dfd4eed7
Code: bad PC value
---[ end trace d8447dd37d1d45d8 ]---
Kernel panic - not syncing: Fatal exception
[<c003e58c>] (unwind_backtrace+0x0/0xf0) from [<c04862f0>]
(panic+0x6c/0xe0)
[<c04862f0>] (panic+0x6c/0xe0) from [<c003d420>] (die+0x2b4/0x304)
[<c003d420>] (die+0x2b4/0x304) from [<c003d4ac>] (bad_mode+0x3c/0x5c)
[<c003d4ac>] (bad_mode+0x3c/0x5c) from [<afd0bf6c>] (0xafd0bf6c)

Do I need some other setting to trap the abort to monitor mode? Eventually
I will set CSU to make peripherals like I2C0/IPU secure and trap and
emulate aborts there. But I need to do this first step of directing an
abort to a monitor handler function. Can someone please help?

Thanks!
Riju

Alexander Boettcher

2017-03-30 08:43:25 UTC

Permalink

Hi,

Post by Martin Stein

Unfortunately, I'm not that familiar with base-sel4. Maybe someone else
can answer this?

--
Alexander Boettcher
Genode Labs

http://www.genode-labs.com - http://www.genode.org

Genode Labs GmbH - Amtsgericht Dresden - HRB 28424 - Sitz Dresden
Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

Yevgeny Lavrov

2017-04-03 02:49:00 UTC

Permalink

Hi,

Thanks for the hints. I managed to solve the sd_card_bench issue.
I've tried to print out completion state as Martin suggested by making the
following changes to:
<genode-dir>/repos/os/src/drivers/sd_card/spec/imx/driver.cc

driver.cc : line 131: error("command timed out irqstat: ",
Mmio::read<Irqstat>());

And got the following output during run: â[init -> sd_card_bench] Error:
command timed out irqstat: 0â
I assumed that Genode is unable to locate the device for some reason, and
decided to see if the same approach that worked for the UART would work
here as well.
Went back to /repos/base/include/spec/imx6/drivers/board_base.h and
adjusted the SDHC variables to these values:

/* SD host controller */
SDHC_IRQ = 56,
SDHC_MMIO_BASE = 0x02198000,

This did the trick and sd_card_bench successfully executed :)

On seL4 side I got this far:
As it was suggested, I took files from base-sel4/lib/mk/spec/x86_32/
modified them, and placed them in newly created imx6 folder. These changes
got me from:

checking library dependencies...
Library-description file startup-sel4.mk is missing
Library-description file syscall-sel4.mk is missing
make[2]: *** No rule to make target 'startup-sel4.lib', needed by
'base-sel4-common.lib'. Stop.

to the point where build process hits:

Library core-sel4
COMPILE capability_space.o

The error occurs once the build process hits one of the files within this
directory: base-sel4/src/core and these files appear to be Genode specific.
I was able to clear out errors that are caused by wrong object types, but I
hit dead end once I reach io_port_session_support.c

Since I'm interested in something as basic as Hello World msg for now, do I
need all the files from base-sel4/src/core directory or I may exclude some
them?

Thanks

On Thu, Mar 30, 2017 at 4:43 AM, Alexander Boettcher <

Post by Alexander Boettcher
Hi,

Post by Martin Stein

Unfortunately, I'm not that familiar with base-sel4. Maybe someone else
can answer this?

Look for any x86 specific configuration/files in base-sel4 and come up
with imx6 specific ones, I would guess. E.g. if you search for x86* you
find in
repos/base-sel4/lib/mk/spec/x86_32
several files which setup the sel4 kernel for x86 (build the sel4
kernel, sel4 kernel bindings etc.). This must be (probably) also added to
repos/base-sel4/lib/mk/spec/imx6/
(somehow similar as base-hw does).
For example in repos/base-sel4/lib/mk/spec/x86_32/kernel-sel4.mk the
seL4 kernel is build for x86_32. Here you have to come up with a
kernel-sel4.mk in the imx6 folder which builds the sel4 kernel for
imx6/Sabre lite. How this is exactly is done, you have to check the
documentation of seL4.
Cheers,
Alex.
--
Alexander Boettcher
Genode Labs
http://www.genode-labs.com - http://www.genode.org
Genode Labs GmbH - Amtsgericht Dresden - HRB 28424 - Sitz Dresden
GeschÃ€ftsfÃŒhrer: Dr.-Ing. Norman Feske, Christian Helmuth
------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
genode-main mailing list
https://lists.sourceforge.net/lists/listinfo/genode-main

Alexander Boettcher

2017-04-03 08:36:48 UTC

Permalink

Hi,

Post by Yevgeny Lavrov
This did the trick and sd_card_bench successfully executed :)

Good !

Post by Yevgeny Lavrov
The error occurs once the build process hits one of the files within this
directory: base-sel4/src/core and these files appear to be Genode specific.
I was able to clear out errors that are caused by wrong object types, but I
hit dead end once I reach io_port_session_support.c

Hinnerk van Bruinehsen

2017-04-03 10:41:48 UTC

Permalink

Hi,

I have done some testing to get seL4 and Genode boot on an ARM device
(AM335x based). I have a branch on github that got into the Genode
userland code, but it sadly isn't that up to date (from december 2016).
I just broke x86 support for testing purposes (as it is more or less
hard coded in Genode's seL4 code).

https://github.com/N8Fear/genode/tree/sel4-am335x

There are a few more things to consider:
- my board uses barebox as bootloader (an uboot fork, so I guess much
would work for uboot, too)
- I also used a somewhat hacked version of seL4's elfloader to get an
image, that combines the seL4 kernel and the genode userland to use
with uboot. I guess it also may work using the Genode image as
initramfs, but I never really tried that.
- The branch referenced above does get into the Genode userland, but
fails relatively early on due to a cap fault. (You can read the
simple_root_task.txt from the documentation directory in base-sel4 -
there is a part about GS-relative addressing of a
thread-local-storage facility. My guess is, that that's the point
were it fails on my branch).

I guess the real question is, considering that Genode+seL4 on ARM is
planned for this year, how much work makes sense. Especially because it
would really only make sense, if one has a concept to split the code in
a way that allows to build seL4 for different architectures at the same
time, which essentially means, that the code could be upstreamed. To get
that done, likely would required a certain ammount of coordination with
upstream...

WKR Hinnerk

Post by Alexander Boettcher
Hi,

Post by Yevgeny Lavrov
This did the trick and sd_card_bench successfully executed :)

Good !

io_ports are a speciality on x86, so on ARM you have to skip the
io_port* files completely. (On base-hw, which runs x86 and arm, look
there into the mk files, where the io_port* files depended on the
platform are added or not).
Cheers,
Alex.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
genode-main mailing list
https://lists.sourceforge.net/lists/listinfo/genode-main

Alexander Boettcher

2017-04-04 08:29:54 UTC

Permalink

Hi,

Post by Hinnerk van Bruinehsen
I have done some testing to get seL4 and Genode boot on an ARM device
(AM335x based). I have a branch on github that got into the Genode

Nice !

Post by Hinnerk van Bruinehsen
I guess the real question is, considering that Genode+seL4 on ARM is
planned for this year, how much work makes sense. Especially because it
would really only make sense, if one has a concept to split the code in
a way that allows to build seL4 for different architectures at the same
time, which essentially means, that the code could be upstreamed. To get
that done, likely would required a certain ammount of coordination with
upstream...

feel invited to open up a feature issue on github and we may discuss and
streamline patches in a clean way.

It's right that we plan seL4 and ARM support, but as said on the roadmap
website, nothing is set in stone (e.g. because of high prior
commissioned contract work which may come in at any point in time). So,
I would not bet on this to happen, at least not bet on the schedule ...

Additionally, we would only add support to SoCs we see a need for, have
physical access to and therefore may also test. The whole zoo of ARM
SoCs can't be managed by GenodeLabs alone. That means specifically, that
your desired board may not be part of this line of work.

Why I'm talking about this ? If you have a need for Genode/seL4 and have
already something running, please open up a feature issue on github and
we will see how we get it upstream. Just waiting for things to happen is
the worst thing we can do, community wise.

Cheers,

Alex.

Martin Stein

2017-04-03 08:49:33 UTC

Permalink

Hey Yevgeny.

Post by Yevgeny Lavrov
Hi,
Thanks for the hints. I managed to solve the sd_card_bench issue.
I've tried to print out completion state as Martin suggested by making
<genode-dir>/repos/os/src/drivers/sd_card/spec/imx/driver.cc
driver.cc : line 131: error("command timed out irqstat: ",
Mmio::read<Irqstat>());
command timed out irqstat: 0”
I assumed that Genode is unable to locate the device for some reason,
and decided to see if the same approach that worked for the UART would
work here as well.
Went back to /repos/base/include/spec/imx6/drivers/board_base.h and
/* SD host controller */
SDHC_IRQ = 56,
SDHC_MMIO_BASE = 0x02198000,
This did the trick and sd_card_bench successfully executed :)

Cool :)

Eventhough, I wonder that you were able to successfully do a reset with
the other parameters. But maybe there is a second controller at
0x02190000 without a card inserted.

Cheers,
Martin

Stefan Kalkowski

2017-04-04 09:26:07 UTC

Permalink

Post by Martin Stein
Hey Yevgeny.

Cool :)
Eventhough, I wonder that you were able to successfully do a reset with
the other parameters. But maybe there is a second controller at
0x02190000 without a card inserted.

In fact, the i.MX6 SoCs have even four different SDHC controllers.
Obviously, the card-slot of the i.MX6Q Sabre Lite is connected to a
different controller than the one of the Wandboard.

@m-stein: sorry, I forgot that point when I asked you for support to
investigate this

Regards
Stefan

Post by Martin Stein
Cheers,
Martin
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
genode-main mailing list
https://lists.sourceforge.net/lists/listinfo/genode-main

--
Stefan Kalkowski
Genode Labs

https://github.com/skalk · http://genode.org/

Yevgeny Lavrov

2017-04-10 05:42:53 UTC

Permalink

Thanks for the support, and thank you Hinnerk for sharing your GitHub
branch, so far it was very useful to me when dealing with some errors.
I've looked into .mk files from base-hw and yes, the io_port* files only
get added to the core-hw.mk if one compiles for x86_64, so I've excluded
these files from core-sel4.mk file.
After excluding io_port* files, and clearing out seL4 object type related
errors (e.g seL4_X86_4K) it got me through compile phase. The compiled
image hangs on ## Starting application at 0xe0000000 âŠ which appears to be
an invalid address. All my previous apps were starting at 0x10001000. I've
assumed that this is because I didn't include platform specific files that
can be found in base-hw/src/core/spec and base-hw/src/core/include/spec
directories.

Copying spec files from base-hw dir to my base-seL4/src/core/ directory and
including them into my build didn't give me anything so far. When
attempting to include them into my core-seL4.mk file normally resulted in
one or the other file missing or doesn't exist error. But at least it
improved my understanding of Genode's make process.

For now I just want to confirm one thing about core-seL4.mk file. Want to
make sure that I understand everything correctly.
The files that are included through SRC_CC in core-seL4.mk. Not all of them
are present in base-seL4/src/core. So, where does it pull the files that
are not in base-sel4/src/core? Do they come from repos/base/src/core
directory?

On Tue, Apr 4, 2017 at 5:26 AM, Stefan Kalkowski <

Post by Stefan Kalkowski

Post by Martin Stein
Hey Yevgeny.

Post by Yevgeny Lavrov
Hi,
Thanks for the hints. I managed to solve the sd_card_bench issue.
I've tried to print out completion state as Martin suggested by making
<genode-dir>/repos/os/src/drivers/sd_card/spec/imx/driver.cc
driver.cc : line 131: error("command timed out irqstat: ",
Mmio::read<Irqstat>());
command timed out irqstat: 0â
I assumed that Genode is unable to locate the device for some reason,
and decided to see if the same approach that worked for the UART would
work here as well.
Went back to /repos/base/include/spec/imx6/drivers/board_base.h and
/* SD host controller */
SDHC_IRQ = 56,
SDHC_MMIO_BASE = 0x02198000,
This did the trick and sd_card_bench successfully executed :)

Cool :)
Eventhough, I wonder that you were able to successfully do a reset with
the other parameters. But maybe there is a second controller at
0x02190000 without a card inserted.

In fact, the i.MX6 SoCs have even four different SDHC controllers.
Obviously, the card-slot of the i.MX6Q Sabre Lite is connected to a
different controller than the one of the Wandboard.
@m-stein: sorry, I forgot that point when I asked you for support to
investigate this
Regards
Stefan

Post by Martin Stein
Cheers,
Martin
------------------------------------------------------------

------------------

Post by Martin Stein
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
genode-main mailing list
https://lists.sourceforge.net/lists/listinfo/genode-main

--
Stefan Kalkowski
Genode Labs
https://github.com/skalk Â· http://genode.org/
------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
genode-main mailing list
https://lists.sourceforge.net/lists/listinfo/genode-main

Norman Feske

2017-04-10 06:49:10 UTC

Permalink

Hello Yevgeny

Post by Yevgeny Lavrov
For now I just want to confirm one thing about core-seL4.mk file. Want
to make sure that I understand everything correctly.
The files that are included through SRC_CC in core-seL4.mk. Not all of
them are present in base-seL4/src/core. So, where does it pull the files
that are not in base-sel4/src/core? Do they come from
repos/base/src/core directory?

--
Dr.-Ing. Norman Feske
Genode Labs

http://www.genode-labs.com · http://genode.org

Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden
Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

Yevgeny Lavrov

2017-05-09 23:33:26 UTC

Permalink

Hi,

I kept experimenting with Genode/seL4 and I ran into the following issue
that I can't solve. I have no more problems compiling Genode with seL4
kernel, but my build always ends with a lot of "undefined reference" errors:
Ex:

genode build completed
using 'ld-sel4.lib.so' as 'ld.lib.so'
using 'sel4/core.o' as 'core.o'
core/sel4/core.o: In function `error<char const (&)[53], char const
(&)[18], void*&, char const (&)[35], void*, char const (&)[2]>':
../genode-17.02/repos/base/include/base/log.h:131: undefined reference to
`Genode::Log::log()'
core/sel4/core.o: In function `warning<long unsigned int&, char const
(&)[21], char const*, char const (&)[31]>':
../genode-17.02/repos/base/include/base/log.h:119: undefined reference to
`Genode::Log::log()'
core/sel4/core.o: In function `error<char const (&)[19],
Genode::Avl_node_base*&, char const (&)[22]>':
../genode-17.02/repos/base/include/base/log.h:131: undefined reference to
`Genode::Log::log()'
.......

It looks like the linking between Genode & seL4 fails at some point. I
think that this is caused by /<genode-dir>/tool/run/boot_dir/sel4 file, so
I'm trying to change it so that it looks more like run/boot_dir/hw
Am I on the right track, or is there something else that I'm missing?

Thank you

Post by Norman Feske
Hello Yevgeny

the files are obtained according to the 'vpath' definitions at the end
of the core-sel4.mk file. If you want to inspect the build steps in
detail, I recommend you to append the "VERBOSE=" argument when invoking
make. E.g.,
make core/sel4 VERBOSE=
Cheers
Norman
--
Dr.-Ing. Norman Feske
Genode Labs
http://www.genode-labs.com Â· http://genode.org
Genode Labs GmbH Â· Amtsgericht Dresden Â· HRB 28424 Â· Sitz Dresden
GeschÃ€ftsfÃŒhrer: Dr.-Ing. Norman Feske, Christian Helmuth
------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
genode-main mailing list
https://lists.sourceforge.net/lists/listinfo/genode-main

Yevgeny Lavrov

2017-06-16 06:39:34 UTC

Permalink

Hi

Are there any suggestions on what might be causing linking between seL4 and
Genode to fail?
It fails once it reaches <genode>/tool/run/run: proc build_core {lib
modules target link_address} with "undefined reference" errors.

# link final image
exec [cross_dev_prefix]g++ {*}$arch -nostdlib {*}[core_ld_opts] \
-Wl,-z -Wl,max-page-size=0x1000 \
-Wl,-Ttext=$link_address -Wl,-gc-sections \
-Wl,-nostdlib -Wl,--whole-archive
-Wl,--start-group \
$lib [run_dir].boot_modules.o
-Wl,--no-whole-archive \
-Wl,--end-group $libgcc -o $target

Do I need to add bootstrap to my build? The similar way it is done when
compiling Genode with hw kernel?
I would really appreciate any suggestions or ideas on where to look.

Thank you

Post by Yevgeny Lavrov
Hi,
I kept experimenting with Genode/seL4 and I ran into the following issue
that I can't solve. I have no more problems compiling Genode with seL4
genode build completed
using 'ld-sel4.lib.so' as 'ld.lib.so'
using 'sel4/core.o' as 'core.o'
core/sel4/core.o: In function `error<char const (&)[53], char const
../genode-17.02/repos/base/include/base/log.h:131: undefined reference to
`Genode::Log::log()'
core/sel4/core.o: In function `warning<long unsigned int&, char const
../genode-17.02/repos/base/include/base/log.h:119: undefined reference to
`Genode::Log::log()'
core/sel4/core.o: In function `error<char const (&)[19],
../genode-17.02/repos/base/include/base/log.h:131: undefined reference to
`Genode::Log::log()'
.......
It looks like the linking between Genode & seL4 fails at some point. I
think that this is caused by /<genode-dir>/tool/run/boot_dir/sel4 file,
so I'm trying to change it so that it looks more like run/boot_dir/hw
Am I on the right track, or is there something else that I'm missing?
Thank you
On Mon, Apr 10, 2017 at 2:49 AM, Norman Feske <

Post by Norman Feske
Hello Yevgeny

Alexander Boettcher

2017-06-19 10:44:58 UTC

Permalink

Hello,

Post by Yevgeny Lavrov
Are there any suggestions on what might be causing linking between seL4 and
Genode to fail?
It fails once it reaches <genode>/tool/run/run: proc build_core {lib
modules target link_address} with "undefined reference" errors.

Which "undefined references" ? If it is still the Log* methods, see below.

Post by Yevgeny Lavrov
Do I need to add bootstrap to my build? The similar way it is done when
compiling Genode with hw kernel?
I would really appreciate any suggestions or ideas on where to look.

no, bootstrap of hw is a wrong direction. (It's specific for hw and
can't be used with any other kernel.)

Post by Yevgeny Lavrov

Post by Yevgeny Lavrov
genode build completed
using 'ld-sel4.lib.so' as 'ld.lib.so'
using 'sel4/core.o' as 'core.o'
core/sel4/core.o: In function `error<char const (&)[53], char const
../genode-17.02/repos/base/include/base/log.h:131: undefined reference to
`Genode::Log::log()'
core/sel4/core.o: In function `warning<long unsigned int&, char const
../genode-17.02/repos/base/include/base/log.h:119: undefined reference to
`Genode::Log::log()'
core/sel4/core.o: In function `error<char const (&)[19],
../genode-17.02/repos/base/include/base/log.h:131: undefined reference to
`Genode::Log::log()'
.......

Log::log, e.g., is implemented in repos/base/src/lib/base/default_log.cc
and normally compiled by repos/base-sel4/lib/mk/core-sel4.mk.

It seems that it is missing. Please check that you compile and link the
file to core. Check that the symbol actually shows up as symbol in
core.o, e.g. by examining the output of "readelf -s
build/<arch>/core/sel4/core.o".

Cheers,

l***@critical.com

2017-06-21 19:41:01 UTC

Permalink

Hi, Alex

Yes, default_log.cc is listed in core-sel4.mk file. However, I've recently
noticed that not all of the components listed in SRC_CC actually get to
compile (including default_log.cc), which results in incomplete core-sel4
library. After taking a closer look, it turned out that
io_port_session_support.cc and io_port_session_component.cc are the source
of this problem. I had them out commented for my sabre_lite build as
you've previously suggested. Removing them from core-sel4.mk for
seL4_x86_32 build gave me the same results as for sabre_lite: incomplete
core-seL4 library

Library core-sel4
COMPILE cpu_session_component.o
COMPILE cpu_session_support.o
COMPILE cpu_thread_component.o
COMPILE io_mem_session_component.o
COMPILE io_mem_session_support.o
COMPILE main.o
COMPILE pd_assign_pci.o
COMPILE pd_session_component.o
COMPILE pd_upgrade_ram_quota.o
COMPILE ram_session_component.o
COMPILE ram_session_support.o
COMPILE rom_session_component.o
COMPILE rpc_cap_factory.o
COMPILE version.o
MERGE core-sel4.lib.a

and the same "undefined reference" errors at the end.
Now that I know where the problem is: what can I do from here?

Post by Alexander Boettcher
Please check that you compile and link the
file to core. Check that the symbol actually shows up as symbol in
core.o, e.g. by examining the output of "readelf -s
build/<arch>/core/sel4/core.o".

Not sure what you mean by the symbol. "readelf -s core.o | grep -i log"
gave me the following output:
10311: 00000000 0 FILE LOCAL DEFAULT ABS log.cc

Comparing to successful build for x86_32:
8733: 00000000 0 FILE LOCAL DEFAULT ABS log.cc
9028: 00000000 0 FILE LOCAL DEFAULT ABS core_log.cc
9175: 00000000 0 FILE LOCAL DEFAULT ABS default_log.cc

Thanks

Alexander Boettcher

2017-06-22 13:14:38 UTC

Permalink

Hi,

Post by l***@critical.com
Yes, default_log.cc is listed in core-sel4.mk file. However, I've recently
noticed that not all of the components listed in SRC_CC actually get to
compile (including default_log.cc), which results in incomplete core-sel4
library. After taking a closer look, it turned out that
io_port_session_support.cc and io_port_session_component.cc are the source
of this problem. I had them out commented for my sabre_lite build as
you've previously suggested. Removing them from core-sel4.mk for
seL4_x86_32 build gave me the same results as for sabre_lite: incomplete
core-seL4 library

now I get the same error. You can't just uncomment it with '#', because
all followed files will _not_ be added anymore. Just remove the lines
completely. The issue here is that all files are concatenated by the '\'
at the end of each line. If you uncomment one in between, all lines (and
therefore files) below will not be compiled anymore.

Post by l***@critical.com
Library core-sel4
COMPILE cpu_session_component.o
COMPILE cpu_session_support.o
COMPILE cpu_thread_component.o
COMPILE io_mem_session_component.o
COMPILE io_mem_session_support.o
COMPILE main.o
COMPILE pd_assign_pci.o
COMPILE pd_session_component.o
COMPILE pd_upgrade_ram_quota.o
COMPILE ram_session_component.o
COMPILE ram_session_support.o
COMPILE rom_session_component.o
COMPILE rpc_cap_factory.o
COMPILE version.o
MERGE core-sel4.lib.a
and the same "undefined reference" errors at the end.
Now that I know where the problem is: what can I do from here?

In case it is successful, on x86 I get:

readelf -s build/x86_32/core/sel4/core-sel4.o | grep log | grep Log

7729: 00000000 0 NOTYPE GLOBAL DEFAULT UND _ZN6Genode3Log3logEv

Here you see the symbol part of core.o.

Yevgeny Lavrov

2017-06-23 03:31:23 UTC

Permalink

Hi, Alex

Thanks a lot for the hint. Got it all fixed. Now I can get image.elf to
compile and readelf -s returns:
22790: 00000000 112 FUNC GLOBAL DEFAULT 3735 _ZN6Genode3Log3logEv

Ran into "undefined reference" again with io_port* files but was able to
fix by changing vpath for platform_services.cc
from: $(GEN_CORE_DIR)/spec/x86 to $(GEN_CORE_DIR).

Running the image on board gave no result, apart from msg: ## Starting
application at 0x10001000 ...

Is it possible that I might be missing some i.MX6 platform specific files
in my build? Like those that can be found in
/base-hw/src/core/spec and /base-hw/src/core/include/spec

On Thu, Jun 22, 2017 at 9:14 AM, Alexander Boettcher <

Post by l***@critical.com
Hi,

Post by l***@critical.com
Yes, default_log.cc is listed in core-sel4.mk file. However, I've

recently

Post by l***@critical.com
noticed that not all of the components listed in SRC_CC actually get to
compile (including default_log.cc), which results in incomplete core-sel4
library. After taking a closer look, it turned out that
io_port_session_support.cc and io_port_session_component.cc are the

source

Post by l***@critical.com
of this problem. I had them out commented for my sabre_lite build as
you've previously suggested. Removing them from core-sel4.mk for
seL4_x86_32 build gave me the same results as for sabre_lite: incomplete
core-seL4 library

readelf -s build/x86_32/core/sel4/core-sel4.o | grep log | grep Log
7729: 00000000 0 NOTYPE GLOBAL DEFAULT UND _ZN6Genode3Log3logEv
Here you see the symbol part of core.o.
--
Alexander Boettcher
Genode Labs
http://www.genode-labs.com - http://www.genode.org
Genode Labs GmbH - Amtsgericht Dresden - HRB 28424 - Sitz Dresden
GeschÃ€ftsfÃŒhrer: Dr.-Ing. Norman Feske, Christian Helmuth
------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
genode-main mailing list
https://lists.sourceforge.net/lists/listinfo/genode-main

Norman Feske

2017-06-23 10:00:42 UTC

Permalink

Hello Yevgeny,

Post by Yevgeny Lavrov
Running the image on board gave no result, apart from msg: ## Starting
application at 0x10001000 ...

I wonder, how exactly are you running the image on the board? In
particular, how is the image created?

I am asking because the boot procedure on ARM is different from
x86/multiboot. On x86, the kernel and the Genode ELF image are loaded by
the boot loader (e.g., Grub) as separate boot modules. The kernel is
started by the boot loader. At the startup of the kernel, the kernel
finds the physical memory location of the Genode ELF image in the
multiboot information and ELF-loads core by using this information. In
contrast, on ARM, everything (seL4 kernel + Genode) must be contained in
a single image. The details of how such an image is assembled is
kernel-specific. Consequently, there must exist a seL4-specific tool for
creating it. Can you please elaborate, which tool you use and which
particular steps you take?

Another potential pitfall would be the use of the wrong UART or the use
of a kernel configuration without debug support. The latter is needed
for the kernel-provided UART driver. Have you tried to run a
non-Genode-based seL4 image on the hardware? I would not try to run
Genode on the device before running a simple seL4 example first.

Cheers
Norman

Hinnerk van Bruinehsen

2017-06-23 23:20:24 UTC

Permalink

Post by Norman Feske
Hello Yevgeny,

Post by Yevgeny Lavrov
Running the image on board gave no result, apart from msg: ## Starting
application at 0x10001000 ...

I wonder, how exactly are you running the image on the board? In
particular, how is the image created?
I am asking because the boot procedure on ARM is different from
x86/multiboot. On x86, the kernel and the Genode ELF image are loaded by
the boot loader (e.g., Grub) as separate boot modules. The kernel is
started by the boot loader. At the startup of the kernel, the kernel
finds the physical memory location of the Genode ELF image in the
multiboot information and ELF-loads core by using this information. In
contrast, on ARM, everything (seL4 kernel + Genode) must be contained in
a single image. The details of how such an image is assembled is
kernel-specific. Consequently, there must exist a seL4-specific tool for
creating it. Can you please elaborate, which tool you use and which
particular steps you take?
Another potential pitfall would be the use of the wrong UART or the use
of a kernel configuration without debug support. The latter is needed
for the kernel-provided UART driver. Have you tried to run a
non-Genode-based seL4 image on the hardware? I would not try to run
Genode on the device before running a simple seL4 example first.

Hi,

I'm using a fork of seL4's elfloader-tool that I've hacked together to
create an image that acutally boots (at least it gets into the genode
userland image where it is failing).
To be clear: I need to add calls to kernel_debugger_outstring as I get
a data fault before the logging infrastructure works (I guess due to
exception handling not being initialized before the fail occurs).

I'm using an am335x based board so I can't test if this works for other
hardware, but if anyone is interested you can find my elfloader fork at
https://github.com/N8Fear/elfloader-tool

The bootable image is then created by running the script from the
elfloader dir
TOOLPREFIX=arm-none-eabi- PLAT=am335x ./gen_boot_image.sh
<path to genode>/build/wega_am335x/var/run/log/sel4
<path to genode>/build/wega_am335x/var/run/log/image.elf
/tmp/out.elf

PLAT and TOOLPREFIX need to be changed accordingly and when building the
prelinked elfloader binary PLAT and ARMV needs to be adjusted as well
(take a look at the Makefile).

I guess for your board you should try PLAT=imx6 for building and for
creating the image.

I guess I should do some cleanup if anyone else wants to use the
stuff...

With kind regards,
Hinnerk

Yevgeny Lavrov

2017-06-26 04:14:56 UTC

Permalink

Hi, Norman

Post by Norman Feske
I wonder, how exactly are you running the image on the board?

I normally just copy created image over to SD card and then run it via
bootelf command.

Post by Norman Feske
In contrast, on ARM, everything (seL4 kernel + Genode) must be contained

in a single image. The details of how such an image is assembled is
kernel-specific
This might explain why the image didn't give me any output. I ended up with
two images: image.elf & sel4.elf instead of just image.elf in my
<sabre_lite>/var/run/log/

Post by Norman Feske
Consequently, there must exist a seL4-specific tool for creating it. Can

you please elaborate, which tool you use and which particular steps you
take?
Didn't think of any tool for combining image.elf & sel4.elf together until
I got your reply. Only thought of modifying /tool/run/boot_dir/sel4 file.
I'll give Hinnerks elfloader-tool a try today.

Post by Norman Feske
Have you tried to run a non-Genode-based seL4 image on the hardware? I

would not try to run

Post by Norman Feske
Genode on the device before running a simple seL4 example first.

Yes, this was my starting point. All seL4 apps ran w/o any problems.

Thanks

On Fri, Jun 23, 2017 at 7:20 PM, Hinnerk van Bruinehsen <

Post by Norman Feske

Post by Norman Feske
Hello Yevgeny,

Post by Yevgeny Lavrov
Running the image on board gave no result, apart from msg: ## Starting
application at 0x10001000 ...

I wonder, how exactly are you running the image on the board? In
particular, how is the image created?
I am asking because the boot procedure on ARM is different from
x86/multiboot. On x86, the kernel and the Genode ELF image are loaded by
the boot loader (e.g., Grub) as separate boot modules. The kernel is
started by the boot loader. At the startup of the kernel, the kernel
finds the physical memory location of the Genode ELF image in the
multiboot information and ELF-loads core by using this information. In
contrast, on ARM, everything (seL4 kernel + Genode) must be contained in
a single image. The details of how such an image is assembled is
kernel-specific. Consequently, there must exist a seL4-specific tool for
creating it. Can you please elaborate, which tool you use and which
particular steps you take?
Another potential pitfall would be the use of the wrong UART or the use
of a kernel configuration without debug support. The latter is needed
for the kernel-provided UART driver. Have you tried to run a
non-Genode-based seL4 image on the hardware? I would not try to run
Genode on the device before running a simple seL4 example first.

Hi,
I'm using a fork of seL4's elfloader-tool that I've hacked together to
create an image that acutally boots (at least it gets into the genode
userland image where it is failing).
To be clear: I need to add calls to kernel_debugger_outstring as I get
a data fault before the logging infrastructure works (I guess due to
exception handling not being initialized before the fail occurs).
I'm using an am335x based board so I can't test if this works for other
hardware, but if anyone is interested you can find my elfloader fork at
https://github.com/N8Fear/elfloader-tool
The bootable image is then created by running the script from the
elfloader dir
TOOLPREFIX=arm-none-eabi- PLAT=am335x ./gen_boot_image.sh
<path to genode>/build/wega_am335x/var/run/log/sel4
<path to genode>/build/wega_am335x/var/run/log/image.elf
/tmp/out.elf
PLAT and TOOLPREFIX need to be changed accordingly and when building the
prelinked elfloader binary PLAT and ARMV needs to be adjusted as well
(take a look at the Makefile).
I guess for your board you should try PLAT=imx6 for building and for
creating the image.
I guess I should do some cleanup if anyone else wants to use the
stuff...
With kind regards,
Hinnerk
------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
genode-main mailing list
https://lists.sourceforge.net/lists/listinfo/genode-main

Alexander Boettcher

2017-07-05 10:43:29 UTC

Permalink

Hi Hinnerk,

Post by Hinnerk van Bruinehsen
I'm using a fork of seL4's elfloader-tool that I've hacked together to
create an image that acutally boots (at least it gets into the genode
userland image where it is failing).
To be clear: I need to add calls to kernel_debugger_outstring as I get
a data fault before the logging infrastructure works (I guess due to
exception handling not being initialized before the fail occurs).
I'm using an am335x based board so I can't test if this works for other
hardware, but if anyone is interested you can find my elfloader fork at
https://github.com/N8Fear/elfloader-tool
The bootable image is then created by running the script from the
elfloader dir
TOOLPREFIX=arm-none-eabi- PLAT=am335x ./gen_boot_image.sh
<path to genode>/build/wega_am335x/var/run/log/sel4
<path to genode>/build/wega_am335x/var/run/log/image.elf
/tmp/out.elf
PLAT and TOOLPREFIX need to be changed accordingly and when building the
prelinked elfloader binary PLAT and ARMV needs to be adjusted as well
(take a look at the Makefile).

just wanted to say, thanks for your seL4 elfloader tool adaptations to
make it usable standalone (so - no need to dissect Camkes for it, like
getting cpio lib and common.mk mainly).

Thanks to your work I could get the tool integrated into the run tool
infrastructure of Genode in within one day. And the best, it boots and I
get the serial life sign of Genode/seL4 on ARM.

Great !

Alexander Boettcher

2017-07-07 16:54:08 UTC

Permalink

Hi Hinnerk and Yevgeny,

Post by Alexander Boettcher
Thanks to your work I could get the tool integrated into the run tool
infrastructure of Genode in within one day. And the best, it boots and I
get the serial life sign of Genode/seL4 on ARM.

nice to hear thank it helps. I guess the next step will be to split out
the x86 specific code from the generic parts and implement arm specific
stuff.

this is now done, see the issue 2451 [0] and the referenced branch.

Let me know if I can help. I'm kind of fiddling around with this for
quite a while now.

You may now try to re-add your desired board. In theory you should just
add some *.mk files at the right places, some minor patches to the
autoconfig.h, but without actually changing (hopefully) the code of
'core' on Genode/seL4.

I'm interested to hear from you, whether my assumption is right in that
regard.

Cheers,

Alex.

[0] https://github.com/genodelabs/genode/issues/2451