odoll

  • Content Count

    36
  • Joined

  • Last visited

About odoll

  • Rank
    Advanced Member

Recent Profile Visitors

790 profile views
  1. Thx! Yes, I'm trying to connect to the console of a cubietruck. (Access from the cubietruck to the console of the espressobin works). Mine is a (fake) Prolific [177708.603331] usb 1-1: USB disconnect, device number 12 root@espressobin:~# ls -al /dev/tty* > tty.a [177965.718765] usb 1-1: new high-speed USB device number 13 using orion-ehci [177965.878745] usb 1-1: config 1 interface 0 altsetting 0 bulk endpoint 0x2 has invalid maxpacket 64 [177965.878792] usb 1-1: config 1 interface 0 altsetting 0 bulk endpoint 0x83 has invalid maxpacket 64 [177965.881592] usb 1-1: New USB d
  2. Hi, I'm using an esprossobin with Debian Stretch with Armbian Linux 4.19.56-mvebu64. However regardless inwhat USB-TTL / Serial adapter I connect to he espressobin's USB2.0 port I don't get a ttyUSB0 device I tried to use a Prolific and a couple of others I got lend from a friend
  3. I know it's not you to blame, but it's again disappointing with a GlobalScale product, which I bought as *up* to 1.2 GHz, just to find, that it's not even good enough to scale down to 1000/800, but even down to 800/800 to get a stable service.
  4. Started from 5.75 image again and installed the below one by one with a reboot in between linux-u-boot-espressobin-next 5.85 --> OK linux-stretch-root-next-espressobin 5.85 --> OK linux-image-next-mvebu64 5.84 --> hangs (linux-dtb-next-mvebu64 5.85) PS: Once again 5.75 -> linux-u-boot-espressobin-next 5.85 --> OK linux-stretch-root-next-espressobin 5.85 --> OK linux-dtb-next-mvebu64 5.85 --> OK but as there's no image between 5.75 and 5.84 I'll leave it that way for now (and I think you should revoke 5.84 as well
  5. OT: when the PSUs of my SheevaPlugs started to fail I "swore" myself not buy any other device from Globalscale in the future, but even though I did it again ...
  6. OK, imaged Armbian_5.75_Espressobin_Debian_stretch_next_4.19.20.img to other SD and started from scratch --> OK Did apt-get update & upgrade which brought me back to 5.85 (5.84 image), but system hangs again after reboot So I think it's up to you now ;-)
  7. booting from SD, too. Checked FS of the SD which is clean and dd'ed to another SD, but same issue
  8. Just updated both my cubietruck and espressobin to 5.85, however the latter doesn't up come again after the update (from 5.83 IMO). (Had to get it out of the basement and) the console gives me the following error msg, now: Marvell>> boot starting USB... USB0: Register 2000104 NbrPorts 2 Starting the controller USB XHCI 1.00 USB1: USB EHCI 1.00 scanning bus 0 for devices... 1 USB Device(s) found scanning bus 1 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found / ** Bad device usb 0 ** ## Executing script at 06d00000 W
  9. Thx for the reply. That's odd, so the issue might be caused by the fact, that I'm not using an original Prolific, but cheap "China" clone cable!? I though this wouldn't cause an issue with Linux, as it does with Windows (with the latter I had to downgrade to a former Prolific driver to get it working, as the actual would detect the "fake".)
  10. Hello, I own boards of two different manufactures, namely a Cubietruck and an Espressobin. Before a recent Kernel update these days I was still greeted with the following messages: Welcome to ARMBIAN 5.73 stable Debian GNU/Linux 9 (stretch) 4.19.17-sunxi Welcome to ARMBIAN 5.73 stable Debian GNU/Linux 9 (stretch) 4.19.18-mvebu64 But even after the update - IMO apt-get was telling we're going from 5.73 to 5.75 versions of the files the version number in the greeting is still 5.73 Welcome to ARMBIAN 5.73 stable Debian GNU/Linux 9 (stretch) 4.19.2
  11. thx! - but don't think so (using armbian as didn't want to bother with those details myself ;-)
  12. Sorry for hijacking this thread, but I'm also having (two) issues with having USB Serial Support not working. Background: I plan to migrate my setup off a Cubiertuck over to an Espressobin, and as both devices are "remote" in the basement I thought I could ease my life by cross-connecting their "uart/serial/usb/jtag" ports. So a micro-usb cable is connected from the CT's USB to the EB's micro-USB port Cubietruck with ARMBIAN 5.70 stable Debian GNU/Linux 9 (stretch) 4.19.13-sunxi root@share:~# lsusb Bus 003 Device 002: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Po
  13. BTW: fell into the same pit and also got it working again with flash-image-1g-1cs-1000_800_boot_sd_and_usb.bin (v? from May 10th 2018). Got mine with only one chip on the back just a few days ago shipped from Amazon/US. However to You can obtain numbers from the current boot prompt., what are the appropriate commands to figure the right u-boot version for a board? It might be helpful to mention those on the site as well ;-)
  14. Maybe a long shot: rather than setting up armbian on my new ESPRESSObin (epb), installing needed SW and tools, porting configs off my Cubietruck (cbt), would it be possible to tweak the cbt's SDcard / FS to boot on the ESPRESSObin? If I'm not mistaken the cbtis armhf based and all those binaries should also run on the epb!? Would it be "good enough" to add the arm64 architecture to the CBT with "dpkg --add-architecture arm64" and then to install linux-u-boot-espressobin-next linux-image-next-mvebu64 linux-headers-next-mvebu64 linux-firmware-image-next-