Jump to content

Search the Community

Showing results for tags 'lime2'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Armbian
    • Armbian project administration
  • Community
    • Announcements
    • SBC News
    • Framework and userspace feature requests
    • Off-topic
  • Using Armbian
    • Beginners
    • Software, Applications, Userspace
    • Advanced users - Development
  • Standard support
    • Amlogic meson
    • Allwinner sunxi
    • Rockchip
    • Other families
  • Community maintained / Staging
    • TV boxes
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Support

Categories

  • Official giveaways
  • Community giveaways

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Matrix


Mastodon


IRC


Website URL


XMPP/Jabber


Skype


Github


Discord


Location


Interests

  1. After creating my own initramfs using this command from a chroot-ed environment sudo update-initramfs -t -u -k `uname -r` And rebooting, I get the following error: Found U-Boot script /boot/boot.scr 3708 bytes read in 126 ms (28.3 KiB/s) ## Executing script at 43100000 U-boot loaded from eMMC or secondary SD Boot script loaded from mmc 202 bytes read in 80 ms (2 KiB/s) 5731772 bytes read in 668 ms (8.2 MiB/s) 6790944 bytes read in 759 ms (8.5 MiB/s) Found legacy kernel configuration ** File not found /boot/script.bin ** ## Loading init Ramdisk from Legacy Image at 43300000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 5731708 Bytes = 5.5 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK EHCI failed to shut down host controller. Loading Ramdisk to 49a88000, end 49fff57c ... OK Starting kernel ... Uncompressing Linux... done, booting the kernel. Error: unrecognized/unsupported machine ID (r1 = 0x42000820). Available machine support: ID (hex) NAME ffffffff Generic DT based system ffffffff Allwinner sun9i Family ffffffff Allwinner sun8i Family ffffffff Allwinner sun7i (A20) Family ffffffff Allwinner sun6i (A31) Family ffffffff Allwinner sun4i/sun5i Families Please check your kernel config and/or bootloader. I chroot from a SD card with Armbian 5.35.installed to a eMMC with armbian 5.35 installed, with an encrypted LUKS partition (and a boot ext4 partition containing my boot files, including the initramfs). I am missing something but could not find it. What is the right way to update initrd ?
  2. Hi, is it possible to have the serial/UART on the Olimex LIME2 to work as a serial console on Armbian Jessie (kernel version 4.5.2)? The UART is already working during early boot, but once kernel is loaded it becomes inactive. /boot/boot.cmd contains: setenv bootargs "console=tty1 root=/dev/sda1 rootwait rootfstype=ext4 sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_no_mali_mem_reserve sunxi_fb_mem_reserve=16 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 panic=10 consoleblank=0 enforcing=0 loglevel=1" Thanks
  3. We want to merge eMMC/non eMMC images and in theory, it should work. eMMC version works on my Lime2 but just to make sure I need some feedback from Micro with and without eMMC, especially most recent ones. Lime2 with or without eMMC https://dl.armbian.com/lime2/Debian_stretch_next_nightly.7z Micro with or without eMMC https://dl.armbian.com/micro/Debian_stretch_next_nightly.7z Thank you.
  4. Hello there, I am looking for some feedback/suggestion about an issue I have. Installed Armbian legacy kernel just yesterday. Then I have plugged https://www.olimex.com/Products/USB-Modules/MOD-WIFI-AR9271-ANT/ to enable wifi and found out I missed required firmware. I installed such firmware (htc_9271.fw) first by Ubuntu linux-firmware package, then tried with armbian-firmware-full, then I have downloaded from here http://linuxwireless.org/download/htc_fw/1.3/ (putting in /lib/firmware and after failing tried also /lib/firmware/ath9k_htc like package manager does. I have also tried compiling my own version from here https://github.com/qca/open-ath9k-htc-firmware In all of these cases, looks like firmware is not detected and loaded and therefore wif interface is not created. Errors I get in dmesg are of the kind: [ 371.442863] usb 2-1: ath9k_htc: Firmware htc_9271.fw requested [ 371.460441] usb 2-1: ath9k_htc: Failed to get firmware htc_9271.fw [ 371.473538] usb 2-1: ath9k_htc: USB layer deinitialized Can anybody confirm this issue? Packages from Ubuntu and Armbian repos put firmware in /lib/firmware/ath9k_htc, but I have also tried /lib/firmware. Are those the right places to go? Many thanks for any feedback on this Antonio
  5. Hi all, first of all, I'm new to this forum even if I've been using Armbian on my Olimex Lime2 since lot of time and I find it a great project; thanks and keep up the good work! Now: I would like to use the Lime2 SPI #2 on pins "b" in master mode to communicate with a single slave device. What I did was: 1) downloaded Armbian v5.31 (latest available release at the time I write) 2) following the guide at https://docs.armbian.com/User-Guide_Allwinner_overlays/ I modified /boot/armbianEnv.txt to contain: verbosity=1 logo=disabled console=both disp_mode=1920x1080p60 overlay_prefix=sun7i-a20 rootdev=UUID=8cf9ed72-8225-4db8-a3a2-a242d648d644 rootfstype=ext4 overlays=spi-spidev param_spidev_spi_bus=2 param_spi2_bus_pins=b and rebooted. 3) at reboot I found that a device /dev/spidev32766.0 does actually exist now (good!); it was not there before. PROBLEM: I tried to use different example code found online to use that SPI device but the oscilloscope reveals that the clock line (pin PB15 when using SPI2 on pins b ) never show any activity (always low) as all other lines (CS0 and MOSI). So I guess I must be doing something wrong... any ideas or suggestions? Is there some message or log where I can check that what I activated is indeed the SPI #2 and not another SPI ? Or maybe the "bus_pins" setting is not working properly and the SPI is activated on pins "a" ? Btw to send data on the SPI I tried - the Python library provided by Olimex, https://pypi.python.org/pypi/pyA20Lime - spidev_test utility, http://elixir.free-electrons.com/linux/v4.0/source/Documentation/spi/spidev_test.c I tried sending data in an infinite loop and inspected the pins with an oscilloscope... but as I said: nothing, all lines seem to be always low (0V) Thanks! Francesco
  6. I'm using an Olimex LIME2 board with an A20 processor (actually it's a Olimex A20-SOM, but that shouldn't matter) and trying to use PWM. I have an older image (jessie with Kernel 3.4) where the PWM hardware can be accessed through /sys/class/pwm-sunxi/pwm*/{duty, duty_percent, period, pin, polarity, pulse, run}. Now I'm building a newer image (xenial with Vanilla kernel). It has /sys/class/pwm, but the directory is empty. Any ideas? The fex file is the same for both boards; the relevant section is: [pwm0_para] pwm_used = 1 pwm_period = 10000 pwm_duty_percent = 50 [pwm1_para] pwm_used = 1 pwm_period = 10000 pwm_duty_percent = 50
  7. Hello, I'm using the last Kernel (4.13.3) and U-boot (2017-09). I noticed that the device does not reboot each time we ask for it. It sometime get stuck and I have to start it manually, this is really annoying for my needs. I figure it out that the Device Tree from 4.13.3 introduce some improvement on AXP209 and power management. I tried Device Tree file from 4.11.x and everything seems fine. Does any body noticed it ? Thanks
  8. Hey all, I'm using U-boot 2017-09 and Kernel 4.13. I'm looking for a way to disable the board auto start. I'm explaining. When you plug the power in, the board start by itself and U-boot does the rest. I would like to disable this feature in order to be able to plug in the power, charge the battery if needed and start the board with the regular push button. Is there any tweak to be done in the Device Tree ? Thanks Florian
  9. When I do a reboot the Olimex Lime2-emmc shuts down. No more information is shown on the display. This happens with the latest Armbian_5.31_Lime2_Debian_jessie_next_4.11.5 image from the website. It also happens with a self-build image with u-boot v2017.07 and v2017.05 Any ideas? Or debugging directions? I am out of options after 2 days...
  10. Hello, I've downgrade Olimex Lime2 armbian from 5.31 to 5.25 with following commands: sudo dpkg -i linux-u-boot-next-lime2_5.25_armhf.deb sudo dpkg -i linux-dtb-next-sunxi_5.25_armhf.deb sudo dpkg -i linux-image-next-sunxi_5.25_armhf.deb and then reboot -f Unfortunately Olimex lime2 cannot re-start !! How can I recover my board ? Thank you
  11. Hi, yesterday I used the latest mainline built (https://dl.armbian.com/lime2/Debian_jessie_next.7z) on Olimex Lime2-emmc 4 GB but i can not access the eMMC. I only tested once with the latest mainline built. I have read other old topics about patching uboot but I wonder if I really need to patch uboot or if this a problem (bug?) with the latest built. Is there any .deb file available with the patched uboot? Thank you
  12. The board does not start with Debian Jessy. Blank screen.
  13. I have two Olimex Lime 2 eMMC boards, both set up the same way – same HDDs, same batteries, same power supplies, etc. Both run: - Armbian 5.31 (although one was updated to it, and the other was freshly installed with that version) - Debian 9 “stretch“ (same issue when they were both on Debian 8 “wheezy” though) - Linux kernel 4.8.14-sunxi Yet, one shows the CPU temperature, and the other doesn’t. A (the fresh-installed one): cat /sys/class/thermal/thermal_zone0/temp 41800 B (the one updated to 5.31 from a previous 5.x version): cat /sys/class/thermal/thermal_zone0/temp cat: /sys/class/thermal/thermal_zone0/temp: Invalid argument Any idea how that came to be and how to fix it? My plan is to use the GPIO pins to regulate the power of an 5V fan to provide cooling only when needed. If there is interest, I’m happy to share a HowTo, if I succeed
  14. After figuring out how to enable analog audio on the Lime2 (https://forum.armbian.com/index.php?/topic/4224-analog-audio-on-lime2-with-stable-kernel-version-49/), I now have the problem that there is a clearly noticeable mainline hum whenever no sound is playing. The hum goes away as soon as any sound is playing on the device, and it returns a couple seconds after the sound stopped. It appears like some kind of power saving feature kicks in. With the legacy kernel the hum goes away during boot and does not return. Any ideas?
  15. While analog audio output (through the GPIO connector) works out of the box using the legacy kernel 3.4.113-sun7i, I could not get it to work with the stable kernel 4.9.12-sunxi. Since the driver is not activated in the stable kernel, I added the following to the dts: &codec { status = "okay"; }; This lead to the following `dmesg` output: sun4i-codec 1c22c00.codec: Codec <-> 1c22c00.codec mapping ok `aplay -l` gives: **** List of PLAYBACK Hardware Devices **** card 0: sun4icodec [sun4i-codec], device 0: CDC PCM Codec-0 [] Subdevices: 1/1 Subdevice #0: subdevice #0 However when I play back some audio file, no sound is generated. Also using the legacy kernel, there is a particular point during boot time, when the power line hum goes away. In the stable kernel this does not happen; the hum stays. Does anybody know to fix this?
  16. Hi to All, I am proud to announce that our effort to embed Olimex' Lime2-eMMC board in Application Controller for Ground Penetrating Radar (GPR) systems meets with success to the final phase. Our product EGPR (Easy Ground Penetrating Radar) is ready for demo and field tests. Everybody can take a look on our just finished web site. There is link to the real application from Demo page. We would like to express our gratitude to Armbian project, its whole team and everybody here in for the great effort and help. Best regards EGPR team
  17. Hi all, I am running a lime2 board with trusty as a server. Now I wanted to upgrade to xenial and used the standard Ubuntu way using "do-release-upgrade". Since that failed and resulted in a not booting image I was now wondering if this is the right approach for armbian as well. I was searching the docs but couldn't find what I was looking for. Thanks Chris
  18. Hi to All, I found this project extremely useful and start customization process in the following directions: customize packet set for deploying into A20-Olinuxino-Lime2-4GB based server box use read only Root FS on NAND and SD with overlayfs and USB automount capability fully configurable by scripts in userpatches and up-gradable by web interface only completely none interactive (no tty1, ttyS0, ssh etc.) and controllable via web interface only Armbian project usage is a must in later maintenance so the customization has to be done by userpatches only. Final project has to be ready for automated builds. On the first step while trying to remove changing root password and adding user account at the first login a problem was reached adding to customize-image.sh following staff in Jessie case: chage -m 0 -M 99999 -I -1 -E -1 root # disable root password change at next login rm -f $HOME/.not_logged_in_yet # disable execution of the staff in check_first_login.sh Both actions cannot not be disabled while previous lines for configuring network in hostapd mode works fine. To overcome the problem distributions.sh was changed by commenting corresponding lines which is not acceptable. The other problem reached was at hostname change by adding in lib.config of: HOST=newhostname The new name is applied at first boot but it is changed again to board name by firstrun script. How to disable / change above staff without modifying Armbian code base? One more problem was reached at trying to mount final raw SD card image on a loop device. It is failed probably because of shrinking so the inspecting of written staff become harder by using SD mounted on other Linux system. Is it possible to leave final image before shrinking for verification and testing purposes without modifying Armbian code base? Best regards Chris
  19. Hi! I look for this topic in every place at the internet but all of the topics are not related with my problem. I have a custom board based on the Lime2-emmc. It can boot from SD, but when I tried to copy the same u-boot-sunxi-with-spl.bin to the emmc and try to boot, nothing happends, the screen is empty. dd if=u-boot-sunxi-with-spl.bin of=/dev/mmcblk1 bs=1024 seek=8 boot from SD http://imgur.com/a/OHxzm When it boots from SD the u-boot shows both (SD on MMC0 and EMMC on MMC1) I´m using the A20-OLinuXino-Lime2-eMMC_defconfig with some mods to my board. My emmc is unit is KLM8G1GEME-B041 and is connected to the board like the emmc unit is connected to A20-OLinuXino-Lime2_Rev_G http://imgur.com/a/GIY3W I did a hexdump on the SD and MMC and it looks the same with the "eGON.BT0" tag in the right position. SD http://imgur.com/a/AL6lv MMC http://imgur.com/a/bM5v3 Thanks!
  20. Hello! I'm using Wheezy under kernel 3.4.x on Lime2 with 7" LCD and i added fbcon=rotate:1 in boot.cmd and the console booted in portrait but LXDE is still in landscape. I also added FBDEV_ROTATE_CCW=90 but with no results. I can rotate the screen from the /usr/share/X11/xorg.conf.d/XX-fbturbo.conf file but every time i touch the screen the LXDE crashes. Any suggestions please how to rotate the screen in LXDE? Thank you!
  21. Hello. I've got physically rotated HDMI monitor and try using Olimex Lime 2 with simplefb graphics. I could rotate console in kernels compiled with CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y by using echo 3 > /sys/class/graphics/fbcon/rotate But what about graphical sessions? Like I install some desktop environment and in its screen properties rotation is grayed out! Any instructions please how to make HDMI screen rotation working with latest Igor's Olimex Lime 2 images? Preferrably for 4.x kernel since I believe it is more free software without proprietary blobs and plain software simplefb graphics handling. If I only could rotate it! Any help? http://www.igorpecovnik.com/2014/11/18/olimex-lime-debian-sd-image/
  22. Following the instructions from the download page for the Lime2-eMMC we tried to apply the commands listed, but it looks that something is garbled here source is not a command AFAIK and if I use it as an apt-get option the system complaints about missing entries in sources. What is the correct way?
  23. I was wondering if there is a significant performance difference with the lime2 when a heatsink is added? I plan on ordering a couple of heatsinks from ebay to try myself however I'm wondering if anyone from the community has any feedback. Thanks
  24. Hi guys! I've an Olimex LIME2 EMMC installed in a remote location: I installed it with Olimex provided image of debian Jessie, which has kernel 3.4.103-00033-g9a1cd03-dirty. The installation has been done over internal EMMC and it worked. Now, for various reason I would like to switch to armbian. I would like to install armbian over the existing image. so not to have to reinstall packages ad my local software. I would like to keep the installation on internal 4GB EMMC memory. I'm asking if it's possibile to do it without having to reinstall and possibily over ssh, because the board is in remote location. Thanks for your suggestions.
  25. Hi, I've tested more than 10 pcs of Lime2 rev. G and those that I received from Olimex in last supply (Jan 2017) has strange behavior, all of them. It won't boot if HDMI connector is plugged in (tested with two different screens). There is only simple message in console repeated crazy fast "rb int error!". Googling returned only two links to source code I use latest version 2017.01-armbian (Feb 02 2017 - 02:40:37) - Armbian_5.25_Lime2_Ubuntu_xenial_default_3.4.113.img When I try older Armbian 2016.09-armbian (Sep 15 2016 - 03:51:47 +0200) everything is fine. What has changed? I attach the beginning and the end of the serial console output (working HDMI not connected on the left, failing HDMI connected on the right). I have no idea how to debug this, only solution I can think of is sticking with older Armbian, which I really don't like. Thanks for your ideas!
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines