Date
1 - 10 of 10
Building for TI 8148 EVM
|
Rainer Koenig <Rainer.Koenig@...>
Hi,
I'm currently trying to build an image for the TI 8148 EVM board. For that I added the meta-ti layer to the standard Yocto/Edison environment. meta-ti has under conf/machine a dm8148-evm.conf. So I wrote dm8148-evm as MACHINE in my local.conf. Build stopped at building u-boot_git.bb and William Mills pointed me to u-boot_2010.06-psp.bb for the 8148 EVM board. I tried that but then the build process complained about the SRCREV. Looking at the recipe I see: require u-boot.inc FILESPATHPKG =. "u-boot-psp-git:" COMPATIBLE_MACHINE = "am387x-evm|am389x-evm|c6a814x-evm|c6a816x-evm|dm814x-evm" SRC_URI = "git://arago-project.org/git/projects/u-boot-omap3.git;branch=${BRANCH};protocol=git" BRANCH_ti814x = "ti81xx-master" SRCREV_pn-${PN}_ti814x = "5fcf46a405fe8e8a59a04d3cebdafd39ac0c4bd0" LIC_FILES_CHKSUM_pn-${PN}_ti814x = "file://COPYING;md5=4c6cde5df68eff615d36789dc18edd3b" Questions: I can solve my SRCREV problem when I substite the ti814x in BRANCH... and SRCREV with my actual dm8148-evm. That makes me ask, what the purpose of the COMPATIBLE_MACHINE variable is? If this what I (beginner level) found is a bug, then where do I report it or submit a fix for it? The recipe built u-boot.bin now, but I don't see an MLO file in my image directory. What did I do wrong? After the image compiled I put it on an SD card and tried to boot with it, but the kernel runs into a panic: USB Video Class driver (v1.0.0) OMAP Watchdog Timer Rev 0x00: initial timeout 60 sec usbcore: registered new interface driver usbhid usbhid: USB HID core driver Unable to handle kernel NULL pointer dereference at virtual address 00000002 pgd = c0004000 [00000002] *pgd=00000000 Internal error: Oops: 5 [#1] last sysfs file: Modules linked in: CPU: 0 Not tainted (2.6.37+ #2) PC is at strcmp+0xc/0x40 LR is at omap_mbox_get+0x3c/0x1d0 pc : [<c01cf034>] lr : [<c00566c4>] psr: a0000013 sp : de83df28 ip : de83df38 fp : de83df34 r10: 00000000 r9 : 00000000 r8 : 00000000 r7 : 00000013 r6 : c0458048 r5 : c0503af8 r4 : c04de2e4 r3 : 00000064 r2 : 00000076 r1 : c0458048 r0 : 00000002 Flags: NzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel Control: 10c5387d Table: 80004019 DAC: 00000017 Process swapper (pid: 1, stack limit = 0xde83c2e8) Stack: (0xde83df28 to 0xde83e000) df20: de83df5c de83df38 c00566c4 c01cf034 c02cc038 c01cf034 df40: 00000000 c0503a9c c0503a98 00000000 de83df7c de83df60 c02cfb0c c0056694 df60: 00000000 00000000 c0029c0c c0024034 de83dfa4 de83df80 c0024070 c02cf988 df80: de83c000 c0029c0c c0024034 00000000 00000013 00000000 de83dfdc de83dfa8 dfa0: c00343b8 c0024040 de83dfc4 00000176 c04ea918 c006154c c0029c0c c0029cb0 dfc0: c006154c 00000013 00000000 00000000 de83dff4 de83dfe0 c0008cf4 c0034304 dfe0: 00000000 c0008c40 00000000 de83dff8 c006154c c0008c4c 00010960 4a408a08 Backtrace: [<c01cf028>] (strcmp+0x0/0x40) from [<c00566c4>] (omap_mbox_get+0x3c/0x1d0) [<c0056688>] (omap_mbox_get+0x0/0x1d0) from [<c02cfb0c>] (notify_shm_drv_setup+0x190/0x268) r6:00000000 r5:c0503a98 r4:c0503a9c [<c02cf97c>] (notify_shm_drv_setup+0x0/0x268) from [<c0024070>] (notify_init+0x3c/0x2b0) r5:c0024034 r4:c0029c0c [<c0024034>] (notify_init+0x0/0x2b0) from [<c00343b8>] (do_one_initcall+0xc0/0x194) r8:00000000 r7:00000013 r6:00000000 r5:c0024034 r4:c0029c0c r3:de83c000 [<c00342f8>] (do_one_initcall+0x0/0x194) from [<c0008cf4>] (kernel_init+0xb4/0x164) r9:00000000 r8:00000000 r7:00000013 r6:c006154c r5:c0029cb0 r4:c0029c0c [<c0008c40>] (kernel_init+0x0/0x164) from [<c006154c>] (do_exit+0x0/0x61c) r5:c0008c40 r4:00000000 Code: e89da800 e1a0c00d e92dd800 e24cb004 (e4d03001) ---[ end trace e6ffc3d1c2d89a51 ]--- Kernel panic - not syncing: Attempted to kill init! Now I start wondering if I'm using the right kernel for this board. meta-ti/recipes-kernel/linux/lists recipes for a lot of kernels, but according to the conf/machine/include/ti814x.inc I should have used the right one. So how can I debug this kernel panic? Regards Rainer -- Dipl.-Inf. (FH) Rainer Koenig Project Manager Linux Clients Dept. PDG WPS R&D SW OSE Fujitsu Technology Solutions Bürgermeister-Ullrich-Str. 100 86199 Augsburg Germany Telephone: +49-821-804-3321 Telefax: +49-821-804-2131 Mail: mailto:Rainer.Koenig@... Internet ts.fujtsu.com Company Details ts.fujitsu.com/imprint.html |
|
|
|
Koen Kooi
Op 21 okt. 2011, om 11:07 heeft Rainer Koenig het volgende geschreven:
Hi,Please follow the instructions detailed in the meta-ti README: http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/README Yocto/Poky lacks support for various meta-ti (and OE-classic) constructs needed for a successfull build. Following the instructions above you will get a proper setup. regards, Koen |
|
|
|
Rainer Koenig <Rainer.Koenig@...>
Koen,
Am 21.10.2011 11:14, schrieb Koen Kooi: Tried this over the weekend on my home PC. Yes, works. But I was justI'm currently trying to build an image for the TI 8148 EVM board. ForPlease follow the instructions detailed in the meta-ti README: http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/README able to build a console image. The build of systemd-gnome-image fails with the error that nothing provides "DRI". MACHINE=dm8148-evm. Regards Rainer -- Dipl.-Inf. (FH) Rainer Koenig Project Manager Linux Clients Dept. PDG WPS R&D SW OSE Fujitsu Technology Solutions Bürgermeister-Ullrich-Str. 100 86199 Augsburg Germany Telephone: +49-821-804-3321 Telefax: +49-821-804-2131 Mail: mailto:Rainer.Koenig@... Internet ts.fujtsu.com Company Details ts.fujitsu.com/imprint.html |
|
|
|
Koen Kooi
Op 24 okt. 2011, om 10:48 heeft Rainer Koenig het volgende geschreven:
Koen,I'm not seeing that with this set of metadata: OE Build Configuration: BB_VERSION = "1.13.3" TARGET_ARCH = "arm" TARGET_OS = "linux-gnueabi" MACHINE = "dm814x-evm" DISTRO = "angstrom" DISTRO_VERSION = "v2011.10-core" TUNE_FEATURES = "armv7a vfp neon cortexa8" TARGET_FPU = "vfp-neon" meta-angstrom = "master:14f73c63403525f85a15f61f88895ba377364338" meta-oe meta-efl meta-gpe meta-gnome meta-xfce = "master:5da48e6e4a4ab0488943c5e93f005211bd7a22f7" meta-ti = "master:2ea9f93740259be7eee59edeb88e632c5441fb58" meta-ettus = "master:617506b5cfd2b8325d85f0dcba0232c3f796d044" meta-efikamx = "master:2ef47fdd4e8232d766c0c63d9427253ee56e31d0" meta-nslu2 = "master:17853811179f2760791c6b138f96e9dd15493517" meta-htc meta-nokia meta-openmoko meta-palm = "oe-core:794b32d234dbf7e6626c8a0efc915fc04804b9d0" meta-sugarbay meta-crownbay meta-emenlow meta-fishriver meta-jasperforest meta-n450 = "master:0ea04b02119c44865e5e1c2529c74950928c3347" meta = "master:99da9a4e65f9dffb04efc3ad60125194c476d6b3" Could you please share your version of that so we can see if there are fixes missing? regards, Koen |
|
|
|
Rainer Koenig <Rainer.Koenig@...>
Koen,
Am 24.10.2011 10:58, schrieb Koen Kooi:
Tried this over the weekend on my home PC. Yes, works. But I was justI'm not seeing that with this set of metadata: Could you please share your version of that so we can see if there are fixes missing?Difficult at the moment because now I'm back to work and the data is at home. :-) But I will setup this again on my work machine and see that I get the firewall-issues solved, so I should be able to reproduce my results. I was really just following the linked instructions above, maybe I should have setup something in my local.conf...? Regards Rainer -- Dipl.-Inf. (FH) Rainer Koenig Project Manager Linux Clients Dept. PDG WPS R&D SW OSE Fujitsu Technology Solutions Bürgermeister-Ullrich-Str. 100 86199 Augsburg Germany Telephone: +49-821-804-3321 Telefax: +49-821-804-2131 Mail: mailto:Rainer.Koenig@... Internet ts.fujtsu.com Company Details ts.fujitsu.com/imprint.html |
|
|
|
Koen Kooi
Op 24 okt. 2011, om 11:05 heeft Rainer Koenig het volgende geschreven:
Koen,The oebb.sh script has builtin firewall support, have a look at that. If something is missing, please let us know. I was really just following the linked instructions above, maybe INo, the setup scripts try really hard to avoid having you edit conf files :) regards, Koen |
|
|
|
Koen Kooi
Op 24 okt. 2011, om 11:05 heeft Rainer Koenig het volgende geschreven:
Koen,Roger provided a log with a related looking bug, which should get solved Real Soon(TM) when the following gets applied: http://patchwork.openembedded.org/patch/13783/ In the mean time you should be able to get around it by doing 'bitbake mesa-dri' manually. regards, Koen |
|
|
|
Denys Dmytriyenko
On Mon, Oct 24, 2011 at 01:22:54PM +0200, Koen Kooi wrote:
Yep, I can confirm this issue. I had it fixed locally by adding mesa-dri to DEPENDS in xorg-xserver... Didn't have time to submit either a patch or a bugreport though. -- Denys |
|
|
|
Rainer Koenig <Rainer.Koenig@...>
Am 24.10.2011 20:37, schrieb Denys Dmytriyenko:
Ok, with all the hints from this thread I was able to build an image.In the mean time you should be able to get around it by doing 'bitbakeYep, I can confirm this issue. I had it fixed locally by adding mesa-dri to Testing on my DM8148 EVM wasn't that much of a success, image boots to console, but is lacking of the required (question: what do I need for this EVM, anyone from TI can tell me?) xorg-modules. /etc/X11/xorg.conf tries to load an intel driver which is definitely out of range for this board. :-) How can I see from the logs what xserver/xorg-components were built and how can I add the missing ones? TIA Rainer -- Dipl.-Inf. (FH) Rainer Koenig Project Manager Linux Clients Dept. PDG WPS R&D SW OSE Fujitsu Technology Solutions Bürgermeister-Ullrich-Str. 100 86199 Augsburg Germany Telephone: +49-821-804-3321 Telefax: +49-821-804-2131 Mail: mailto:Rainer.Koenig@... Internet ts.fujtsu.com Company Details ts.fujitsu.com/imprint.html |
|
|
|
Koen Kooi
Op 25 okt 2011, om 14:32 heeft Rainer Koenig het volgende geschreven:
Am 24.10.2011 20:37, schrieb Denys Dmytriyenko:You need to ask your TI rep for a m3 firmware file. When you have that you need to build some syslink things to get your display working. I integrated it all a few months ago for a demo you probably have seen :)Ok, with all the hints from this thread I was able to build an image.In the mean time you should be able to get around it by doing 'bitbakeYep, I can confirm this issue. I had it fixed locally by adding mesa-dri to I'm at a conference now, so I can't look up my notes for the exact sequence, but it starts with getting the magic firmware file. regards, Koen |
|
|