On 8/19/2017 4:51 PM, mugginsac wrote:
> OK, I can now get a /dev/ttyUSB0. I had to add altera vendor id 0x09fb and
> DE10
> product id 0x6810 to ftdi_sio. I have to plug in the USB cable from the DE10
> to
> get ftdi_sio to load. Then by the time I get it plugged in and putty loaded
> there
On 8/20/2017 6:38 PM, mugginsac wrote:
> OK, my face is red. Yes I was plugging into the wrong port. It is running
> u-boot-with-spl but it is looking for an ext2 partition instead of an ext4.
> So
> after a while it starts looking for a USB device.
With the three different USB ports, it's
On 8/20/2017 4:03 PM, mugginsac wrote:
> Well it appears that the not so fun situation is the case. When I unplug
> power
> from the DE10-Nano the ftdi chip disappears. I also tried plugging DE10 cable
> into a powered hub instead of directly into the desktop box but same result.
>
> How about
OK, my face is red. Yes I was plugging into the wrong port. It is running
u-boot-with-spl but it is looking for an ext2 partition instead of an ext4.
So after a while it starts looking for a USB device.
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
Well it appears that the not so fun situation is the case. When I unplug
power from the DE10-Nano the ftdi chip disappears. I also tried plugging
DE10 cable into a powered hub instead of directly into the desktop box but
same result.
How about if I plug in the DE10, get the ttyUSB0 and then
On 8/20/2017 4:35 PM, Charles Steinkuehler wrote:
> On 8/20/2017 4:03 PM, mugginsac wrote:
>> Well it appears that the not so fun situation is the case. When I unplug
>> power
>> from the DE10-Nano the ftdi chip disappears. I also tried plugging DE10
>> cable
>> into a powered hub instead of
I rebuilt the uSD with an ext2 filesystem.
At first I got a bunch of messages related to the initialization. Then a
bunch of characters seem to scroll down the right side of the "terminal"
screen in a single column.
Then after awhile, I got a login prompt in minicom, but I couldn't get it
to
