All Activity

This stream auto-updates   

  1. Past hour
  2. running sudo while you are root is redundant, sudo (superuser do) is intended for normal users to run some commands as root to fix DNS issue add this to the file /etc/hosts 127.0.0.1 localhost 127.0.1.1 bpi-iot-ros-ai # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters for the eMMC i think there is a tool they call bpi-copy as they state: "support bpi-copy to write SD/eMMC with img.zip file" but as @martinayotte already told your "dd" worked and you copied to eMMC.
  3. Connecting to: /dev/ttyUSB0 Changing monitoring state from 'Offline' to 'Opening serial port' Connected to: Serial<id=0xafdedf50, open=True>(port='/dev/ttyUSB0', baudrate=9600, bytesize=8, parity='N', stopbits=1, timeout=60.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor Changing monitoring state from 'Opening serial port' to 'Connecting' Changing monitoring state from 'Connecting' to 'Offline' Connecting to: /dev/ttyUSB0 Changing monitoring state from 'Offline' to 'Opening serial port' Connected to: Serial<id=0xb02054d0, open=True>(port='/dev/ttyUSB0', baudrate=9600, bytesize=8, parity='N', stopbits=1, timeout=60.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor Changing monitoring state from 'Opening serial port' to 'Connecting' Recv: 4��1q�1a��\x1fq1�dlqh�9� ��05p0��1h��W�d ���x4�p011x��R58������ Connection closed, closing down monitor There was a timeout while trying to connect to the printer Changing monitoring state from 'Connecting' to 'Offline' Connection closed, closing down monitor this octoprint Terminal log
  4. So, the log above shows that it is connecting to it...
  5. yes local ip i connect laptop and phone,
  6. I don't see any errors in the above, although I'm not familiar with what OctoPrint is used to provide as output. Is the IP address 192.168.0.104 is your printer ?
  7. hi thanks but now server some give error so : its connect but not control printer 2017-04-25 21:34:07,019 - octoprint.filemanager - INFO - Adding backlog items from all storage types to analysis queue... 2017-04-25 21:34:07,029 - octoprint.filemanager - INFO - Added 0 items from storage type "local" to analysis queue 2017-04-25 21:34:07,034 - octoprint.server - INFO - Reset webasset folder /home/pi/.octoprint/generated/webassets... 2017-04-25 21:34:07,056 - octoprint.server - INFO - Reset webasset folder /home/pi/.octoprint/generated/.webassets-cache... 2017-04-25 21:34:07,520 - octoprint.plugins.discovery - INFO - Registered OctoPrint instance on orangepilite for SSDP 2017-04-25 21:34:07,542 - octoprint.plugins.pluginmanager - INFO - Loaded plugin repository data from disk, was still valid 2017-04-25 21:34:07,673 - octoprint.server - INFO - Listening on http://0.0.0.0:5000 2017-04-25 21:34:07,788 - octoprint.server - INFO - Preemptively caching / (ui _default) for {'query_string': 'l10n=en', 'path': '/', 'base_url': 'http://192.168.0.149:5000/'} 2017-04-25 21:34:27,418 - octoprint.server.util.sockjs - INFO - New connection from client: 192.168.0.104 2017-04-25 21:34:38,213 - octoprint.server.util.sockjs - INFO - Client connection closed: 192.168.0.104 2017-04-25 21:34:38,834 - octoprint.server.util.sockjs - INFO - New connection from client: 192.168.0.104 2017-04-25 21:35:01,705 - octoprint.server.util.sockjs - INFO - Client connection closed: 192.168.0.104 2017-04-25 21:35:02,490 - octoprint.server.util.sockjs - INFO - New connection from client: 192.168.0.104
  8. I got a very friendly email of one of the maintainers of the sun8i-emac ethernet driver. See my posting on:
  9. I got a very friendly reply on my search for correct AppleTalk working on the sun8i-emac network driver. See this: Not sure how to use this fix in the building development, but maybe someone is willing to give some help!
  10. your screenshot seems to show that your have DNS issue with host bpi-iot-ros-ai, but I don't understand the relationship with "sudo". About the "dd" command, it worked succesffully since it displayed at the end "2807037952 bytes copied" ...
  11. In my Orange Pi One with ARMBIAN 5.27.170422 nightly Ubuntu 16.04.2 LTS 4.10.11-sun8i I install acpi: sudo apt-get install acpi And run sudo acpi_listen And nothing is show when I press the power button. Is normal or my button is damaged? Thanks
  12. Today
  13. Why can not I transfer the system to EMMC?
  14. I try again and again and same result... I think the last option is to recompile uboot... Do you have any documentation to help me in that task please @zador.blood.stained?
  15. Building the "Desktop" image, I got: HELLO! BOOT0 is starting! boot0 version : 3.0.0 reg_addr 0x01f00100 =0x00007347 reg_addr 0x01f00104 =0x0000703b reg_addr 0x01f00108 =0x5aa5a55a reg_addr 0x01f0010c =0x000000ff reg_addr 0x01f00110 =0x000000ff reg_addr 0x01f00114 =0x000000ff eraly jump fel U-Boot SPL 2017.03-armbian (Apr 25 2017 - 15:56:39) DRAM: 1024 MiB Trying to boot from MMC1 U-Boot 2017.03-armbian (Apr 25 2017 - 15:56:39 -0300) Allwinner Technology CPU: Allwinner A31? (SUN6I, id: 7) Model: Merrii A31 Hummingbird DRAM: 1 GiB MMC: SUNXI SD/MMC: 0 *** Warning - bad CRC, using default environment Setting up a 1024x768 vga console (overscan 0x0) Error: no valid bmp image at 66000000 In: serial Out: vga Err: vga Net: eth0: ethernet@01c30000 Hit any key to stop autoboot: 0 38518 bytes read in 147 ms (255.9 KiB/s) switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3550 bytes read in 204 ms (16.6 KiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc 128 bytes read in 175 ms (0 Bytes/s) 4256917 bytes read in 484 ms (8.4 MiB/s) 6189880 bytes read in 593 ms (10 MiB/s) Found mainline kernel configuration 40041 bytes read in 580 ms (67.4 KiB/s) ** File not found /boot/dtb/overlay/-fixup.scr ** ## Loading init Ramdisk from Legacy Image at 43300000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 4256853 Bytes = 4.1 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 43000000 Booting using the fdt blob at 0x43000000 Loading Ramdisk to 49bf0000, end 49fff455 ... OK reserving fdt memory region: addr=43000000 size=a000 Loading Device Tree to 49be3000, end 49beffff ... OK Starting kernel ... Uncompressing Linux... done, booting the kernel. And it Stucks at that point.
  16. Ok I test with 2 others sd card and a second A/C adapter. Same result for the first SD card, tested with the two alimentations. The second, after som tries (because I get block at : Trying to boot from MMC1), give me that: U-Boot 2017.01-armbian (Feb 02 2017 - 03:03:34 +0100) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi Plus 2E I2C: ready DRAM: 2 GiB MMC: SUNXI SD/MMC: 0, SUNXI SD/MMC: 1 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: phy interface7 eth0: ethernet@1c30000 Hit any key to stop autoboot: 0 6944 bytes read in 158 ms (42 KiB/s) switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 2652 bytes read in 194 ms (12.7 KiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc 123 bytes read in 134 ms (0 Bytes/s) Unknown command '▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒data abort pc : [<bdf714d4>] lr : [<bdf67930>] reloc pc : [<4a0184d4>] lr : [<4a00e930>] sp : b9f33c50 ip : bdfb0250 fp : 00000018 r10: b9f641a8 r9 : b9f38ee0 r8 : 00000000 r7 : 00000000 r6 : b9f643d8 r5 : b9f67426 r4 : 00000001 r3 : b9f67428 r2 : 00000000 r1 : fffffffe r0 : b9f67430 Flags: nZCv IRQs off FIQs off Mode SVC_32 Resetting CPU ... resetting ... U-Boot SPL 2017.01-armbian (Feb 02 2017 - 03:03:34) DRAM: 2048 MiB Trying to boot from MMC1
  17. I just wanted to share some instructions on how to control all GPIO pins on the OrangePi Zero Plus 2 board. These instructions are meant for newbies but it can be extremely helpful if you are new to Armbian, OPI and GPIO. At least it would have been for me. There is a total of 17 different pins to control according to the schematic below. These pins are highlighted in blue numbers that indicate what GPIO port they are available at. Use these numbers in order to know that pins to control. Look for instructions further down. First off some basics: Activate a pin by exporting it. For example. In order to activate IO-0 run: echo "352" > /sys/class/gpio/export Set the direction of the port. echo "out" > /sys/class/gpio/gpio352/direction Turn it on: echo "1" > /sys/class/gpio/gpio352/value Turn it off: echo "0" > /sys/class/gpio/gpio352/value To figure out what number to use for each pin follow the schematics above or read from the list below. I really have not figured out wether it is safe to control all pins(and not just IO-pins) for output but it seems to work when I verify with a voltmeter. These pins were identified using the official schematic for the board: http://linux-sunxi.org/File:ORANGE_PI-ZERO-PLUS2_V1_0.pdf If you are interested to learn how pins are identified based on the schematic please dig deeper into these files in the GIT repo: https://github.com/armbian/linux/blob/sun8i/drivers/pinctrl/pinctrl-sunxi.h https://github.com/armbian/linux/blob/sun8i/arch/arm/mach-sunxi/include/mach/pinctrl.h GPIO Table SDA = 12 SCL = 11 IO-GCLK = 6 IO-0 = 352 IO-2 = 353 IO-3 = 3 SPI1-MOSI = 15 SPI1-MISO = 16 SPI1-CLK = 14 TXD0 = 15 RXD0 = 16 IO-1 = 107 IO-4 = 19 IO-5 = 18 IO-6 = 2 SPI-CE0 = 13 SPI-CE1 = 110 I hope this helps someone.
  18. Please try another SD card and power supply first. This message U-boot loaded from SD means that u-boot was loaded correctly from SD and boot script was loaded correctly too, so SD card detection may be considered fixed.
  19. I try again tonight to fix the SD switch, then I got this log with a sd card in sd card reader: U-Boot 2017.01-armbian (Feb 02 2017 - 03:03:34 +0100) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi Plus 2E I2C: ready DRAM: 2 GiB MMC: SUNXI SD/MMC: 0, SUNXI SD/MMC: 1 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: phy interface7 eth0: ethernet@1c30000 Hit any key to stop autoboot: 0 6944 bytes read in 155 ms (43 KiB/s) switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 2652 bytes read in 191 ms (12.7 KiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc 123 bytes read in 132 ms (0 Bytes/s) ** ext4fs_devread read error - block The last line show a mmc error, no? If it's possible to recompile uboot to bypass this SDCard verification, do you think it's a better alternative for all Orange Pi's images? I'm not the first with this problem, as I can see in this forum... Can you tell me where I can found some documentations about that?
  20. Hello. I just got the board to play with, but I can't find any specific documentation on how to build a specific image to such board. After researching on google, foruns, etc. I've found some *mentions* on using the bananapim2 config and build (since they use the same core), but it's not working. Building an image using bananapim2 profile, after power on the device start booting from SD, but shows me: unknow image format and start asking for TFP to find flash. Can you please point me toward some useful information on how to build an Armbian image on such card? Thank you in advance
  21. Well, sdBoot.txt looks like abroken card detect switch. Other logs, however, looks like eMMC issue or powering issue, but if you got errors writing image from FEL mode it can be related to bad eMMC contents. So your best option is trying to bend/fix the SD switch first, if you can't make it work - then may be solder a piece of wire between SD card detect pin and ground to bypass the switch and boot from SD or prepare to recompile u-boot to skip the SD detection check.
  22. I'm baaaack with a TTL Cable! So this is how I process: 1: test with a flash sd card with armbian. TTL information in sdBoot.txt @zador.blood.stained I think it's a sd card switch broken like you said.. 2: Boot in FEL mode, flash EMMC with Disk32Imager. FEL Boot information in felBoot.txt. 3: Boot with only TTL cable + A/C Log in bootxMMC.txt. Sometimes, boot stuck from at "Trying to boot from MMC2", I ned to plug and unplug A/C (cf boot3EMMC.txt). I don't understand what happens on this card... @zador.blood.stained these logs help you to understand? boot1MMC.txt boot2MMC.txt boot3MMC.txt felBoot.txt sdBoot.txt
  23. Do any of you know of an Android 5 ROM for this box? That way, we could run a few benchmarks under termux, at least.
  24. Hi everybody! I have the Armbian OS on OrangePi PC and I try to connect it to my WiFi router. For this purpose I have a Realtek USB RTL8188. I tried to connect it a couple of time, but it was unsuccessful. The "Connecting" pop-up window remains on the screen for minutes without connecting to the internet. Perhaps the Armbian does not have the right driver for this device? I have it, but I have no idea how to install it. Can someone help me, please?
  25. So next challenges are * CPU Frequency stuff.. DFS? * network interface management -- either eliminate network manager for now or like patch it. Network Manager isn't equiped to deal with the interfaces because they're on a distributed switch. NM does too much low level stuff... I saw a thread from august on a networkmanger bugtracker somewhere also identify that weakness, but it doesnt' look like it's been solved yet.
  26. Thank you, zador.blood.stained.
  27. BTW, this is not a page from Armbian web site ...
  1. Load more activity