Hi,
Someone know if Olimex plan to release an ArchLinux (or other distrib) with a more recent kernel, with more drivers ?
A good minimal software support is essential to make this board really, really attractive.
Regards,
Laurent
we still lack support for audio and video to may release proper image with latest kernel
Quote from: olimex on November 28, 2012, 12:08:43 PM
we still lack support for audio and video to may release proper image with latest kernel
Thanks for your fast reply.
Is there a way to obtain a pre-release with the ease-to-use of a distribution like ArchLinux ?
Who's working on it ?
The community don't seems to be very important ?
Freescale provide any kind of support for this kernel port ?
+1 for giving us what you currently have. It would be really nice to have one place, one repository, from where we can download compiled images and put them on the SD card. I really do not want to spend time and efforts compiling kernel or making rootfs.
Ivan
I've got a version hot off kernel.org that I'll try to post somewhere this weekend... I compiled it last night, just need to load it on an sdcard and run it through its paces. I may even try to package it up and just drop it in the AUR.
Quote from: laurent on November 28, 2012, 12:38:24 PM
Is there a way to obtain a pre-release with the ease-to-use of a distribution like ArchLinux ?
Who's working on it ?
The community don't seems to be very important ?
Freescale provide any kind of support for this kernel port ?
You can find pre compiled kernel 3.7-rc4 following this topic:
https://www.olimex.com/forum/index.php?topic=327.msg1231#msg1231
there are also instructions how to install on your SD card
Fadil Berisha
Quote from: Fadil Berisha on November 28, 2012, 04:53:36 PM
You can find pre compiled kernel 3.7-rc4 following this topic:
https://www.olimex.com/forum/index.php?topic=327.msg1231#msg1231
there are also instructions how to install on your SD card
Fadil Berisha
Thank you Fadil Berisha.
This image is very small, does it contains some of useful utils usuay found on Linux distros ?
I'm going to test it very soon.
This image could also be very useful for me since I bought the Asix USB-Ethernet adapter from Olimex.
Regards,
Laurent
This is only kernel - install on 1st partition. Second partition should contain your rootfs (archlinux, debian etc).
Fadil Berisha
Quote from: Fadil Berisha on November 28, 2012, 11:55:01 PM
This is only kernel - install on 1st partition. Second partition should contain your rootfs (archlinux, debian etc).
Fadil Berisha
Okay, thanks again ;)
I've just tested it, obviously, without success. I tested on a spare 1Gb uSD.
I can't now, but I'll soon test this on the first partition of the original 2Gb uSD from Olimex (of course, I've already backuped it).
Quote from: laurent on November 29, 2012, 12:09:10 AM
Quote from: Fadil Berisha on November 28, 2012, 11:55:01 PM
This is only kernel - install on 1st partition. Second partition should contain your rootfs (archlinux, debian etc).
Fadil Berisha
Okay, thanks again ;)
I've just tested it, obviously, without success. I tested on a spare 1Gb uSD.
I can't now, but I'll soon test this on the first partition of the original 2Gb uSD from Olimex (of course, I've already backuped it).
I already test it with debian fs (work with 2.6 kernel) and I can't boot with this kernel.
Hi --,
could you please let me know how exactly to copy new kernel to boot partition?
I use the standard rootfs image from Archlinuxarm and have three partitions
Device Boot Start End Blocks Id System
/dev/mmcblk0p1 * 2048 67583 32768 53 OnTrack DM6 Aux3
/dev/mmcblk0p2 67584 3164159 1548288 83 Linux
/dev/mmcblk0p3 3164160 5261311 1048576 82 Linux swap / Solaris
The boot partition mmcblk0p1 is not mounted and /boot contains following files:
-rw-r--r-- 1 root 48K Sep 21 19:04 config-2.6.35-8-ARCH+
-rw-r--r-- 1 root 2.0M Sep 21 19:04 oli-2.6.35-8-ARCH+-ntsc.sb
-rw-r--r-- 1 root 2.0M Sep 21 19:04 oli-2.6.35-8-ARCH+-pal.sb
-rwxr-xr-x 1 root 2.0M Sep 21 19:04 zImage*
Where and how to copy sd_mmc_bootstream.raw ?
Many thanks!
srdjan
Quote from: bsrdjan on December 20, 2012, 11:12:28 PM
Hi --,
could you please let me know how exactly to copy new kernel to boot partition?
I use the standard rootfs image from Archlinuxarm and have three partitions
Device Boot Start End Blocks Id System
/dev/mmcblk0p1 * 2048 67583 32768 53 OnTrack DM6 Aux3
/dev/mmcblk0p2 67584 3164159 1548288 83 Linux
/dev/mmcblk0p3 3164160 5261311 1048576 82 Linux swap / Solaris
Image sd_mmc_bootstream.raw found at https://www.dropbox.com/s/rfnmzdbcu21pfgf/sd_mmc_bootstream.raw is kernel 3.7-rc4 with wifi support. Included driver is rtl8188. It work with imx23-olinuxino-mini board. I tested also with imx23-olinuxino-maxi with rtl USB dongle connected on USB port. I do not have imx23-olinuxino-micro, but for sure will work on that board too.
Image contain bootlets+kernel+dts_file. This image should be installed on 1st partition of your SD card. Second partition contain any rootfs (Yocto, arch, debian etc). I am using Yocto with no X server. Booting process is possible to track with debug console. All board control is done with ssh. I am doing cross compile on my PC and transfer files via network.
To get kernel 3.7-rc4 with wifi support please follow those steps:
1. On your linux PC machine, download image https://www.dropbox.com/s/rfnmzdbcu21pfgf/sd_mmc_bootstream.raw.
2. Insert SD card on your linux PC machine and identify how is recognized SD card on your PC machine. Run command:
sudo fdisk -l
I am getting /dev/sda and /dev/sdb. Device sdb is my SD card.
3. Copy image on 1st partition /dev/sdb1:
sudo dd if=sd_mmc_bootstream.raw of=/dev/sdb1
4. Insert SD card on your olinuxino board.
5. Connect USB-serial cable on olinuxino board (see olinuxino manual - debug connector)
6. Connect USB-serial cable on your PC. Open console on PC and start your terminal program. I am using
minicom with following setting: E - Bps/Par/Bits : 115200 8N1
7. power ON olinuxino board.
After boot, check with iwconfig, wifi device should be wlan0 or wlan1.
Message to Olimex, bsrdjan, JaG, laurent, idragoev:
Can someone of you please confirm this procedure. Needed imx23-olinuxino-mini and USB-serial cable.
I am working on mini howto prepare sd_mmc_bootstream.raw file based on latest kernel 3.7. This kernel support USB, SPI, I2C and wifi.
If everything goes well, next step would be TV-out support.
Regards
Fadil Berisha
I can confirm the kernel 3.7 boots on IMX233-MAXI, the only device one I have.
After login via USB-serial cable, the free -h shows 42 MB free
-/+ buffers/cache: 9.0M 42M
comparing to 2.6.38 kernel showing 50 MB after boot
-/+ buffers/cache: 8.2M 50M
I could not test WLAN, also could not connect via LAN as the device usb0 has not been found. Below are my boot messages.
Should kernel 3 be used on iMX233-MAXI and how to get LAN working?
Arch Linux 2.6.35-8-ARCH+ (ttyAMA0)
imx233 login: HTLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLC
PowerPrep start initialize power...
Battery Voltage = 0.76V
No battery or bad battery detected!!!.Dis8
EMI_CTRL 0x1C084040
FRAC 0x92926192
init_ddr_mt46v32m16_133Mhz
power 0x00820710
Frac 0x92926192
start change cpu freq
hbus 0x00000003
cpu 0x00010001
LLLLLLLFCLJUncompressing Linux... done, booting the kernel.
[ 0.000000] Booting Linux on physical CPU 0
[ 0.000000] Linux version 3.7.0-rc4 (devel@laptop) (gcc version 4.4.5 (Debia2
[ 0.000000] CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
[ 0.000000] CPU: VIVT data cache, VIVT instruction cache
[ 0.000000] Machine: Freescale i.MX23 (Device Tree), model: i.MX23 Olinuxinod
[ 0.000000] Memory policy: ECC disabled, Data cache writeback
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pa6
[ 0.000000] Kernel command line: noinitrd console=ttyAMA0,115200 root=/dev/mt
[ 0.000000] PID hash table entries: 256 (order: -2, 1024 bytes)
[ 0.000000] Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
[ 0.000000] Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.000000] Memory: 64MB = 64MB total
[ 0.000000] Memory: 53020k/53020k available, 12516k reserved, 0K highmem
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
[ 0.000000] vmalloc : 0xc4800000 - 0xff000000 ( 936 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xc4000000 ( 64 MB)
[ 0.000000] modules : 0xbf000000 - 0xc0000000 ( 16 MB)
[ 0.000000] .text : 0xc0008000 - 0xc05ccf74 (5908 kB)
[ 0.000000] .init : 0xc05cd000 - 0xc05f0950 ( 143 kB)
[ 0.000000] .data : 0xc05f2000 - 0xc06460d8 ( 337 kB)
[ 0.000000] .bss : 0xc06460fc - 0xc0b99e88 (5456 kB)
[ 0.000000] SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, 1
[ 0.000000] NR_IRQS:16 nr_irqs:16 16
[ 0.000000] of_irq_init: children remain, but no parents
[ 0.000000] sched_clock: 32 bits at 100 Hz, resolution 10000000ns, wraps eves
[ 0.000000] Console: colour dummy device 80x30
[ 0.000000] Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingr
[ 0.000000] ... MAX_LOCKDEP_SUBCLASSES: 8
[ 0.000000] ... MAX_LOCK_DEPTH: 48
[ 0.000000] ... MAX_LOCKDEP_KEYS: 8191
[ 0.000000] ... CLASSHASH_SIZE: 4096
[ 0.000000] ... MAX_LOCKDEP_ENTRIES: 16384
[ 0.000000] ... MAX_LOCKDEP_CHAINS: 32768
[ 0.000000] ... CHAINHASH_SIZE: 16384
[ 0.000000] memory used by lock dependency info: 3695 kB
[ 0.000000] per task-struct memory footprint: 1152 bytes
[ 0.070000] Calibrating delay loop... 226.09 BogoMIPS (lpj=1130496)
[ 0.070000] pid_max: default: 32768 minimum: 301
[ 0.070000] Mount-cache hash table entries: 512
[ 0.080000] CPU: Testing write buffer coherency: ok
[ 0.080000] Setting up static identity map for 0x4043d260 - 0x4043d2b8
[ 0.090000] devtmpfs: initialized
[ 0.100000] pinctrl core: initialized pinctrl subsystem
[ 0.110000] regulator-dummy: no parameters
[ 0.110000] NET: Registered protocol family 16
[ 0.110000] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.160000] Serial: AMBA PL011 UART driver
[ 0.160000] 80070000.serial: ttyAMA0 at MMIO 0x80070000 (irq = 125) is a PL02
[ 0.350000] console [ttyAMA0] enabled
[ 0.420000] bio: create slab <bio-0> at 0
[ 0.430000] mxs-dma 80004000.dma-apbh: initialized
[ 0.440000] mxs-dma 80024000.dma-apbx: initialized
[ 0.450000] usb0_vbus: 5000 mV
[ 0.450000] SCSI subsystem initialized
[ 0.460000] usbcore: registered new interface driver usbfs
[ 0.460000] usbcore: registered new interface driver hub
[ 0.470000] usbcore: registered new device driver usb
[ 0.480000] Advanced Linux Sound Architecture Driver Initialized.
[ 0.500000] cfg80211: Calling CRDA to update world regulatory domain
[ 0.510000] Switching to clocksource mxs_timer
[ 0.780000] NET: Registered protocol family 2
[ 0.790000] TCP established hash table entries: 2048 (order: 2, 16384 bytes)
[ 0.790000] TCP bind hash table entries: 2048 (order: 4, 73728 bytes)
[ 0.800000] TCP: Hash tables configured (established 2048 bind 2048)
[ 0.810000] TCP: reno registered
[ 0.810000] UDP hash table entries: 256 (order: 2, 20480 bytes)
[ 0.820000] UDP-Lite hash table entries: 256 (order: 2, 20480 bytes)
[ 0.830000] NET: Registered protocol family 1
[ 0.840000] RPC: Registered named UNIX socket transport module.
[ 0.840000] RPC: Registered udp transport module.
[ 0.850000] RPC: Registered tcp transport module.
[ 0.850000] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.860000] NetWinder Floating Point Emulator V0.97 (double precision)
[ 0.950000] NFS: Registering the id_resolver key type
[ 0.960000] Key type id_resolver registered
[ 0.960000] Key type id_legacy registered
[ 0.970000] msgmni has been set to 103
[ 0.980000] Block layer SCSI generic (bsg) driver version 0.4 loaded (major )
[ 0.990000] io scheduler noop registered (default)
[ 1.000000] uart-pl011 80070000.serial: no DMA platform data
[ 1.000000] 8006c000.serial: ttyAPP0 at MMIO 0x8006c000 (irq = 122) is a 800l
[ 1.010000] mxs-auart 8006c000.serial: Found APPUART 3.0.0
[ 1.030000] rtw driver version=v3.4.4_xxxx.20120730
[ 1.030000] Build at: Nov 10 2012 20:41:11
[ 1.040000] usbcore: registered new interface driver rtl8192cu
[ 1.040000] usbcore: registered new interface driver cdc_ether
[ 1.050000] usbcore: registered new interface driver smsc95xx
[ 1.060000] Initializing USB Mass Storage driver...
[ 1.060000] usbcore: registered new interface driver usb-storage
[ 1.070000] USB Mass Storage support registered.
[ 1.080000] imx_usb 80080000.usb: pinctrl get/select failed, err=-19
[ 1.090000] ci_hdrc ci_hdrc.0: doesn't support gadget
[ 1.090000] ci_hdrc ci_hdrc.0: ChipIdea HDRC EHCI
[ 1.100000] ci_hdrc ci_hdrc.0: new USB bus registered, assigned bus number 1
[ 1.160000] ci_hdrc ci_hdrc.0: USB 2.0 started, EHCI 1.00
[ 1.170000] hub 1-0:1.0: USB hub found
[ 1.180000] hub 1-0:1.0: 1 port detected
[ 1.190000] mousedev: PS/2 mouse device common for all mice
[ 1.200000] stmp3xxx-rtc 8005c000.rtc: rtc core: registered 8005c000.rtc as 0
[ 1.210000] i2c /dev entries driver
[ 1.260000] mxs-mmc 80010000.ssp: initialized
[ 1.260000] leds-gpio leds.5: pins are not configured from the driver
[ 1.280000] usbcore: registered new interface driver usbhid
[ 1.290000] usbhid: USB HID core driver
[ 1.310000] TCP: cubic registered
[ 1.310000] NET: Registered protocol family 17
[ 1.320000] lib80211: common routines for IEEE802.11 drivers
[ 1.330000] Key type dns_resolver registered
[ 1.340000] registered taskstats version 1
[ 1.340000] mmc0: host does not support reading read-only switch. assuming w.
[ 1.350000] stmp3xxx-rtc 8005c000.rtc: setting system clock to 1970-01-01 00)
[ 1.390000] mmc0: new high speed SDHC card at address 1234
[ 1.400000] ALSA device list:
[ 1.400000] No soundcards found.
[ 1.410000] mmcblk0: mmc0:1234 SA08G 7.28 GiB
[ 1.440000] mmcblk0: p1 p2 p3
[ 1.470000] kjournald starting. Commit interval 5 seconds
[ 1.490000] EXT3-fs (mmcblk0p2): using internal journal
[ 1.490000] EXT3-fs (mmcblk0p2): recovery complete
[ 1.500000] EXT3-fs (mmcblk0p2): mounted filesystem with ordered data mode
[ 1.510000] usb 1-1: new high-speed USB device number 2 using ci_hdrc
[ 1.510000] VFS: Mounted root (ext3 filesystem) on device 179:2.
[ 1.520000] Freeing init memory: 140K
[ 1.670000] hub 1-1:1.0: USB hub found
[ 1.680000] hub 1-1:1.0: 3 ports detected
INIT: version 2.88 booting
[ 1.970000] usb 1-1.1: new high-speed USB device number 3 using ci_hdrc
[ 2.100000] smsc95xx v1.0.4
[ 2.240000] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-ci_hdrc.0-1.5
[ 2.350000] usb 1-1.2: new full-speed USB device number 4 using ci_hdrc
[ 2.590000] usb 1-1.3: new full-speed USB device number 5 using ci_hdrc
HOSTNAME= is deprecated. See rc.conf(5) and hostname(5) for details.
> Arch Linux ARM
> http://archlinuxarm.org/
------------------------------
:: Mounting root read-only [BUSY] [DONE]
:: Setting hostname: imx233 [BUSY] [DONE]
HARDWARECLOCK= is deprecated. See rc.conf(5) and hwclock(8) for details.
:: Adjusting system time and setting kernel time zone [BUSY] TIMEZONE= is d
[DONE]
:: Starting udev daemon [BUSY] [ 12.140000] systemd-udevd[78]: starting ve6
[DONE]
:: Triggering udev uevents [BUSY] [DONE]
:: Loading user-specified modules [BUSY] [DONE]
:: Waiting for udev uevents to be processed [BUSY] [DONE]
:: Configuring virtual consoles [BUSY] G [DONE]
:: Bringing up loopback interface [BUSY] [DONE]
:: Checking filesystems [BUSY] [DONE]
:: Remounting root and API filesystems [BUSY] [ 17.920000] EXT3-fs (mmcblkl
[DONE]
:: Mounting local filesystems [BUSY] [DONE]
:: Activating swap [BUSY] [DONE]
:: Configuring time zone [BUSY] [DONE]
:: Initializing random seed [BUSY] [DONE]
:: Removing leftover files [BUSY] [DONE]
:: Saving dmesg log [BUSY] [DONE]
Cannot find device "usb0"
INIT: Entering runlevel: 3
mount: mount point /proc/sys/fs/binfmt_misc does not exist
:: Starting Syslog-NG [BUSY] Error binding socket; addr='AF_UNIX(/run/system'
Error initializing source driver; source='src', id='src#0'
Error initializing message pipeline;
[FAIL]
:: Starting network [BUSY] Cannot find device "usb0"
[DONE]
:: Mounting network filesystems [BUSY] [DONE]
:: Starting crond daemon [BUSY] [DONE]
:: Starting Secure Shell Daemon [BUSY] [DONE]
Quote from: Fadil Berisha on December 21, 2012, 09:05:22 AM
Quote from: bsrdjan on December 20, 2012, 11:12:28 PM
Hi --,
could you please let me know how exactly to copy new kernel to boot partition?
I use the standard rootfs image from Archlinuxarm and have three partitions
Device Boot Start End Blocks Id System
/dev/mmcblk0p1 * 2048 67583 32768 53 OnTrack DM6 Aux3
/dev/mmcblk0p2 67584 3164159 1548288 83 Linux
/dev/mmcblk0p3 3164160 5261311 1048576 82 Linux swap / Solaris
Image sd_mmc_bootstream.raw found at https://www.dropbox.com/s/rfnmzdbcu21pfgf/sd_mmc_bootstream.raw is kernel 3.7-rc4 with wifi support. Included driver is rtl8188. It work with imx23-olinuxino-mini board. I tested also with imx23-olinuxino-maxi with rtl USB dongle connected on USB port. I do not have imx23-olinuxino-micro, but for sure will work on that board too.
Image contain bootlets+kernel+dts_file. This image should be installed on 1st partition of your SD card. Second partition contain any rootfs (Yocto, arch, debian etc). I am using Yocto with no X server. Booting process is possible to track with debug console. All board control is done with ssh. I am doing cross compile on my PC and transfer files via network.
To get kernel 3.7-rc4 with wifi support please follow those steps:
1. On your linux PC machine, download image https://www.dropbox.com/s/rfnmzdbcu21pfgf/sd_mmc_bootstream.raw.
2. Insert SD card on your linux PC machine and identify how is recognized SD card on your PC machine. Run command:
sudo fdisk -l
I am getting /dev/sda and /dev/sdb. Device sdb is my SD card.
3. Copy image on 1st partition /dev/sdb1:
sudo dd if=sd_mmc_bootstream.raw of=/dev/sdb1
4. Insert SD card on your olinuxino board.
5. Connect USB-serial cable on olinuxino board (see olinuxino manual - debug connector)
6. Connect USB-serial cable on your PC. Open console on PC and start your terminal program. I am using
minicom with following setting: E - Bps/Par/Bits : 115200 8N1
7. power ON olinuxino board.
After boot, check with iwconfig, wifi device should be wlan0 or wlan1.
Message to Olimex, bsrdjan, JaG, laurent, idragoev:
Can someone of you please confirm this procedure. Needed imx23-olinuxino-mini and USB-serial cable.
I am working on mini howto prepare sd_mmc_bootstream.raw file based on latest kernel 3.7. This kernel support USB, SPI, I2C and wifi.
If everything goes well, next step would be TV-out support.
Regards
Fadil Berisha
I confirm your procedure works perfectly ;)
After restart with 3.7 kernel, the console displayed repeatedly an error on an /home/example program about GPIO. I renamed the program so I don't remember its exact name.
I don't know if it's linked, but the LED usually turned ON when the board is powered is now OFF.
I tested the USB-Ethernet dongle from Olimex, without success (kernel don't have the driver ?)
I tested a USB WiFi dongle (chipset rt5370) which perfectly works on my Ubuntu PC and my Raspberry Pi, without success.
I switched back to 2.6 kernel. I saw that the Asix AX88772B has a kernel 2.6 driver, but unable to compile it...
Hi bsrdjan, laurent
Thank you for your follow up. It is good that you confirmed that this image booting system.
To bsrdjan
Quote
Should kernel 3 be used on iMX233-MAXI
If old kernel does not support new devices connected on board, answer is yes.
Quote
and how to get LAN working?
Your rootfs looks to connect on network via usb0 ethernet connection. You want connection via wlan0 or wlan1.
To configure wlan0 instead of usb0, you need to
connect rtl8188 dongle on USB port and edit your /etc/rc.conf file. For details, see Keans post « Reply #6 on: September 19, 2012, 03:04:19 PM »: https://www.olimex.com/forum/index.php?topic=13.0
To laurent,
Quote
I don't know if it's linked, but the LED usually turned ON when the board is powered is now OFF.
Probably I forgot to turn ON led support on kernel. Will fix on final version.
Quote
I tested the USB-Ethernet dongle from Olimex, without success (kernel don't have the driver ?)
What chip is used USB-Ethernet dongle from Olimex? Probably, is matter of just activating driver on kernel.
Quote
I tested a USB WiFi dongle (chipset rt5370) which perfectly works on my Ubuntu PC and my Raspberry Pi, without success.
We want to get image with rtl8188 because that chip is included on imx23-olinuxino-mini board. Based on that example you can incorporate rt5370 too. See also following post:Building driver for Ralink RT5370 USB WiFi WLAN Dongle at http://askubuntu.com/questions/99373/building-driver-for-ralink-rt5370-usb-wifi-wlan-dongle
Quote
I switched back to 2.6 kernel. I saw that the Asix AX88772B has a kernel 2.6 driver, but unable to compile it...
You may get solution from this post: https://www.olimex.com/forum/index.php?topic=27.0.
I am working on mini howto prepare sd_mmc_bootstream.raw file based on latest kernel 3.7 with USB, SPI, I2C and rtl8188 wifi support. Hope to get all done by weekend.
Fadil Berisha
Fadil,
thanks a lot for the great work!
QuoteI am working on mini howto prepare sd_mmc_bootstream.raw file based on latest kernel 3.7 with USB, SPI, I2C and rtl8188 wifi support. Hope to get all done by weekend.
Would it be possible to have 3.7 kernel which supports also LAN, so the same kernel could be used for LAN and for WLAN boards?
Regards,
srdjan
Quote from: bsrdjan on December 21, 2012, 08:55:46 PM
thanks a lot for the great work!
I am happy to help
Quote
Would it be possible to have 3.7 kernel which supports also LAN, so the same kernel could be used for LAN and for WLAN boards?
for sure
Fadil Berisha
Quote from: Fadil Berisha on December 21, 2012, 06:25:51 PM
Hi bsrdjan, laurent
Thank you for your follow up. It is good that you confirmed that this image booting system.
Thank you too for your help provided here ;)
Quote from: Fadil Berisha on December 21, 2012, 06:25:51 PM
Quote
I tested the USB-Ethernet dongle from Olimex, without success (kernel don't have the driver ?)
What chip is used USB-Ethernet dongle from Olimex? Probably, is matter of just activating driver on kernel.
According what is printed on the adapter, it may be a AX88772B chipset. It's recognized as a "ASIX AX88772 USB 2.0 Ethernet" when plugged on my Ubuntu PC.
Quote from: Fadil Berisha on December 21, 2012, 06:25:51 PM
Quote
I tested a USB WiFi dongle (chipset rt5370) which perfectly works on my Ubuntu PC and my Raspberry Pi, without success.
We want to get image with rtl8188 because that chip is included on imx23-olinuxino-mini board. Based on that example you can incorporate rt5370 too. See also following post:Building driver for Ralink RT5370 USB WiFi WLAN Dongle at http://askubuntu.com/questions/99373/building-driver-for-ralink-rt5370-usb-wifi-wlan-dongle
Thank you for the solution and link provided. Although I am a long time GNU/Linux user, I am not very familiar with embedded kernel (re)compilation.
I don't have yet the experience required to follow such guides, and unfortunately, I don't have the (long) time required to acquire this experience on my own, now (although I really would like).
Quote from: Fadil Berisha on December 21, 2012, 06:25:51 PM
Quote
I switched back to 2.6 kernel. I saw that the Asix AX88772B has a kernel 2.6 driver, but unable to compile it...
You may get solution from this post: https://www.olimex.com/forum/index.php?topic=27.0.
I am working on mini howto prepare sd_mmc_bootstream.raw file based on latest kernel 3.7 with USB, SPI, I2C and rtl8188 wifi support. Hope to get all done by weekend.
Fadil Berisha
I looked on this topic, but it seems that there is no solution for me there.
Thank you for your help.
Laurent
Hello Fadil,
Thank you for your work with the 3.7 kernel, it works great so far.
Any chance you can add UVC support to the next one?
Thanks
Rob
After following the steps to building my own Bootlets more than 10x, I finally got it working.
Next step: I'm working on the wifi adaptor right now. Any suggestions on how to get it up and running would be greatly appreciated.
Thanks,
Rob
Hi Rob,
Quote from: Cure on December 23, 2012, 11:49:48 PM
After following the steps to building my own Bootlets more than 10x, I finally got it working.
Next step: I'm working on the wifi adaptor right now. Any suggestions on how to get it up and running would be greatly appreciated.
Thanks,
Rob
Driver for rtl81988CU supplied with kernel - doesn't work (need firmware from manufacturer). Latest driver from manufacturer contain firmware but is for kernel 3.0. Inside source are detailed instructions how to incorporate in kernel and with some work you can get working with kernel up to 3.6-rc4.
Latest kernel has removed some old functions from source so to work with new kernel 3.7 and 3.8-rc1 needed to patch driver source with missing functions. I have prepared those patches and shortly will post on https://github.com/koliqi/imx23-olinuxino.
Fadil Berisha
Hello Fadil,
I tested your 3.7-rc4 and got the mini+wifi working on there, so you must be doing something right. I'll keep my eye out for the instructions.
Until then I just wanted to say thank you for all your hard work. It really is appreciated.
Rob
Quote
I am working on mini howto prepare sd_mmc_bootstream.raw file based on latest kernel 3.7 with USB, SPI, I2C and rtl8188 wifi support. Hope to get all done by weekend.
Hi Fadil,
is it likely to expect 3.7 version soon ?
Thank you,
srdjan
Kernel image 3.7.1-stable with USB, SPI, I2C, rtl8188 wifi and asix-ax88772b dongle is available for download from here: https://www.dropbox.com/s/rfnmzdbcu21pfgf/sd_mmc_bootstream.raw (https://www.dropbox.com/s/rfnmzdbcu21pfgf/sd_mmc_bootstream.raw). In this threat you can find instructions to copy image on your card.
If you are interested to build from scratch, instruction are at https://github.com/koliqi/imx23-olinuxino.
Fadil Berisha
amazing! I'm uploading it in the wiki
Quote from: Fadil Berisha on January 05, 2013, 06:31:47 AM
Kernel image 3.7.1-stable with USB, SPI, I2C, rtl8188 wifi and asix-ax88772b dongle is available for download from here: https://www.dropbox.com/s/rfnmzdbcu21pfgf/sd_mmc_bootstream.raw (https://www.dropbox.com/s/rfnmzdbcu21pfgf/sd_mmc_bootstream.raw). In this threat you can find instructions to copy image on your card.
If you are interested to build from scratch, instruction are at https://github.com/koliqi/imx23-olinuxino.
Fadil Berisha
Awesome !!!
Thanks a lot for your work.
I'm downloading and I'll test that very soon.
Tested just now, your image works perfectly with the USB-Ethernet key provided by Olimex ;)
Thanks a lot Fadil, great work ! :)
Some questions :
- What appended to /dev/watchdog ?
- Did the other serial port /dev/ttySP1 became /dev/ttyAPP0 ?
Another question :
Your post mentioned kernel version "3.7.1-stable", but the version of the image downloaded from your dropbox share say :
[root@alarm ~]# uname -r
3.7.0-00001-ga557dd2-dirty
kernel source is updated from git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git. Probably old tag is not updated. To get fresh copy please follow instructions at https://github.com/koliqi/imx23-olinuxino and you will get right tag. /dev/ttyAPP0 is UART on UEXT connector.
Fadil Berisha
Quote from: Fadil Berisha on January 05, 2013, 06:31:47 AM
If you are interested to build from scratch, instruction are at https://github.com/koliqi/imx23-olinuxino.
I've followed the steps to build my own kernel but I'm getting stuck here:
# make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- zImage modules
...
...
...
drivers/built-in.o: In function `thread_enter':
/home/user/imx23-olinuxino/kernel/linux-stable/drivers/net/wireless/rtl8192cu/include/osdep_service.h:581: undefined reference to `daemonize'
make: *** [vmlinux] Error 1
My understanding of Linux isn't that great, any ideas what the error means and how I can fix it?
Thanks,
Rob
Hello,
I've exactly the same problem :
Quote from: Cure on January 07, 2013, 09:12:06 AM
Quote from: Fadil Berisha on January 05, 2013, 06:31:47 AM
If you are interested to build from scratch, instruction are at https://github.com/koliqi/imx23-olinuxino.
I've followed the steps to build my own kernel but I'm getting stuck here:
# make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- zImage modules
...
...
...
drivers/built-in.o: In function `thread_enter':
/home/user/imx23-olinuxino/kernel/linux-stable/drivers/net/wireless/rtl8192cu/include/osdep_service.h:581: undefined reference to `daemonize'
make: *** [vmlinux] Error 1
My understanding of Linux isn't that great, any ideas what the error means and how I can fix it?
Thanks,
Rob
I may try to recompile without the driver for rtl8192... Note that i don't use module in the kernel as i exactly know what hardware i will use.
Olivier
It should work if you explicitly checkout the 3.7.1 kernel
[chris@thinkpad tools]$ cd kernel
[chris@thinkpad kernel]$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
Cloning into 'linux-stable'...
remote: Counting objects: 3000082, done.
remote: Compressing objects: 100% (469603/469603), done.
remote: Total 3000082 (delta 2521093), reused 2981126 (delta 2502295)
Receiving objects: 100% (3000082/3000082), 620.49 MiB | 624 KiB/s, done.
Resolving deltas: 100% (2521093/2521093), done.
Checking out files: 100% (41502/41502), done.
[chris@thinkpad kernel]$ cd linux-stable/
[chris@thinkpad linux-stable]$ gitk --all
[chris@thinkpad linux-stable]$
You can use git-cola which is a sleek and powerful git GUI to revert
any patch you've applied already or do it from the command line,
you don't have to download the kernel source again.
[chris@thinkpad linux-stable]$ git checkout v3.7.1
Note: checking out 'v3.7.1'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
git checkout -b new_branch_name
HEAD is now at cc86050... Linux 3.7.1
[chris@thinkpad linux-stable]$
I applied the wifi patch to an older 3.6-rc2 kernel and it compiled successfully. I didn't test it last night as it was getting late and I was falling asleep. I'll post a followup later today and let everyone know if it works under the older kernel and maybe that will help wtih some of the troubleshooting.
Christian, I believe we are using the latest kernel as your line matches the steps in the instructions:
git clone git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
Edit: didn't work under 3.6-rc2, I get the following message on bootup and no wifi adapter is found:
cat: /sys/class/net/usb0/address: No such file or directory
Quote from: Christian Jann on January 07, 2013, 09:42:00 PM
It should work if you explicitly checkout the 3.7.1 kernel
Thank you Christian for contribution.
Let me put light what is going on. When we do clone as:
git clone git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
HEAD is on latest kernel. At this moment rc2 for 3.8.
Starting with 3.8-rc1, in kernel sources is not present anymore function to define `daemonize' used by rtl8188cu driver. I have included that function on rtl8188cu driver but is disabled because 3.7.1 doesn't need it.
There are two solutions:
1. If you have already downloaded kernel sources and want to test 3.8-rc2 open file drivers/net/wireless/rtl8192cu/os_dep/osdep_service.c and enable daemonize function.
Look for code:
#endif /* DBG_MEMORY_LEAK */
#if 0
#include <linux/mm.h>
#include <linux/slab.h>
Find next #endif
EXPORT_SYMBOL(daemonize);
#endif
#if defined(PLATFORM_LINUX)
Save changes and follow rest of instructions. I didn't try 3.8-rc2, so please follow up.
2. Revert patches as per Christian's instructions, or if you are not familiar with git, you can get 3.7.1 sources as follow:wget http://www.kernel.org/pub/linux/kernel/v3.0/linux-3.7.1.tar.bz2
tar xvjf linux-3.7.1.tar.bz2
mv linux-3.7.1 linux-stable
After this point follow instructions at https://github.com/koliqi/imx23-olinuxino.
I think, at moment is good idea to work with 3.7.1. As soon as next stable release is out, I will enable changes on rtl8188cu driver.
Fadil Berisha
Edit: After posted, I did once again test and it is working. Here is my console output:
root@imx233-olinuxino-maxi:~# iwconfig
lo no wireless extensions.
wlan1 IEEE 802.11bg ESSID:"home" Nickname:"<WIFI@REALTEK>"
Mode:Managed Frequency:2.437 GHz Access Point: 00:26:5A:CF:57:34
Bit Rate:54 Mb/s Sensitivity:0/0
Retry:off RTS thr:off Fragment thr:off
Encryption key:746F-6269-35 Security mode:restricted
Power Management:off
Link Quality=68/100 Signal level=45/100 Noise level=0/100
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
Thanks for pointing this out, I was able to build the 3.8-rc2 kernel without rtl8188cu already but than creating the device tree blob .dtb file has failed (some error about spi2) and switched to v3.7.1.
Downloading the BZ2 file is really a good idea for people with a slow internet connection, git: 620.49 MiB bz2: 79.8 MB.
Hi --,
I was following option 2 (kernel 3.7.1) and completed all steps from https://github.com/koliqi/imx23-olinuxino but failed at the building boot stream
make CROSS_COMPILE=arm-linux-gnueabi-
Here is the error:
elftosb2 -d -z -c ./linux_prebuilt.db -o imx23_linux.sb
elftosb2: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory
make: *** [gen_bootstream] Error 127
~/olimex/imx23-olinuxino/boot/imx-bootlets-src-10.05.02
☹
The libstdc is missing from /usr/lib and I tried to install but got following error:
sudo apt-get install libstdc++
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'libstdc++-dev-armel-cross' for regex 'libstdc+'
Note, selecting 'libstdc++6-4.4-doc' for regex 'libstdc+'
Note, selecting 'libstdc++6-4.2-dbg-armel-cross' for regex 'libstdc+'
Note, selecting 'libstdc++5' for regex 'libstdc+'
Note, selecting 'libstdc++6' for regex 'libstdc+'
Note, selecting 'libstdc++6-armel-cross-armhf' for regex 'libstdc+'
Note, selecting 'libstdc++6-4.1-dbg' for regex 'libstdc+'
Note, selecting 'libstdc++-dev-armhf-cross' for regex 'libstdc+'
Note, selecting 'libstdc++6-4.1-doc' for regex 'libstdc+'
Note, selecting 'libstdc++6-4.2-dbg-armhf-cross' for regex 'libstdc+'
Note, selecting 'libstdc++2.9-dev' for regex 'libstdc+'
Note, selecting 'libstdc++6-4.4-pic' for regex 'libstdc+'
Note, selecting 'libstdc++6-4.6-armhf-cross-dbg-armel' for regex 'libstdc+'
Note, selecting 'libstdc++6-4.3-dbg-armel-cross' for regex 'libstdc+'
Note, selecting 'libstdc++6-dev-armel-dcv1' for regex 'libstdc+'
Note, selecting 'libstdc++6-4.3-dbg-armhf-cross' for regex 'libstdc+'
Note, selecting 'libstdc++-dev-armhf-dcv1' for regex 'libstdc+'
Note, selecting 'libstdc++6-4.5-dbg' for regex 'libstdc+'
Note, selecting 'libstdc++6-4.5-dev' for regex 'libstdc+'
Note, selecting 'libstdc++6-4.4-dbg-armel-cross' for regex 'libstdc+'
Note, selecting 'libstdc++6-4.5-doc' for regex 'libstdc+'
Note, selecting 'libstdc++-dev' for regex 'libstdc+'
Note, selecting 'libstdc++2.10-dev' for regex 'libstdc+'
Note, selecting 'libstdc++2.9-glibc2.1-dev' for regex 'libstdc+'
Note, selecting 'libstdc++6-dbg-armel-dcv1' for regex 'libstdc+'
Note, selecting 'libstdc++6-4.2-dbg' for regex 'libstdc+'
Note, selecting 'libstdc++6-4.4-dbg-armhf-cross' for regex 'libstdc+'
Note, selecting 'libstdc++6-4.2-doc' for regex 'libstdc+'
Note, selecting 'libstdc++6-armhf-dcv1' for regex 'libstdc+'
Note, selecting 'libstdc++6-pic-armel-dcv1' for regex 'libstdc+'
Note, selecting 'libstdc++6-4.5-pic' for regex 'libstdc+'
Note, selecting 'libstdc++6-4.5-dbg-armel-cross' for regex 'libstdc+'
Note, selecting 'libstdc++6-4.4-dev-armel-cross' for regex 'libstdc+'
Note, selecting 'libstdc++6-4.4-pic-armel-cross' for regex 'libstdc+'
Note, selecting 'libstdc++6-4.5-dbg-armhf-cross' for regex 'libstdc+'
Note, selecting 'libstdc++5-3.3-dbg-armel-cross' for regex 'libstdc+'
Note, selecting 'libstdc++6-4.4-dev-armhf-cross' for regex 'libstdc+'
Note, selecting 'libstdc++6-4.6-dbg-armel-cross' for regex 'libstdc+'
Note, selecting 'libstdc++6-4.6-dbg' for regex 'libstdc+'
Note, selecting 'libstdc++6-4.6-dev' for regex 'libstdc+'
Note, selecting 'libstdc++6-4.6-doc' for regex 'libstdc+'
Note, selecting 'libstdc++6-4.5-dev-armel-cross' for regex 'libstdc+'
Note, selecting 'libstdc++6-4.4-pic-armhf-cross' for regex 'libstdc+'
Note, selecting 'libstdc++6-dev-armhf-dcv1' for regex 'libstdc+'
Note, selecting 'libstdc++5-3.3-dbg-armhf-cross' for regex 'libstdc+'
Note, selecting 'libstdc++5-dbg' for regex 'libstdc+'
Note, selecting 'libstdc++5-doc' for regex 'libstdc+'
Note, selecting 'libstdc++6-4.5-pic-armel-cross' for regex 'libstdc+'
Note, selecting 'libstdc++6-4.6-dbg-armhf-cross' for regex 'libstdc+'
Note, selecting 'libstdc++6-4.3-dbg' for regex 'libstdc+'
Note, selecting 'libstdc++6-armel-cross' for regex 'libstdc+'
Note, selecting 'libstdc++6-4.3-dev' for regex 'libstdc+'
Note, selecting 'libstdc++6-4.5-dev-armhf-cross' for regex 'libstdc+'
Note, selecting 'libstdc++6-4.3-doc' for regex 'libstdc+'
Note, selecting 'libstdc++6-4.6-pic' for regex 'libstdc+'
Note, selecting 'libstdc++5-dbg-armel-cross' for regex 'libstdc+'
Note, selecting 'libstdc++6-4.0-dbg-armel-cross' for regex 'libstdc+'
Note, selecting 'libstdc++6-4.6-dev-armel-cross' for regex 'libstdc+'
Note, selecting 'libstdc++6-4.5-pic-armhf-cross' for regex 'libstdc+'
Note, selecting 'libstdc++6-armhf-cross' for regex 'libstdc+'
Note, selecting 'libstdc++6-4.0-dbg' for regex 'libstdc+'
Note, selecting 'libstdc++6-dbg-armhf-dcv1' for regex 'libstdc+'
Note, selecting 'libstdc++6-armhf-cross-armel' for regex 'libstdc+'
Note, selecting 'libstdc++6-4.6-pic-armel-cross' for regex 'libstdc+'
Note, selecting 'libstdc++6-4.0-doc' for regex 'libstdc+'
Note, selecting 'libstdc++2.8-dev' for regex 'libstdc+'
Note, selecting 'libstdc++6-pic-armhf-dcv1' for regex 'libstdc+'
Note, selecting 'libstdc++5-dbg-armhf-cross' for regex 'libstdc+'
Note, selecting 'libstdc++6-4.0-dbg-armhf-cross' for regex 'libstdc+'
Note, selecting 'libstdc++6-4.6-dev-armhf-cross' for regex 'libstdc+'
Note, selecting 'libstdc++-dev-armel-dcv1' for regex 'libstdc+'
Note, selecting 'libstdc++5-3.3-dbg' for regex 'libstdc+'
Note, selecting 'libstdc++6-dbg-armel-cross' for regex 'libstdc+'
Note, selecting 'libstdc++6-4.1-dbg-armel-cross' for regex 'libstdc+'
Note, selecting 'libstdc++5-3.3-doc' for regex 'libstdc+'
Note, selecting 'libstdc++6-4.6-pic-armhf-cross' for regex 'libstdc+'
Note, selecting 'libstdc++3.0-dev' for regex 'libstdc+'
Note, selecting 'libstdc++6-4.6-armel-cross-dbg-armhf' for regex 'libstdc+'
Note, selecting 'libstdc++6-dbg' for regex 'libstdc+'
Note, selecting 'libstdc++6-doc' for regex 'libstdc+'
Note, selecting 'libstdc++6-dbg-armhf-cross' for regex 'libstdc+'
Note, selecting 'libstdc++6-4.1-dbg-armhf-cross' for regex 'libstdc+'
Note, selecting 'libstdc++6-4.4-dbg' for regex 'libstdc+'
Note, selecting 'libstdc++6-4.4-dev' for regex 'libstdc+'
Note, selecting 'libstdc++6-armel-dcv1' for regex 'libstdc+'
Note, selecting 'libstdc++6-armel-cross' instead of 'libstdc++6-armel-dcv1'
Note, selecting 'libstdc++6-armhf-cross' instead of 'libstdc++6-armhf-dcv1'
libstdc++6 is already the newest version.
libstdc++6-4.6-dev is already the newest version.
libstdc++6-4.6-dev set to manually installed.
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
libstdc++6-4.5-dbg : Conflicts: libstdc++6-4.4-dbg but 4.4.7-1ubuntu2 is to be installed
libstdc++6-4.5-dbg-armel-cross : Conflicts: libstdc++6-4.4-dbg-armel-cross but 4.4.7-1ubuntu2cross1.52 is to be installed
libstdc++6-4.5-dbg-armhf-cross : Conflicts: libstdc++6-4.4-dbg-armhf-cross but 4.4.7-1ubuntu2cross1.52 is to be installed
libstdc++6-4.5-doc : Conflicts: libstdc++6-4.4-doc but 4.4.7-1ubuntu2 is to be installed
libstdc++6-4.6-dbg : Conflicts: libstdc++6-4.4-dbg but 4.4.7-1ubuntu2 is to be installed
Conflicts: libstdc++6-4.5-dbg but 4.5.3-12ubuntu2 is to be installed
libstdc++6-4.6-dbg-armel-cross : Conflicts: libstdc++6-4.4-dbg-armel-cross but 4.4.7-1ubuntu2cross1.52 is to be installed
Conflicts: libstdc++6-4.5-dbg-armel-cross but 4.5.3-12ubuntu2cross1.61 is to be installed
libstdc++6-4.6-dbg-armhf-cross : Conflicts: libstdc++6-4.4-dbg-armhf-cross but 4.4.7-1ubuntu2cross1.52 is to be installed
Conflicts: libstdc++6-4.5-dbg-armhf-cross but 4.5.3-12ubuntu2cross1.61 is to be installed
libstdc++6-4.6-doc : Conflicts: libstdc++6-4.4-doc but 4.4.7-1ubuntu2 is to be installed
Conflicts: libstdc++6-4.5-doc but 4.5.3-12ubuntu2 is to be installed
E: Unable to correct problems, you have held broken packages.
What could be wrong?
I am running Ubuntu 64 bit.
elftosb2 is built for the i386 architecture, you need to have the 32bit version of libstdc++ installed.
http://ubuntuforums.org/showthread.php?t=1604953
Try installing the "g++-multilib" package. It contains non-native library versions for many standard libraries.
Quote from: Christian Jann on January 08, 2013, 04:34:18 PM
elftosb2 is built for the i386 architecture, you need to have the 32bit version of libstdc++ installed.
http://ubuntuforums.org/showthread.php?t=1604953
Try installing the "g++-multilib" package. It contains non-native library versions for many standard libraries.
Thanks, this worked and I created boot stream image but it fails to boot exactly as described here:
QuoteUndefined Instruction
r14_unHTLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLFC
Probably your toolchain does not support cpu arm926ej-s. Download sources and
compile --with-arch=armv5te --with-tune=arm926ej-s. If you prefer premade binaries,
download arm-none-eabi toolchain. It is proven to work with arm926ej-s.
I have two questions
1. How to prepare and partition the SD card, in general, before copying boot stream image?
2. Could you please share more detailed explanation how to "download sources and compile --with-arch=armv5te --with-tune=arm926ej-s" ?
Many thanks in advance,
srdjan
I've tried this 10 times now, and I'm not joking. It just doesn't want to boot without errors!
Fadil can you please make a 3.7.1 raw file with WIFI + UVC support? That's all I need, then I can stop compiling day and night and start working on my project, PLEASE PLEASE PLEASE.
Device Drivers > Multimedia support:
(*) cameras/video grabbers support
(*) media usb adaptors
(*) usb video class
(*) uvc input events device support
Thank you,
Rob
Quote from: bsrdjan on January 08, 2013, 07:55:19 PM
I have two questions
1. How to prepare and partition the SD card, in general, before copying boot stream image?
Like I've written in my blog just copy a current ARCH Linux image to the SD card:
[chris@thinkpad Downloads]$ sudo dd if=imx233_kernel_2.6_ARCH_FS_WIFI.img of=/dev/mmcblk0
I've used the one from here: https://olimex.wordpress.com/2012/12/05/imx233-olinuxino-arch-linux-image-with-rtl8188-wifi-support/, https://docs.google.com/open?id=0B-bAEPML8fwlYUUxaUtsNkZrRk0
Another image is available under http://archlinuxarm.org/platforms/armv5/olinuxino.
But you can use nearly every image made for the OLinuXino, even a Debian image would be possible. The above image is a complete SD card image with 3 partitions, that means you don't have to partition your SD card manually, just dd the image to the card. If you are using only a rootfs (root filesystem) you will have to create at least 2 partitions, one for the kernel /dev/mmcblk0p1 and one for the rootfs /dev/mmcblk0p2 and maybe a third as swap.
Quote from: bsrdjan on January 08, 2013, 07:55:19 PM
2. Could you please share more detailed explanation how to "download sources and compile --with-arch=armv5te --with-tune=arm926ej-s" ?
--with-arch=armv5te --with-tune=arm926ej-s is probably defined in some Makefile, it is enought to run make but your compiler has to support the armv5te architecture.
I'm using the cross compiler from Launchpad:
https://launchpad.net/gcc-arm-embedded/+download
https://launchpad.net/gcc-arm-embedded/4.6/4.6-2012-q4-update/+download/gcc-arm-none-eabi-4_6-2012q4-20121016.tar.bz2
Extract the tarball somewhere and add the compiler to the $PATH, e.g. edit your ~/.bashrc file an add a line like this:
export PATH=$PATH:/home/chris/tools/gcc-arm-none-eabi-4_6-2012q4/binYou may need to install some 32bit librarys when running a 64bit Linux, just run arm-none-eabi-gcc --version and see what is mssing.
[chris@thinkpad linux-stable]$ git checkout v3.7.1
Note: checking out 'v3.7.1'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
git checkout -b new_branch_name
HEAD is now at cc86050... Linux 3.7.1
[chris@thinkpad linux-stable]$
I've applied the git checkout and I'm 100% sure I'm in 3.7.1. When I get to the final step of running:
make ARCH=arm CROSS_COMPILE=arm-none-eabi- clean
make ARCH=arm CROSS_COMPILE=arm-none-eabi-
here are the errors I get, any ideas?
root@user-VirtualBox:/home/user/imx371/imx23-olinuxino/boot/imx-bootlets-src-10.05.02# make ARCH=arm CROSS_COMPILE=arm-none-eabi- clean
rm -rf *.sb
rm -f sd_mmc_bootstream.raw
rm -f linux_prep/board/*.o
rm -f power_prep/*.o
make -C linux_prep clean ARCH=arm
make[1]: Entering directory `/home/user/imx371/imx23-olinuxino/boot/imx-bootlets-src-10.05.02/linux_prep'
Cleaning...
Files:
rm -rf ./core/entry.o ./core/resume.o ./core/cmdlines.o ./core/setup.o ./core/keys.o ./board/stmp378x_dev.o ./hw/lradc-buttons.o ./output-target/linux_prep.ld
Build output:
rm -rf ./output-target
Build system:
rm -rf ./include/arch
make[1]: Leaving directory `/home/user/imx371/imx23-olinuxino/boot/imx-bootlets-src-10.05.02/linux_prep'
make -C boot_prep clean ARCH=arm
make[1]: Entering directory `/home/user/imx371/imx23-olinuxino/boot/imx-bootlets-src-10.05.02/boot_prep'
Cleaning...
Files:
Build output:
rm -rf *.o
rm -f boot_prep
make[1]: Leaving directory `/home/user/imx371/imx23-olinuxino/boot/imx-bootlets-src-10.05.02/boot_prep'
make -C power_prep clean ARCH=arm
make[1]: Entering directory `/home/user/imx371/imx23-olinuxino/boot/imx-bootlets-src-10.05.02/power_prep'
Cleaning...
rm -f power_prep.map
rm -f power_prep
make clean -C ./../mach-arm/hw
make: Entering an unknown directory
make: *** ./../mach-arm/hw: No such file or directory. Stop.
make: Leaving an unknown directory
make[1]: *** [clean] Error 2
make[1]: Leaving directory `/home/user/imx371/imx23-olinuxino/boot/imx-bootlets-src-10.05.02/power_prep'
make: *** [clean] Error 2
root@user-VirtualBox:/home/user/imx371/imx23-olinuxino/boot/imx-bootlets-src-10.05.02# make ARCH=arm CROSS_COMPILE=arm-none-eabi-
by using the pre-build command line
# force building linux_prep
make clean -C linux_prep
make[1]: Entering directory `/home/user/imx371/imx23-olinuxino/boot/imx-bootlets-src-10.05.02/linux_prep'
Cleaning...
Files:
rm -rf ./core/entry.o ./core/resume.o ./core/cmdlines.o ./core/setup.o ./core/keys.o ./board/stmp378x_dev.o ./hw/lradc-buttons.o ./output-target/linux_prep.ld
Build output:
rm -rf ./output-target
Build system:
rm -rf ./include/arch
make[1]: Leaving directory `/home/user/imx371/imx23-olinuxino/boot/imx-bootlets-src-10.05.02/linux_prep'
cross-compiling linux_prep
make -C linux_prep ARCH=arm BOARD=imx23_olinuxino_dev
make[1]: Entering directory `/home/user/imx371/imx23-olinuxino/boot/imx-bootlets-src-10.05.02/linux_prep'
arm-none-eabi-gcc -c -Wall -I./include -nostdinc -fno-builtin -O -DIMX23_OLINUXINO -DBOARD_IMX23_OLINUXINO_DEV -D__ASSEMBLY__ -o core/entry.o core/entry.S
core/entry.S:22:27: fatal error: arch/platform.h: No such file or directory
compilation terminated.
make[1]: *** [core/entry.o] Error 1
make[1]: Leaving directory `/home/user/imx371/imx23-olinuxino/boot/imx-bootlets-src-10.05.02/linux_prep'
make: *** [linux_prep] Error 2
Quote from: Cure on January 10, 2013, 07:38:43 AM
root@user-VirtualBox:/home/user/imx371/imx23-olinuxino/boot/imx-bootlets-src-10.05.02# make ARCH=arm CROSS_COMPILE=arm-none-eabi-
Try
$: make CROSS_COMPILE=arm-none-eabi- clean
$: make CROSS_COMPILE=arm-none-eabi-
Fadil Berisha
Quote from: Fadil Berisha on January 10, 2013, 08:43:59 AM
Quote from: Cure on January 10, 2013, 07:38:43 AM
root@user-VirtualBox:/home/user/imx371/imx23-olinuxino/boot/imx-bootlets-src-10.05.02# make ARCH=arm CROSS_COMPILE=arm-none-eabi-
Try
$: make CROSS_COMPILE=arm-none-eabi- clean
$: make CROSS_COMPILE=arm-none-eabi-
Fadil Berisha
I swear I checked my notes 5 times! I guess it was a typo all along, I'm finally up and running so thank you for the help.
Rob
Greetings.
This is a great little board, and I have had success with the pre-made kernels. The applications needs UVC, wifi and a USB to Serial converter so I am trying to build my own 3.x.x.
This guide was used: https://github.com/koliqi/imx23-olinuxino, but it seems no matter what I do, I just get to:
HTLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLFC
PowerPrep start initialize power...
Battery Voltage = 0.84V
No battery or bad battery detected!!!.Disabling battery voltage measurements./r/nLLCJan 10 201300:00:49
EMI_CTRL 0x1C084040
FRAC 0x92926192
init_ddr_mt46v32m16_133Mhz
power 0x00820710
Frac 0x92926192
start change cpu freq
hbus 0x00000003
cpu 0x00010001
LLLLLLLFCLJUncompressing Linux... done, booting the kernel.
And the that's as far as it gets.
I tried the arm-linux-gnueabi- and arm-none-eabi- compilers, and I am fairly sure the kernel command line is correct and points to the right serial power.
All of the patches apply correctly, and I am loading the SD card correctly.
I would greatly appreciate any suggestions.
Hi nulluser,
Quote from: nulluser on January 11, 2013, 12:02:38 AM
LLLLLLLFCLJUncompressing Linux... done, booting the kernel.
This message show's that kernel start boot and before get at point to activate debug console - kernel crash. That is reason why you don't see any message on debug console. It is possible to enable earlyprintk in kernel to see some info on screen. earlyprintk is used in unknown/new systems during test phase.
That is one way to go but for sure you will spend less time if once again repeat procedure at https://github.com/koliqi/imx23-olinuxino. Please don't do any shortcut, 1st time follow instructions step by step and latter you can do experiment of your choice.
Fadil Berisha
I did end up getting it working. A stupid mistake, I was appending the uncompiled dtb to the kernel.
Here is my build script:
#!/bin/bash
make ARCH=arm CROSS_COMPILE=arm-none-eabi- distclean
make ARCH=arm CROSS_COMPILE=arm-none-eabi- clean
read -p "Pause..."
cp config.last .config
make ARCH=arm CROSS_COMPILE=arm-none-eabi- menuconfig
cp .config config.last
read -p "Pause..."
make ARCH=arm CROSS_COMPILE=arm-none-eabi- zImage
read -p "Pause..."
make ARCH=arm CROSS_COMPILE=arm-none-eabi- INSTALL_MOD_PATH=output modules
read -p "Pause..."
make ARCH=arm CROSS_COMPILE=arm-none-eabi- INSTALL_MOD_PATH=output modules_install
read -p "Pause..."
make ARCH=arm CROSS_COMPILE=arm-none-eabi- imx23-olinuxino.dtb
read -p "Pause..."
rm arch/arm/boot/zImage_dtb
cat arch/arm/boot/zImage arch/arm/boot/imx23-olinuxino.dtb > arch/arm/boot/zImage_dtb
Here is my script to prep the card:
#!/bin/bash
sd_device="/dev/$11"
cd ../../boot/imx-bootlets-src-10.05.02
make CROSS_COMPILE=arm-none-eabi- clean
make CROSS_COMPILE=arm-none-eabi-
echo "Writing to " $sd_device
dd if=sd_mmc_bootstream.raw of=$sd_device
cd ../../kernel/linux-stable/
They are crude, but they do the job for me.
Now I have a solid 3.7.1 with a debian rootfs.
Thanks.
Happy to help
Fadil Berisha
Hi,
Kernel 3.7.1 doesn't seem to enable watchdog. How can I enable it or its support is currently missing in 3.7 kernel?
Regards,
Carmine noviello