Skip to contentSkip to conversation

bare-metal RPi2B & RPI3B

DISCUSSION Edward Vidal 1 participant 1 message Apr 13, 2017 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw

Hello All,
As of now I have been able to get the library of openjpeg running in bare-metal RPi2B or RPi3B.With just 5 files on a RPi2B or RPi3B the compression of bitmap is done.bootcode.bin  fixup.dat  kernel7.img  MyBitmap.bmp  start.elf.In addition this provides a TFTP server and Telnet services.In 26 sec the RPi3B boots and does a compression of a 1024 x 1024 image.The compression takes 5 sec  These files are found at https://github.com/develone/jpeg-2000-test/tree/master/bare-metal/openjp/sd-card/see https://github.com/develone/jpeg-2000-test/blob/master/bare-metal/LibC/LibC.pdfand the openjpeg library https://github.com/develone/openjpeg/blob/ultibo/openjpeg.odtI forked the openjpeg repo and created a ultibo branch.The compiler used is arm-none-eabi tools to compile the C code and Free Pascal Compiler to compile and link kernel7.img. This is the documentation to date.
pi@raspberrypi3:~ $ export PATH=/home/pi/ultibo/core/fpc/bin:$PATHpi@raspberrypi3:~ $ cd jpeg-2000-test/bare-metal/openjp/pi@raspberrypi3:~/jpeg-2000-test/bare-metal/openjp $ ./compile.sh Thu 13 Apr 11:36:26 UTC 2017Word count arm-none-eabi-ar -t libopenjp2.acopied from /home/pi/t_ultibo/src/lib/openjp2     22      22     180Target OS: UltiboCompiling DWT_LIFT_RPi2.lprCompiling uTFTP.pasAssembling utftpCompiling uliftbitmap.pasCompiling uBufferToC.pasAssembling uliftbitmapAssembling dwt_lift_rpi2Linking DWT_LIFT_RPi21086 lines compiled, 4.7 sec, 2733156 bytes code, 89252 bytes data-rw-r--r-- 1 pi pi    7364 Apr 13 11:36 dwtlift.o-rwxr-xr-x 1 pi pi 2808540 Apr 13 11:36 kernel7.img-rw-r--r-- 1 pi pi  356242 Apr 13 11:36 libdwtlift.a-rw-r--r-- 1 pi pi  356242 Apr 13 11:36 libopenjp2.awhen ./compile.sh is executed should be 23Word count libopenjp2_obj.txt in /home/pi/t_ultibo/src/lib/openjp2plus dwtlift.o 23  23 190 libopenjp2_obj.txt Does Wine run in Yocto? This would make Ultibo the Bare-metal project work in Yocto.

Let me know if you have any questions. Edward Vidal Jr. e-mail [email protected] 915-595-1613

On Friday, February 3, 2017 12:37 AM, "[email protected]" <[email protected]> wrote:

Send yocto mailing list submissions to
    [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
    https://lists.yoctoproject.org/listinfo/yocto
or, via email, send a message with subject or body 'help' to [email protected]

You can reach the person managing the list at
    [email protected]

When replying, please edit your Subject line so it is more specific than "Re: Contents of yocto digest..."

Today's Topics:

  1. Re: Ruby and OpenSSL version mismatch? (Khem Raj)
  2. bare-metal RPi2B & RPI3B (Edward Vidal)
  3. [meta-cgl][PATCH 3/3] initramfs: fix parsing issue with do    to uboot inclusion (Armin Kuster)
  4. [meta-cgl][PATCH 1/3] iscsi-initiator-utils: make it DISTRO_FEATURE dependent (Armin Kuster)

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

Message: 1
Date: Thu, 02 Feb 2017 22:47:40 +0000
From: Khem Raj <[email protected]>
To: Takashi Matsuzawa <[email protected]>,    "[email protected]" <[email protected]>
Subject: Re: [yocto] Ruby and OpenSSL version mismatch? Message-ID:
    <CAMKF1sr4Go-8_9k+1d32JkzSeWKguc9S+iZ94Vk_iFKrv_-kDw@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Send a back port request

Quoted 63 lines · Takashi Matsuzawa

Hello, I just tried and the below seems to be the fix.

https://patchwork.openembedded.org/patch/119999/

------------------------------
*From:* Takashi Matsuzawa
*Sent:* Thursday, February 2, 2017 3:25 PM
*To:* [email protected]
*Subject:* Ruby and OpenSSL version mismatch?

Hello, Yocto.

I am trynig a build of fido based yocto image, with openssl 1.0.2j for security reason.
The openssl recipe itself builds successfully, but later in the build I see error in jscore.
In fact, ruby is complaining that 'OPENSSL_1.0.0' is not available.

|
/xxx/sysroots/x86_64-linux/usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in
`require':
/xxx/sysroots/x86_64-linux/usr/lib/ruby/2.2.0/x86_64-linux-gnu/digest/../../../../libcrypto.so.1.0.0:
version `OPENSSL_1.0.0' not found (required by /xxx/sysroots/x86_64-linux/usr/lib/ruby/2.2.0/x86_64-linux-gnu/digest/sha1.so)
-
/xxx/sysroots/x86_64-linux/usr/lib/ruby/2.2.0/x86_64-linux-gnu/digest/sha1.so
(LoadError)
|    from
/xxx/sysroots/x86_64-linux/usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in
`require'
|    from /xxx/work/core2-32-poky-linux/qtwebkit/5.5.0+gitAUTOINC+0d592678ba-r0/git/Source/JavaScriptCore/offlineasm/generate_offset_extractor.rb:30:in `<main>'
| make[2]: *** [LLIntDesiredOffsets.h] Error 1

In fact, if I do objdump -p on sha1.so (in ruby tree):

Quoted 2 lines

  required from libcrypto.so.1.0.0:
    0x066a2b20 0x00 02 OPENSSL_1.0.0

Whereas, my libcrypt.so.1.0.0 says:

Quoted 5 lines

Version definitions:
1 0x01 0x0746be50 libcrypto.so.1.0.0
2 0x00 0x06a2b2e4 OPENSSL_1.0.2d
3 0x00 0x06a2b2e7 OPENSSL_1.0.2g
    OPENSSL_1.0.2d

So, this might be the cause of the problem.
But I am not sure why sha1.so (which ruby build generats) define these version numbers and not refer to the OpenSSL library in the build.

I googled, but there were some tips on updating ruby to solve OpenSSL version mismatch, but it is through grew or apt-get, etc.  Not a tip for yocto build.

I may be not familiar with ruby build yet, but any idea how I can fix this? I could try updating ruby recipe as well to more recent version, but first I want to confirm how ruby is deciding the OpenSSL version for its plugin library and causing this mismatch.

Quoted 8 lines

Thank you for your knowledge..

--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20170202/e4ddf3be/attachment-0001.html>

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

Message: 2
Date: Fri, 3 Feb 2017 00:24:27 +0000 (UTC)
From: Edward Vidal <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [yocto] bare-metal RPi2B & RPI3B
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"

Hello All,
Today I was able to get the lifting step in bare-metal.
With just 5 files on a RPi2B the lifting step was done.
bootcode.bin ?fixup.dat ?kernel7.img ?MyBitmap.bmp ?start.elf
?These files are found at?https://github.com/develone/jpeg-2000-test/tree/master/bare-metal/LibC/sd-card/RPi2 see?https://github.com/develone/jpeg-2000-test/blob/master/bare-metal/LibC/LibC.pdf
This is the documentation to date.
Let me know if you have any questions.??Edward Vidal Jr. e-mail [email protected] 915-595-1613 -------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20170203/9402a9cd/attachment-0001.html>

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

Message: 3
Date: Thu,  2 Feb 2017 16:36:36 -0800
From: Armin Kuster <[email protected]>
To: [email protected],    [email protected]
Subject: [yocto] [meta-cgl][PATCH 3/3] initramfs: fix parsing issue with do    to uboot inclusion
Message-ID: <[email protected]>

From: Armin Kuster <[email protected]>

since the image type includes "uboot", need to inherit the class for it

---
 meta-cgl-common/images/core-image-cgl-initramfs.bb | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
meta-cgl-common/images/core-image-cgl-initramfs.bb +2 -2
index 0777b7c..2ebbdf5 100644
@@ -12,8 +12,8 @@ export IMAGE_BASENAME = "core-image-cgl-initramfs"
 IMAGE_LINGUAS = ""
 
 LICENSE = "MIT"
-
-IMAGE_FSTYPES = "cpio.gz.u-boot"
+IMAGE_CLASSES = " image_types_uboot"
+IMAGE_FSTYPES ??= "cpio.gz.u-boot"
 
 IMAGE_ROOTFS_SIZE = "8192"
 
Signature · 23 lines
2.7.4



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

Message: 4
Date: Thu,  2 Feb 2017 16:36:34 -0800
From: Armin Kuster <[email protected]>
To: [email protected],    [email protected]
Subject: [yocto] [meta-cgl][PATCH 1/3] iscsi-initiator-utils: make it
    DISTRO_FEATURE dependent
Message-ID: <[email protected]>

From: Armin Kuster <[email protected]>

When this package was updated in OE,
it now requires systemd. Make this optional.

Signed-off-by: Armin Kuster <[email protected]>
---
 meta-cgl-common/packagegroups/packagegroup-cgl-middleware.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
meta-cgl-common/packagegroups/packagegroup-cgl-middleware.bb +0 -0
index b0c2cac..045691a 100644
@@ -42,7 +42,7 @@ RDEPENDS_packagegroup-cgl-middleware = "\

    strongswan \
    vlan \
    corosync \
-    iscsi-initiator-utils \
+ ${@bb.utils.contains("DISTRO_FEATURES", "systemd", "iscsi-initiator-utils", "",d)} \
    openais \
    openipmi \
    openhpi \

Signature · 15 lines
2.7.4



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

-- 
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto


End of yocto Digest, Vol 77, Issue 10
*************************************