Menu
▾
▴
gumstix-users — General discussion for gumstix users and developers.
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
(114) |
Apr
(35) |
May
(60) |
Jun
(52) |
Jul
(121) |
Aug
(170) |
Sep
(343) |
Oct
(147) |
Nov
(185) |
Dec
(172) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(319) |
Feb
(505) |
Mar
(614) |
Apr
(358) |
May
(344) |
Jun
(306) |
Jul
(558) |
Aug
(506) |
Sep
(639) |
Oct
(863) |
Nov
(705) |
Dec
(562) |
| 2006 |
Jan
(828) |
Feb
(1229) |
Mar
(1099) |
Apr
(856) |
May
(1099) |
Jun
(943) |
Jul
(1109) |
Aug
(975) |
Sep
(928) |
Oct
(1174) |
Nov
(1120) |
Dec
(948) |
| 2007 |
Jan
(858) |
Feb
(1095) |
Mar
(1143) |
Apr
(1178) |
May
(1255) |
Jun
(1092) |
Jul
(1373) |
Aug
(904) |
Sep
(848) |
Oct
(1552) |
Nov
(823) |
Dec
(973) |
| 2008 |
Jan
(1303) |
Feb
(1093) |
Mar
(1173) |
Apr
(1258) |
May
(664) |
Jun
(461) |
Jul
(613) |
Aug
(452) |
Sep
(387) |
Oct
(411) |
Nov
(466) |
Dec
(608) |
| 2009 |
Jan
(529) |
Feb
(452) |
Mar
(482) |
Apr
(679) |
May
(545) |
Jun
(588) |
Jul
(519) |
Aug
(675) |
Sep
(441) |
Oct
(556) |
Nov
(472) |
Dec
(471) |
| 2010 |
Jan
(799) |
Feb
(622) |
Mar
(659) |
Apr
(479) |
May
(631) |
Jun
(698) |
Jul
(802) |
Aug
(666) |
Sep
(533) |
Oct
(797) |
Nov
(459) |
Dec
(486) |
| 2011 |
Jan
(792) |
Feb
(526) |
Mar
(748) |
Apr
(506) |
May
(477) |
Jun
(528) |
Jul
(642) |
Aug
(418) |
Sep
(494) |
Oct
(374) |
Nov
(355) |
Dec
(424) |
| 2012 |
Jan
(476) |
Feb
(491) |
Mar
(606) |
Apr
(462) |
May
(275) |
Jun
(278) |
Jul
(241) |
Aug
(205) |
Sep
(215) |
Oct
(296) |
Nov
(317) |
Dec
(108) |
| 2013 |
Jan
(317) |
Feb
(228) |
Mar
(157) |
Apr
(108) |
May
(120) |
Jun
(123) |
Jul
(136) |
Aug
(204) |
Sep
(169) |
Oct
(152) |
Nov
(103) |
Dec
(164) |
| 2014 |
Jan
(153) |
Feb
(190) |
Mar
(147) |
Apr
(51) |
May
(131) |
Jun
(70) |
Jul
(99) |
Aug
(49) |
Sep
(28) |
Oct
(37) |
Nov
(43) |
Dec
(50) |
| 2015 |
Jan
(53) |
Feb
(48) |
Mar
(49) |
Apr
(83) |
May
(44) |
Jun
(163) |
Jul
(58) |
Aug
(39) |
Sep
(105) |
Oct
(73) |
Nov
(57) |
Dec
(82) |
| 2016 |
Jan
(64) |
Feb
(60) |
Mar
(37) |
Apr
(42) |
May
(113) |
Jun
(51) |
Jul
(56) |
Aug
(37) |
Sep
(26) |
Oct
(40) |
Nov
(28) |
Dec
(19) |
| 2017 |
Jan
(27) |
Feb
(28) |
Mar
(27) |
Apr
(31) |
May
(8) |
Jun
(10) |
Jul
(23) |
Aug
(5) |
Sep
(7) |
Oct
(31) |
Nov
(3) |
Dec
(1) |
| 2018 |
Jan
(1) |
Feb
(9) |
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2019 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
(2) |
Aug
|
Sep
(2) |
Oct
(1) |
Nov
(1) |
Dec
|
| 2020 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
|
From: General m. l. f. g. users.
<gum...@li...> - 2021-09-24 17:11:16
|
Hi, I wanted to see if you guys could give me some insight on why I am having some I2C driver/comm issues with the RTC DS1340 chip on the Overo carrier board. We are using the rtc_ds1307 driver. I would say that its 50/50 that driver works on boot up. When I do a "hwclock" command it gives me the correct date/time and the RTC chip is keeping up with the date/time. When it doesn't work, when I do a "hwclock" command I get a "hwclock: RTC_RD_TIME: Invalid argument" response. When this happens, it seems that the whole I2C bus is dead. Something else to consider: When the driver is working and "hwclock" is successful: When I unload to unload the driver using "modprobe -r rtc_ds1307" and then execute the "i2cget -y 2 0x68 0" I get valid results from the "seconds" register of the chip. When the driver is not working and I unload the driver and execute the same "i2cget" command, I get "0x00" results for all registers. My hardware is listed below: GUM3703WE - Overo Board BRD900000000509-R1-C10110 - Overo Carrier Board V1 Also, two files are attached that show boot sequences of a working driver and non-working driver. Any ideas what's going on? Chris Parris Software Engineer Chemring Sensors and Electronic Systems 4205 Westinghouse Commons Drive Charlotte, NC 28273 Tel: 980-235-2308 Cell: 704-747-7675 Email: cp...@ch...<mailto:cp...@ch...> NOTICE This document, including any attachments and exhibits hereto, may contain technical data or information subject to the International Traffic in Arms Regulations (ITAR) or Export Administration Regulations (EAR) of the U.S. Government. This information is intended for the recipient only, and may not be exported, sold, released, transferred, or disclosed to foreign persons, inside or outside the United States without first obtaining the proper export authorization. Violators of the ITAR or EAR are subject to criminal fines and penalties under Title 22, U.S.C. Section 2778, and Title 50, U.S.C. Section 2410. The recipient shall include this notice verbatim with any reproduced portion of this document. NOTICE: This electronic communication, (including any attachments) is intended exclusively for the individuals or entities to which it is addressed. It may contain sensitive, restricted, or proprietary information. Any unauthorized disclosure, use, dissemination, or copying is strictly prohibited and may be unlawful. Furthermore, this communication may contain technical information that is subject to U.S. Export Control Laws, including the International Traffic in Arms Regulations (ITAR) or the Dept. of Commerce Export Administration Regulations (EAR). If so, transfer to a foreign national or representative of a foreign government or interest, even in the U.S., without prior Government authorization is prohibited and violation of such Export Control Laws is subject to significant penalties. If you have received this communication in error, please notify its sender immediately by replying and then permanently delete this communication from your IT system. |
|
From: General m. l. f. g. users.
<gum...@li...> - 2020-01-09 14:13:00
|
During a recent webinar, Toradex mentioned that work is in progress to support their Apalis IMX8 SoM on Gumstix Geppetto. I’m highly interested in using your service for a Apalis carrier board, when will this be availible? Best Regards, Matt -- Sent from: http://gumstix.8.x6.nabble.com/ |
|
From: General m. l. f. g. users.
<gum...@li...> - 2019-11-28 11:29:11
|
Attempting to build a yocto image using the "thud" release, bitbake fails on building the version of /u-boot/ that comes with the meta-gumstix thud branch, which is 2016.03 (which seems antique?). The error I'm seeing is regarding conflicting types, e.g. Searching the Internet for that, one quickly comes across a range of thread explaining that the problem is the/ libfdt-dev.h/ header that comes with the /dtc/ package. Which I see is required by the u-boot recipe in the gumstix layer for yocto: /DEPENDS += "dtc-native"/ See also https://patchwork.openembedded.org/patch/147816/ However, in the thread linked to above, we're talking versions 2018.01 and 2018.03, not 2016.03 The poky layer for thud brings u-boot 2018.07 which builds fine, but with that one, my overo (Airstorm-Y) won't boot anymore: I'm not entirely sure if this boot problem is related to the u-boot build or to the kernel image that I've built (see my previous thread)? Any tips on how I could solve this issue? Is there a more recent version of u-boot in a gumstix layer for yocto that I haven't discovered just yet, or do you have any other tips on how I could get a working yocto image for my overo? Thanks, David P.S. Note that during the build, I'm also seeing these warning, but I don't think there's an actual problem here: -- Sent from: http://gumstix.8.x6.nabble.com/ |
|
From: General m. l. f. g. users.
<gum...@li...> - 2019-10-01 19:43:05
|
My name is Javier, I am a university student in Ecuador, Some friends gave me a gumstix overo fire COM with a Tobi board, but unfortunately I can't find updated information about installing current versions of Ubuntu or Debian! I need to install Debian 9 and I followed the instructions on this website https://github.com/hackgnar/gumstix-overo-images/tree/master/debian but unfortunately the wifi did not work, I had an error "libertas_sdio: failed to find firmware (-2)" and I was reading and I found that the problem is in Kernel version that is very old "version 3.5.7-custom" I want to install a stable Linux version 4.9 and tried to update it but I can't, it's very difficult for my little experience with Linux! I have the problem that Overo does not recognize the new installed Kernel because it seems to me that the load partition (MLO, uImage, U-boot.img) does not match, with the new kernel!! In general, please, can you tell me how can I install the Debian 9 version? any advice or information will help me a lot! thank you Javier _____________________________________ Sent from http://gumstix.8.x6.nabble.com |
|
From: General m. l. f. g. users.
<gum...@li...> - 2019-09-18 14:05:08
|
Hello everyone, I have tried for several weeks to install Debian Stretch, but I had no luck, probably because of my lack of experience or it could be because of incorrect images and rootfs that I would be using I have tried to continue with the steps that are written here: https://github.com/hackgnar/gumstix-overo-images/tree/master/debian and in the creation of the ARM Debian OS I changed wheezy ./wheezy for stretch ./stretch in other words I did this *"sudo debootstrap --foreign --verbose --arch=armel --include=vim-nox,openssh-server,ntpdate,less,wireless-tools,wpasupplicant,dnsmasq,psmisc,locales,locales-all,screen --exclude=nano stretch ./stretch http://ftp.debian.org/debian/"* and I downloaded a Yocto image to use its kernel and firmware modules but not the one specified in the article, because in the result of the construction, installation and in the boot on the board Overo the WiFi module did not work I had a error "libertas sdio: failed to find firmware (-2)" I researched and found an explanation that the reason was because the kernel is too old for debian stretch Then make the decision to use the images and rootfs of this website *https://catalina.gumstix.com/binaries/10782/* at the beginning it starts well but then I have this kernel problem: [ 1243.688232] ------------[ cut here ]------------ [ 1243.693084] Kernel BUG at c00b3b0c [verbose debug info unavailable] [ 1243.699645] Internal error: Oops - BUG: 0 [#1] SMP ARM [ 1243.705017] Modules linked in: snd_soc_omap_twl4030 libertas_sdio libertas snd_soc_omap_mcbsp cfg80211 snd_soc_omap snd_pcm_dmaengine rfkill snd_soc_twl4030 snd_soc_core snd_pcm snd_timer snd soundcore mt9v032 twl4030_madc v4l2_common industrialio videodev edt_ft5x06 media ip_tables x_tables ipv6 [ 1243.732727] CPU: 0 PID: 2078 Comm: apt-get Not tainted 4.5.0-custom #1 [ 1243.739562] Hardware name: Generic OMAP3 (Flattened Device Tree) [ 1243.745819] task: de4a6380 ti: dd5b8000 task.ti: dd5b8000 [ 1243.751495] PC is at hrtimer_interrupt+0x1c8/0x204 [ 1243.756530] LR is at omap2_gp_timer_interrupt+0x24/0x34 [ 1243.761993] pc : [<c00b3b0c>] lr : [<c0026f7c>] psr: 60000193 [ 1243.761993] sp : dd5b9ee0 ip : c09a758c fp : 00000000 [ 1243.773986] r10: 00000000 r9 : c09a6984 r8 : 00000035 [ 1243.779449] r7 : 00000000 r6 : de016710 r5 : de016760 r4 : df8f2d80 [ 1243.786254] r3 : 00000000 r2 : c09a758c r1 : c0a6d74c r0 : c09ad880 [ 1243.793090] Flags: nZCv IRQs off FIQs on Mode SVC_32 ISA ARM Segment none [ 1243.800659] Control: 10c5387d Table: 9d6c0019 DAC: 00000051 [ 1243.806640] Process apt-get (pid: 2078, stack limit = 0xdd5b8218) [ 1243.813018] Stack: (0xdd5b9ee0 to 0xdd5ba000) [ 1243.817596] 9ee0: 00000000 00000000 de002000 60000193 c09a6984 c0093b94 00000001 00000080 [ 1243.826141] 9f00: 00000000 c09ad980 de016760 de016710 00000000 00000035 c09a6984 00000000 [ 1243.834686] 9f20: 00000000 c0026f7c c09ad980 c009f138 c009f408 00000000 c0382618 de016700 [ 1243.843231] 9f40: de016760 de016700 de016760 de016710 00000000 00000001 de002000 beb78214 [ 1243.851806] 9f60: beb782cc c009f410 de016700 de016760 de016710 c00a2510 c099e8ac 00000035 [ 1243.860351] 9f80: c09a758c c009e7dc c099e8ac c009ead0 b6aac400 60000010 ffffffff 10c5387d [ 1243.868896] 9fa0: 10c5387d 7f5fe830 beb78214 c069d7b4 b6f004c0 00000000 000000f8 0000003c [ 1243.877471] 9fc0: 00000030 b6b7d794 00000030 beb781e8 beb78298 7f5fe830 beb78214 beb782cc [ 1243.886016] 9fe0: b6cf9970 beb77fc0 b6aac3f4 b6aac400 60000010 ffffffff 00000000 00000000 [ 1243.894592] [<c00b3b0c>] (hrtimer_interrupt) from [<c0026f7c>] (omap2_gp_timer_interrupt+0x24/0x34) [ 1243.904052] [<c0026f7c>] (omap2_gp_timer_interrupt) from [<c009f138>] (handle_irq_event_percpu+0x44/0x2e4) [ 1243.914154] [<c009f138>] (handle_irq_event_percpu) from [<c009f410>] (handle_irq_event+0x38/0x5c) [ 1243.923431] [<c009f410>] (handle_irq_event) from [<c00a2510>] (handle_level_irq+0xc0/0x154) [ 1243.932159] [<c00a2510>] (handle_level_irq) from [<c009e7dc>] (generic_handle_irq+0x20/0x34) [ 1243.940979] [<c009e7dc>] (generic_handle_irq) from [<c009ead0>] (__handle_domain_irq+0x64/0xe0) [ 1243.950103] [<c009ead0>] (__handle_domain_irq) from [<c069d7b4>] (__irq_usr+0x54/0x80) [ 1243.958374] Code: e3c33004 e5c43046 e28dd024 e8bd8ff0 (e7f001f2) [ 1243.977966] ---[ end trace fe8e26092be0cefe ]--- [ 1243.982788] Kernel panic - not syncing: Fatal exception in interrupt [ 1243.989471] ---[ end Kernel panic - not syncing: Fatal exception in interrupt I understand that it is because not all the modules or drivers present are found How can I install the missing modules? or what is the best method of installing debian stretch in overo fire? thank you! -- Sent from: http://gumstix.8.x6.nabble.com/ |
|
From: General m. l. f. g. users.
<gum...@li...> - 2019-09-04 08:10:16
|
Hello everyone, I have tried for several weeks to install Debian Stretch, but I had no luck, probably because of my lack of experience or it could be because of incorrect images and rootfs that I would be using I have tried to continue with the steps that are written here: *https://github.com/hackgnar/gumstix-overo-images/tree/master/debian* and in the creation of the ARM Debian OS I changed wheezy ./wheezy for stretch ./stretch in other words I did this *"sudo debootstrap --foreign --verbose --arch=armel --include=vim-nox,openssh-server,ntpdate,less,wireless-tools,wpasupplicant,dnsmasq,psmisc,locales,locales-all,screen --exclude=nano stretch ./stretch http://ftp.debian.org/debian/"* and I downloaded a Yocto image to use its kernel and firmware modules but not the one specified in the article, because in the result of the construction, installation and in the boot on the board Overo the WiFi module did not work I had a error "libertas sdio: failed to find firmware (-2)" I researched and found an explanation that the reason was because the kernel is too old for debian stretch Then make the decision to use the images and rootfs of this website *https://catalina.gumstix.com/binaries/10782/* at the beginning it starts well but then I have this kernel problem: [ 1243.688232] ------------[ cut here ]------------ [ 1243.693084] Kernel BUG at c00b3b0c [verbose debug info unavailable] [ 1243.699645] Internal error: Oops - BUG: 0 [#1] SMP ARM [ 1243.705017] Modules linked in: snd_soc_omap_twl4030 libertas_sdio libertas snd_soc_omap_mcbsp cfg80211 snd_soc_omap snd_pcm_dmaengine rfkill snd_soc_twl4030 snd_soc_core snd_pcm snd_timer snd soundcore mt9v032 twl4030_madc v4l2_common industrialio videodev edt_ft5x06 media ip_tables x_tables ipv6 [ 1243.732727] CPU: 0 PID: 2078 Comm: apt-get Not tainted 4.5.0-custom #1 [ 1243.739562] Hardware name: Generic OMAP3 (Flattened Device Tree) [ 1243.745819] task: de4a6380 ti: dd5b8000 task.ti: dd5b8000 [ 1243.751495] PC is at hrtimer_interrupt+0x1c8/0x204 [ 1243.756530] LR is at omap2_gp_timer_interrupt+0x24/0x34 [ 1243.761993] pc : [<c00b3b0c>] lr : [<c0026f7c>] psr: 60000193 [ 1243.761993] sp : dd5b9ee0 ip : c09a758c fp : 00000000 [ 1243.773986] r10: 00000000 r9 : c09a6984 r8 : 00000035 [ 1243.779449] r7 : 00000000 r6 : de016710 r5 : de016760 r4 : df8f2d80 [ 1243.786254] r3 : 00000000 r2 : c09a758c r1 : c0a6d74c r0 : c09ad880 [ 1243.793090] Flags: nZCv IRQs off FIQs on Mode SVC_32 ISA ARM Segment none [ 1243.800659] Control: 10c5387d Table: 9d6c0019 DAC: 00000051 [ 1243.806640] Process apt-get (pid: 2078, stack limit = 0xdd5b8218) [ 1243.813018] Stack: (0xdd5b9ee0 to 0xdd5ba000) [ 1243.817596] 9ee0: 00000000 00000000 de002000 60000193 c09a6984 c0093b94 00000001 00000080 [ 1243.826141] 9f00: 00000000 c09ad980 de016760 de016710 00000000 00000035 c09a6984 00000000 [ 1243.834686] 9f20: 00000000 c0026f7c c09ad980 c009f138 c009f408 00000000 c0382618 de016700 [ 1243.843231] 9f40: de016760 de016700 de016760 de016710 00000000 00000001 de002000 beb78214 [ 1243.851806] 9f60: beb782cc c009f410 de016700 de016760 de016710 c00a2510 c099e8ac 00000035 [ 1243.860351] 9f80: c09a758c c009e7dc c099e8ac c009ead0 b6aac400 60000010 ffffffff 10c5387d [ 1243.868896] 9fa0: 10c5387d 7f5fe830 beb78214 c069d7b4 b6f004c0 00000000 000000f8 0000003c [ 1243.877471] 9fc0: 00000030 b6b7d794 00000030 beb781e8 beb78298 7f5fe830 beb78214 beb782cc [ 1243.886016] 9fe0: b6cf9970 beb77fc0 b6aac3f4 b6aac400 60000010 ffffffff 00000000 00000000 [ 1243.894592] [<c00b3b0c>] (hrtimer_interrupt) from [<c0026f7c>] (omap2_gp_timer_interrupt+0x24/0x34) [ 1243.904052] [<c0026f7c>] (omap2_gp_timer_interrupt) from [<c009f138>] (handle_irq_event_percpu+0x44/0x2e4) [ 1243.914154] [<c009f138>] (handle_irq_event_percpu) from [<c009f410>] (handle_irq_event+0x38/0x5c) [ 1243.923431] [<c009f410>] (handle_irq_event) from [<c00a2510>] (handle_level_irq+0xc0/0x154) [ 1243.932159] [<c00a2510>] (handle_level_irq) from [<c009e7dc>] (generic_handle_irq+0x20/0x34) [ 1243.940979] [<c009e7dc>] (generic_handle_irq) from [<c009ead0>] (__handle_domain_irq+0x64/0xe0) [ 1243.950103] [<c009ead0>] (__handle_domain_irq) from [<c069d7b4>] (__irq_usr+0x54/0x80) [ 1243.958374] Code: e3c33004 e5c43046 e28dd024 e8bd8ff0 (e7f001f2) [ 1243.977966] ---[ end trace fe8e26092be0cefe ]--- [ 1243.982788] Kernel panic - not syncing: Fatal exception in interrupt [ 1243.989471] ---[ end Kernel panic - not syncing: Fatal exception in interrupt I understand that it is because not all the modules or drivers present are found How can I install the missing modules? or what is the best method of installing debian stretch in overo fire? thank you! -- Sent from: http://gumstix.8.x6.nabble.com/ |
|
From: General m. l. f. g. users.
<gum...@li...> - 2019-07-25 21:18:24
|
I am having some trouble installing the generic arm Alpine Linux distro onto an Overo board. I am not sure how to complete the task of setting up the initramfs image and getting it to properly find the root file system during kernel initialization. Has anyone installed Alpine before on Overo? |
|
From: General m. l. f. g. users.
<gum...@li...> - 2019-07-25 14:17:43
|
Hello, According to GumStix's document, the UART Header (v17)(16) on Aerocore2 TX2 board is connected to UART3 bus on NVidia Jetson COM Connector. What device is this port connected to i.e /dev/ttyTHS3 or /dev/ttyTHS1 etc? I tried loopback on /dev/ttyTHS3 but does not work. I am using DTB file downloaded from GumStix website. How can I test UART Header (v17)(16) ? Thanks, Nimesh -- Sent from: http://gumstix.8.x6.nabble.com/ |
|
From: General m. l. f. g. users.
<gum...@li...> - 2019-06-13 20:16:48
|
Hello, I recently purchased a series of boards built from Gepetto. Those boards are really great. I try to build a new Yocto image with Qt5 support following the method proposed here: https://jumpnowtek.com/rpi/Raspberry-Pi-Systems-with-Yocto.html The method worked fully before (with a raspberry pi 3) but wit the new board the wifi doesn't work. I compiled the module for TI wl18xx, and so on. However, when I modprobe those modules I get these error messages: [ 400.820572] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 400.831058] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 400.837854] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 [ 400.846702] cfg80211: failed to load regulatory.db [ 400.916026] wl18xx_driver wl18xx.0.auto: Unbalanced pm_runtime_enable! [ 400.922800] wl18xx_driver wl18xx.0.auto: Direct firmware load for ti-connectivity/wl1271-nvs.bin failed with error -2 [ 400.933684] wl18xx_driver wl18xx.0.auto: Direct firmware load for ti-connectivity/wl18xx-conf.bin failed with error -2 [ 400.944608] wlcore: ERROR could not get configuration binary ti-connectivity/wl18xx-conf.bin: -2 [ 400.954234] wlcore: WARNING falling back to default config [ 400.991684] wl1271_sdio mmc1:0001:2: wl12xx_sdio_power_on: failed to get_sync(-13) Could you please help me to make this work? Thank you very much for your help!! Pierre -- "It doesn't matter how beautiful your theory is, it doesn't matter how smart you are. If it doesn't agree with experiment, it's wrong." Richard P. Feynman |
|
From: General m. l. f. g. users.
<gum...@li...> - 2019-04-24 19:32:03
|
can someone please direct me on how to get java on overo firestorm? I have tried following this guide https://github.com/gumstix/yocto-manifest/wiki/Java but it seems to be out of date and does not work. -- Sent from: http://gumstix.8.x6.nabble.com/ |
|
From: General m. l. f. g. users.
<gum...@li...> - 2018-11-02 16:54:01
|
Hi, I have a DuoVero Zephyr-Y I'm trying to read the ADC's on. I build the kernel through Yocoto, following the directions here: https://github.com/gumstix/yocto-manifest This is what uname shows: Linux duovero 3.18.21-custom #1 SMP Thu Nov 1 15:32:57 PDT 2018 armv7l GNU/Linux I have the twl4030_madc and twl_madc_hwmon kernel modules loaded: Module Size Used by twl4030_madc_hwmon 2650 0 twl4030_madc 9173 1 twl4030_madc_hwmon industrialio 27168 1 twl4030_madc The problem is none of the device paths I've seen in examples exist. There is no /dev/twl4030-madc and nothing under /sys/class/hwmon root@duovero:~# ls /dev autofs loop3 ram14 tty12 tty34 tty56 usbmon1 block loop4 ram15 tty13 tty35 tty57 usbmon2 bus loop5 ram2 tty14 tty36 tty58 usbmon3 char loop6 ram3 tty15 tty37 tty59 vcs console loop7 ram4 tty16 tty38 tty6 vcs1 cpu_dma_latency mem ram5 tty17 tty39 tty60 vcs2 disk memory_bandwidth ram6 tty18 tty4 tty61 vcs3 dri mmcblk0 ram7 tty19 tty40 tty62 vcs4 fb0 mmcblk0p1 ram8 tty2 tty41 tty63 vcs5 fd mmcblk0p2 ram9 tty20 tty42 tty7 vcs6 full mmcblk0p3 random tty21 tty43 tty8 vcsa i2c-0 mqueue rfkill tty22 tty44 tty9 vcsa1 i2c-1 network_latency rtc tty23 tty45 ttyGS0 vcsa2 i2c-2 network_throughput rtc0 tty24 tty46 ttyO0 vcsa3 i2c-3 null shm tty25 tty47 ttyO1 vcsa4 initctl psaux snd tty26 tty48 ttyO2 vcsa5 input ptmx stderr tty27 tty49 ttyO3 vcsa6 kmem pts stdin tty28 tty5 ttyS0 vhci kmsg ram0 stdout tty29 tty50 ttyS1 watchdog log ram1 tty tty3 tty51 ttyS2 watchdog0 loop-control ram10 tty0 tty30 tty52 ttyS3 zero loop0 ram11 tty1 tty31 tty53 ubi_ctrl loop1 ram12 tty10 tty32 tty54 urandom loop2 ram13 tty11 tty33 tty55 usbmon0 root@duovero:~# ls /sys/class/hwmon/ root@duovero:~# Any help would be greatly appreciated. |
|
From: General m. l. f. g. users.
<gum...@li...> - 2018-06-20 13:18:33
|
Hello everybody, I try, for a while now, to install on my Gumstix Overo, with Tobi platform, a Yocto distribution with Qt5 (5.10.1). The goal is to programming a Qt5 application on my Ubuntu virtual machine then cross compile it with QtCreator and run the application on it. I have followed many support but at the end I have nothing that works correctly. - I created a SD card bootable with Yocto Rocko and Qt5. - I compiled all the cross-compilation tools to use QtCreator on Ubuntu and compile code for the Gumstix. - I configured QtCreator for the cross-compilation. How can I run an graphical application on the Gumstix ? I can't use the gumstix with the keyboard beacause this dosen't works even with a XFCE kernel no idee why.... I only use putty and ssh connexion. I don't have touch screen or something like that, just a basic HDMI screen. my project: https://bitbucket.org/falcon1990/gumstixovero/src Somebody can please explain me how to do that ? Thanks. -- Sent from: http://gumstix.8.x6.nabble.com/ |
|
From: General m. l. f. g. users.
<gum...@li...> - 2018-04-09 19:42:13
|
Hi, I was wondering what caused one of my Overo to break. This is the first time it happens to us. This is my config. Overo Ironstorm Y Arbor43c MicroSD swissbit 8GB I have an Ironstorm Y that broke while it was in a system. It cause a kernel panic: [ 5.053863] List of all partitions: [ 5.057739] 0100 16384 ram0 (driver?) [ 5.062713] 0101 16384 ram1 (driver?) [ 5.067565] 0102 16384 ram2 (driver?) [ 5.072448] 0103 16384 ram3 (driver?) [ 5.077301] 0104 16384 ram4 (driver?) [ 5.082183] 0105 16384 ram5 (driver?) [ 5.087005] 0106 16384 ram6 (driver?) [ 5.091888] 0107 16384 ram7 (driver?) [ 5.096710] 0108 16384 ram8 (driver?) [ 5.101593] 0109 16384 ram9 (driver?) [ 5.106414] 010a 16384 ram10 (driver?) [ 5.111389] 010b 16384 ram11 (driver?) [ 5.116302] 010c 16384 ram12 (driver?) [ 5.121246] 010d 16384 ram13 (driver?) [ 5.126190] 010e 16384 ram14 (driver?) [ 5.131134] 010f 16384 ram15 (driver?) [ 5.136077] 1f00 512 mtdblock0 (driver?) [ 5.141418] 1f01 1792 mtdblock1 (driver?) [ 5.146728] 1f02 256 mtdblock2 (driver?) [ 5.152038] 1f03 8192 mtdblock3 (driver?) [ 5.157348] 1f04 1037824 mtdblock4 (driver?) [ 5.162658] b300 8068096 mmcblk0 driver: mmcblk [ 5.168212] b301 65536 mmcblk0p1 f7f5b4c2-01 [ 5.173797] b302 1048576 mmcblk0p2 f7f5b4c2-02 [ 5.179382] b303 1048576 mmcblk0p3 f7f5b4c2-03 [ 5.184936] b304 1 mmcblk0p4 [ 5.189544] b305 5265408 mmcblk0p5 f7f5b4c2-05 [ 5.195068] b306 524288 mmcblk0p6 f7f5b4c2-06 [ 5.200683] No filesystem could mount root, tried: ext3 [ 5.206237] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,2) [ 5.215209] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,2) I tried to put the same SD card in an other Overo, it works. The only thing that make the system do this kernel panic is the Overo COM. Does any one had this issue or knows what broke? -- Sent from: http://gumstix.8.x6.nabble.com/ |
|
From: General m. l. f. g. users.
<gum...@li...> - 2018-02-23 16:27:44
|
From: Drew Moseley <drew.moseley@northern.tech>
Signed-off-by: Drew Moseley <drew.moseley@northern.tech>
---
recipes-bsp/u-boot/u-boot-fw-utils_%.bbappend | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/recipes-bsp/u-boot/u-boot-fw-utils_%.bbappend b/recipes-bsp/u-boot/u-boot-fw-utils_%.bbappend
index f5fb31e..2158f14 100644
--- a/recipes-bsp/u-boot/u-boot-fw-utils_%.bbappend
+++ b/recipes-bsp/u-boot/u-boot-fw-utils_%.bbappend
@@ -1,5 +1,6 @@
-FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
+FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:${THISDIR}/u-boot:"
SRC_URI_append_overo := " file://fw_env.config"
+SRC_URI_append_overo := " file://0001-omap3_overo-Update-name-of-Filesystem-MTD-partition.patch"
# override the fw_env.config provided by the default recipe
do_install_append_overo () {
--
2.7.4
|
|
From: General m. l. f. g. users.
<gum...@li...> - 2018-02-20 01:44:11
|
From: Drew Moseley <drew.moseley@northern.tech>
Signed-off-by: Drew Moseley <drew.moseley@northern.tech>
---
recipes-core/systemd/systemd_%.bbappend | 1 -
1 file changed, 1 deletion(-)
diff --git a/recipes-core/systemd/systemd_%.bbappend b/recipes-core/systemd/systemd_%.bbappend
index 782585b..dc1a926 100644
--- a/recipes-core/systemd/systemd_%.bbappend
+++ b/recipes-core/systemd/systemd_%.bbappend
@@ -17,7 +17,6 @@ do_install_append() {
install -d ${D}${sysconfdir}/systemd/network/
install -m 0644 ${WORKDIR}/*.network ${D}${sysconfdir}/systemd/network/
install -m 0644 ${WORKDIR}/*.link ${D}${sysconfdir}/systemd/network/
- ln -s /run/systemd/resolve/resolv.conf ${D}${sysconfdir}/resolv.conf
}
USERADD_PARAM_${PN} = "--system --home /dev/null systemd-journal-gateway"
--
2.7.4
|
|
From: General m. l. f. g. users.
<gum...@li...> - 2018-02-20 01:42:10
|
This patch doesn't work. Evidently there is an ordering issue. I'll
send another that simply removes this line of code.
Drew
On 02/19/2018 04:35 PM, drew.moseley@northern.tech wrote:
> From: Drew Moseley <drew.moseley@northern.tech>
>
> In some cases it is created already by upstream layers.
>
> Signed-off-by: Drew Moseley <drew.moseley@northern.tech>
> ---
> recipes-core/systemd/systemd_%.bbappend | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/recipes-core/systemd/systemd_%.bbappend b/recipes-core/systemd/systemd_%.bbappend
> index 782585b..be9c96d 100644
> --- a/recipes-core/systemd/systemd_%.bbappend
> +++ b/recipes-core/systemd/systemd_%.bbappend
> @@ -17,7 +17,9 @@ do_install_append() {
> install -d ${D}${sysconfdir}/systemd/network/
> install -m 0644 ${WORKDIR}/*.network ${D}${sysconfdir}/systemd/network/
> install -m 0644 ${WORKDIR}/*.link ${D}${sysconfdir}/systemd/network/
> - ln -s /run/systemd/resolve/resolv.conf ${D}${sysconfdir}/resolv.conf
> + if [ ! -e ${D}${sysconfdir}/resolv.conf ]; then
> + ln -s /run/systemd/resolve/resolv.conf ${D}${sysconfdir}/resolv.conf
> + fi
> }
>
> USERADD_PARAM_${PN} = "--system --home /dev/null systemd-journal-gateway"
|
|
From: General m. l. f. g. users.
<gum...@li...> - 2018-02-19 21:43:19
|
From: Drew Moseley <drew.moseley@northern.tech>
Signed-off-by: Drew Moseley <drew.moseley@northern.tech>
---
...o-Update-name-of-Filesystem-MTD-partition.patch | 46 ++++++++++++++++++++++
recipes-bsp/u-boot/u-boot_2016.03.bbappend | 1 +
2 files changed, 47 insertions(+)
create mode 100644 recipes-bsp/u-boot/u-boot/0001-omap3_overo-Update-name-of-Filesystem-MTD-partition.patch
diff --git a/recipes-bsp/u-boot/u-boot/0001-omap3_overo-Update-name-of-Filesystem-MTD-partition.patch b/recipes-bsp/u-boot/u-boot/0001-omap3_overo-Update-name-of-Filesystem-MTD-partition.patch
new file mode 100644
index 0000000..417d180
--- /dev/null
+++ b/recipes-bsp/u-boot/u-boot/0001-omap3_overo-Update-name-of-Filesystem-MTD-partition.patch
@@ -0,0 +1,46 @@
+From 2970d93694f84ae8d8a40259b201a3d5d4715761 Mon Sep 17 00:00:00 2001
+From: Drew Moseley <drew.moseley@northern.tech>
+Date: Thu, 15 Feb 2018 17:59:32 -0500
+Subject: [PATCH 1/2] omap3_overo: Update name of Filesystem MTD partition.
+
+This is to sync up with the name expected by the kernel.
+
+Signed-off-by: Drew Moseley <drew.moseley@northern.tech>
+---
+ include/configs/omap3_overo.h | 6 +++---
+ 1 file changed, 3 insertions(+), 3 deletions(-)
+
+diff --git a/include/configs/omap3_overo.h b/include/configs/omap3_overo.h
+index 3b1e5d7ff8..f66a7b00b8 100644
+--- a/include/configs/omap3_overo.h
++++ b/include/configs/omap3_overo.h
+@@ -74,7 +74,7 @@
+ * uboot 14 * NAND_BLOCK_SIZE = 1792 KiB
+ * uboot environtment 2 * NAND_BLOCK_SIZE = 256 KiB
+ * linux 64 * NAND_BLOCK_SIZE = 8 MiB
+- * rootfs remainder
++ * Filesystem remainder
+ */
+ #define MTDIDS_DEFAULT "nand0=omap2-nand.0"
+ #define MTDPARTS_DEFAULT "mtdparts=omap2-nand.0:" \
+@@ -82,7 +82,7 @@
+ "1792k(u-boot)," \
+ "256k(environ)," \
+ "8m(linux)," \
+- "-(rootfs)"
++ "-(Filesystem)"
+ #else /* CONFIG_NAND */
+ #define MTDPARTS_DEFAULT
+ #endif /* CONFIG_NAND */
+@@ -148,7 +148,7 @@
+ "fi;\0" \
+ "nanddtsboot=echo Booting from nand with DTS...; " \
+ "run nandargs; " \
+- "ubi part rootfs; "\
++ "ubi part Filesystem; "\
+ "ubifsmount ubi0:rootfs; "\
+ "run loadubifdt; "\
+ "run loadubizimage; "\
+--
+2.11.0
+
diff --git a/recipes-bsp/u-boot/u-boot_2016.03.bbappend b/recipes-bsp/u-boot/u-boot_2016.03.bbappend
index 3599d8b..7f457fe 100644
--- a/recipes-bsp/u-boot/u-boot_2016.03.bbappend
+++ b/recipes-bsp/u-boot/u-boot_2016.03.bbappend
@@ -11,6 +11,7 @@ SRC_URI = " \
file://0007-Add-support-for-the-Atheros-AR8035-Gigabit-Ethernet.patch \
file://0008-Revert-ti-armv7-enable-EXT-support-in-SPL-using-ti_a.patch \
file://0009-Update-uboot-config-for-DuoVero.patch \
+ file://0001-omap3_overo-Update-name-of-Filesystem-MTD-partition.patch \
"
--
2.7.4
|
|
From: General m. l. f. g. users.
<gum...@li...> - 2018-02-19 21:43:18
|
From: Drew Moseley <drew.moseley@northern.tech> This allows it to be used by recipes other than linux-yocto. Specifically, the Mender client integration requires it for packaging the right files. Signed-off-by: Drew Moseley <drew.moseley@northern.tech> --- conf/machine/duovero.conf | 4 ++++ conf/machine/overo.conf | 17 +++++++++++++++++ conf/machine/pepper.conf | 6 ++++++ conf/machine/poblano.conf | 2 ++ recipes-kernel/linux/linux-yocto_4.8.bbappend | 27 --------------------------- 5 files changed, 29 insertions(+), 27 deletions(-) diff --git a/conf/machine/duovero.conf b/conf/machine/duovero.conf index 3acda0a..22461a4 100644 --- a/conf/machine/duovero.conf +++ b/conf/machine/duovero.conf @@ -9,6 +9,10 @@ TARGET_ARCH = "arm" # builds for Pepper and Overo. DEFAULTTUNE ?= "cortexa8hf-neon" +KERNEL_DEVICETREE = "omap4-duovero-parlor.dtb \ + omap4-duovero-garret50c.dtb \ +" + require conf/machine/include/soc-family.inc require conf/machine/include/tune-cortexa8.inc diff --git a/conf/machine/overo.conf b/conf/machine/overo.conf index 12c5b4b..9c90890 100644 --- a/conf/machine/overo.conf +++ b/conf/machine/overo.conf @@ -7,6 +7,23 @@ TARGET_ARCH = "arm" # DEFAULTTUNE makes it possible to build for the ARM hardfloat ABI. DEFAULTTUNE ?= "cortexa8hf-neon" +KERNEL_DEVICETREE = " \ + omap3-overo-storm-tobi.dtb omap3-overo-tobi.dtb \ + omap3-overo-storm-tobiduo.dtb omap3-overo-tobiduo.dtb \ + omap3-overo-storm-chestnut43.dtb omap3-overo-chestnut43.dtb \ + omap3-overo-storm-alto35.dtb omap3-overo-alto35.dtb \ + omap3-overo-storm-arbor43c.dtb omap3-overo-arbor43c.dtb \ + omap3-overo-storm-arbor43c1.dtb omap3-overo-arbor43c1.dtb \ + omap3-overo-storm-arbor50c.dtb omap3-overo-arbor50c.dtb \ + omap3-overo-storm-arbor70c.dtb omap3-overo-arbor70c.dtb \ + omap3-overo-storm-gallop43.dtb omap3-overo-gallop43.dtb \ + omap3-overo-storm-palo43.dtb omap3-overo-palo43.dtb \ + omap3-overo-storm-palo35.dtb omap3-overo-palo35.dtb \ + omap3-overo-storm-summit.dtb omap3-overo-summit.dtb \ + omap3-overo-storm-swd-jtag.dtb \ + omap3-overo-storm-thumbo.dtb omap3-overo-thumbo.dtb \ +" + require conf/machine/include/soc-family.inc require conf/machine/include/tune-cortexa8.inc diff --git a/conf/machine/pepper.conf b/conf/machine/pepper.conf index 80444f4..729ee78 100644 --- a/conf/machine/pepper.conf +++ b/conf/machine/pepper.conf @@ -7,6 +7,12 @@ TARGET_ARCH = "arm" # DEFAULTTUNE makes it possible to build for the ARM hardfloat ABI. DEFAULTTUNE ?= "cortexa8hf-neon" +KERNEL_DEVICETREE = "am335x-pepper.dtb \ + am335x-pepper-43r.dtb \ + am335x-pepper-43c.dtb \ + am335x-pepper-dvi.dtb \ +" + require conf/machine/include/soc-family.inc require conf/machine/include/tune-cortexa8.inc diff --git a/conf/machine/poblano.conf b/conf/machine/poblano.conf index cac282a..feb67db 100644 --- a/conf/machine/poblano.conf +++ b/conf/machine/poblano.conf @@ -7,6 +7,8 @@ TARGET_ARCH = "arm" # DEFAULTTUNE makes it possible to build for the ARM hardfloat ABI. DEFAULTTUNE ?= "cortexa8hf-neon" +KERNEL_DEVICETREE = "am437x-poblano.dtb" + require conf/machine/include/soc-family.inc require conf/machine/include/tune-cortexa8.inc diff --git a/recipes-kernel/linux/linux-yocto_4.8.bbappend b/recipes-kernel/linux/linux-yocto_4.8.bbappend index d73cd82..2973a6e 100644 --- a/recipes-kernel/linux/linux-yocto_4.8.bbappend +++ b/recipes-kernel/linux/linux-yocto_4.8.bbappend @@ -3,33 +3,6 @@ COMPATIBLE_MACHINE += "poblano|overo|duovero|pepper|" # Pull in the devicetree files into the rootfs RDEPENDS_kernel-base += "kernel-devicetree" -KERNEL_DEVICETREE_overo = " \ - omap3-overo-storm-tobi.dtb omap3-overo-tobi.dtb \ - omap3-overo-storm-tobiduo.dtb omap3-overo-tobiduo.dtb \ - omap3-overo-storm-chestnut43.dtb omap3-overo-chestnut43.dtb \ - omap3-overo-storm-alto35.dtb omap3-overo-alto35.dtb \ - omap3-overo-storm-arbor43c.dtb omap3-overo-arbor43c.dtb \ - omap3-overo-storm-arbor43c1.dtb omap3-overo-arbor43c1.dtb \ - omap3-overo-storm-arbor50c.dtb omap3-overo-arbor50c.dtb \ - omap3-overo-storm-arbor70c.dtb omap3-overo-arbor70c.dtb \ - omap3-overo-storm-gallop43.dtb omap3-overo-gallop43.dtb \ - omap3-overo-storm-palo43.dtb omap3-overo-palo43.dtb \ - omap3-overo-storm-palo35.dtb omap3-overo-palo35.dtb \ - omap3-overo-storm-summit.dtb omap3-overo-summit.dtb \ - omap3-overo-storm-swd-jtag.dtb \ - omap3-overo-storm-thumbo.dtb omap3-overo-thumbo.dtb \ -" -KERNEL_DEVICETREE_duovero = "omap4-duovero-parlor.dtb \ - omap4-duovero-garret50c.dtb \ -" -KERNEL_DEVICETREE_pepper = "am335x-pepper.dtb \ - am335x-pepper-43r.dtb \ - am335x-pepper-43c.dtb \ - am335x-pepper-dvi.dtb \ -" - -KERNEL_DEVICETREE_poblano = "am437x-poblano.dtb" - LINUX_VERSION_EXTENSION = "-custom" BOOT_SPLASH ?= "logo_linux_clut224-generic.ppm" -- 2.7.4 |
|
From: General m. l. f. g. users.
<gum...@li...> - 2018-02-19 21:43:18
|
From: Drew Moseley <drew.moseley@northern.tech>
The need for this file was removed with commit 8fc6c64f35b44b90e311889f59555804361ce4dc
Signed-off-by: Drew Moseley <drew.moseley@northern.tech>
---
recipes-bsp/u-boot/u-boot.inc | 9 ---------
1 file changed, 9 deletions(-)
delete mode 100644 recipes-bsp/u-boot/u-boot.inc
diff --git a/recipes-bsp/u-boot/u-boot.inc b/recipes-bsp/u-boot/u-boot.inc
deleted file mode 100644
index bf01911..0000000
--- a/recipes-bsp/u-boot/u-boot.inc
+++ /dev/null
@@ -1,9 +0,0 @@
-require ${COREBASE}/meta/recipes-bsp/u-boot/u-boot.inc
-
-# The license text is moved from a "COPYING" file to the beginning of
-# the README on recent versions of u-boot.
-LIC_FILES_CHKSUM = "file://README;beginline=1;endline=6;md5=157ab8408beab40cd8ce1dc69f702a6c"
-
-# To deploy a u-boot environment file, uncomment these lines
-#UBOOT_ENV = "uEnv"
-#SRC_URI_append = " file://uEnv.txt"
--
2.7.4
|
|
From: General m. l. f. g. users.
<gum...@li...> - 2018-02-19 21:42:02
|
From: Drew Moseley <drew.moseley@northern.tech> Signed-off-by: Drew Moseley <drew.moseley@northern.tech> --- conf/machine/overo.conf | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/conf/machine/overo.conf b/conf/machine/overo.conf index 9c90890..623c0e4 100644 --- a/conf/machine/overo.conf +++ b/conf/machine/overo.conf @@ -65,12 +65,13 @@ SERIAL_CONSOLES = "115200;ttyO2" IMAGE_FSTYPES ?= "tar.bz2 ubi" # The magic numbers: -# 512 MiB flash = 4096 PEBs (physical erase blocks) (PEB = 128 KiB sector) -# Manufacturer's spec is minimum 4016 PEBs are good for lifetime +# 1024 MiB flash = 8192 PEBs (physical erase blocks) (PEB = 128 KiB sector) +# Manufacturer's spec for the old 512MiB version minimum 4016 PEBs are good for lifetime +# I'm assuming that for the 1024MiB version, the minimum is 8032 PEBs # Logical erase block is PEB minus 2 KiB (NAND page size) for metadata # Partitions reserve 4+14+2+64 PEBS for xloader/u-boot/env/linux -# Minimum remaining available for rootfs: 3932 PEBs (likewise 3932 LEBs) -MKUBIFS_ARGS = "-F -m 2048 -e 126KiB -c 3932" +# Minimum remaining available for rootfs: 7948 PEBs (likewise 7948 LEBs) +MKUBIFS_ARGS = "-F -m 2048 -e 126KiB -c 7948" UBINIZE_ARGS = "-m 2048 -p 128KiB -s 512" UBI_VOLNAME = "rootfs" -- 2.7.4 |
|
From: General m. l. f. g. users.
<gum...@li...> - 2018-02-19 21:35:29
|
From: Drew Moseley <drew.moseley@northern.tech>
In some cases it is created already by upstream layers.
Signed-off-by: Drew Moseley <drew.moseley@northern.tech>
---
recipes-core/systemd/systemd_%.bbappend | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/recipes-core/systemd/systemd_%.bbappend b/recipes-core/systemd/systemd_%.bbappend
index 782585b..be9c96d 100644
--- a/recipes-core/systemd/systemd_%.bbappend
+++ b/recipes-core/systemd/systemd_%.bbappend
@@ -17,7 +17,9 @@ do_install_append() {
install -d ${D}${sysconfdir}/systemd/network/
install -m 0644 ${WORKDIR}/*.network ${D}${sysconfdir}/systemd/network/
install -m 0644 ${WORKDIR}/*.link ${D}${sysconfdir}/systemd/network/
- ln -s /run/systemd/resolve/resolv.conf ${D}${sysconfdir}/resolv.conf
+ if [ ! -e ${D}${sysconfdir}/resolv.conf ]; then
+ ln -s /run/systemd/resolve/resolv.conf ${D}${sysconfdir}/resolv.conf
+ fi
}
USERADD_PARAM_${PN} = "--system --home /dev/null systemd-journal-gateway"
--
2.7.4
|
|
From: General m. l. f. g. users.
<gum...@li...> - 2018-02-05 18:38:34
|
Hi everyone, I have an Overo IronSTORM COM (bought early 2012 - never had any use for it.). I installed Yocto (tried two separate builds) on a microSD card, following the instructions on Gumstix.com perfectly. I also have a Tobi Board - just purchased. All I want is for the thing to turn on. When I attach the two and put in the SD card and power, I see a solid red light on the Tobi next to the ethernet, and a solid green light on the Overo. Nothing boots. Depending on the voltage (bought an AC-DC power adapter) sometimes I see the two lights flashing at various speeds, but I’m not sure if the red light is supposed to come on. Also, there’s no console output. Nothing. Zero. Not even an error. When I first start to touch the COM and the Tobi to attach I’ll sometimes see dots (periods), and weird symbols. Not code. There’s also no HDMI output. Tried multiple monitors and systems. This thing could be so cool, but it doesn’t seem to be working. Do I have a lemon? Any help is truly appreciated. -- Sent from: http://gumstix.8.x6.nabble.com/ |
|
From: General m. l. f. g. users.
<gum...@li...> - 2018-01-30 23:11:36
|
[Dears, I've had a question since I've bought an AeroCore 2 for Dragonboard 410c. How can I access the AeroCore 2 GPIO through a C++ code? I've been looking for functions or alternatives that could help me yet I couldn't find them. I need to install ultrassonics sensors on my MAV, but I don't know how to do this using AeroCore 2 and GPIO. Does anyone know what I can try? Thanks for the help. -- Sent from: http://gumstix.8.x6.nabble.com/ |
|
From: General m. l. f. g. users.
<gum...@li...> - 2017-12-03 21:26:17
|
Hi, We are using the Krogoth build and are getting the following error when starting up bluetooth: hciattach -n ttyO1 texas Found a Texas Instruments' chip! Firmware file : /lib/firmware/TIInit_11.8.108.bts can't open firmware file: No such file or directory Warning: cannot find BTS file: /lib/firmware/TIInit_11.8.*108*.bts Can't init device hci0: Invalid argument (22)Can't initialize device: Invalid argument Currently only TIInit_11.8.*32*.bts is shipped in the Krogoth builds. After querying the chip directly, we got the following hex output for the firmware version: 0xAC6C The driver obtains the required firmware version using the following code from "hciattach_ti.c": chip = (version & 0x7C00) >> 10; min_ver = (version & 0x007F); maj_ver = (version & 0x0380) >> 7; if (version & 0x8000) maj_ver |= 0x0008; This comes out as 11.8.108. Anyone have any ideas on a way forward from here? Thank you! Liam Bunn -- Sent from: http://gumstix.8.x6.nabble.com/ |
|
From: General m. l. f. g. users.
<gum...@li...> - 2017-11-20 07:47:44
|
I am trying to make a bootable microSD with reference to the following. https://www.gumstix.com/support/getting-started/create-bootable-microsd-card/ <https://www.gumstix.com/support/getting-started/create-bootable-microsd-card/> However, I do not know how to create bootable microSD using zImage. I used TI 's sdk to build kernel. http://processors.wiki.ti.com/index.php/WL18xx_System_Build_Scripts <http://processors.wiki.ti.com/index.php/WL18xx_System_Build_Scripts> -- Sent from: http://gumstix.8.x6.nabble.com/ |
592 messages has been excluded from this view by a project administrator.