Ken Stephens Dec 10, 2020, 10:08 PM (4 days ago) I subscribe to a monthly electronic surprise box. This month's surprise is a Propeller 2 8x32bit processor on a circuit board that connects to a computer with U Tom <[email protected]> Dec 10, 2020, 10:26 PM (4 days ago) to me, Portland This message has been deleted. Restore message On Thu, 10 Dec 2020 22:08:08 -0800 Ken Stephens <[email protected]> wrote:
> I subscribe to a monthly electronic surprise box > <https://www.instructables.com/HackerBox-0061-Props/>. This month's > _______________________________________________ > PLUG: https://pdxlinux.org > PLUG mailing list > [email protected] > http://lists.pdxlinux.org/mailman/listinfo/plug Try plugging it in directly to the computer and unplugging adjacent USB devices. -- _________________________________________ / Scratch the disks, dump the core, Shut \ | it down, pull the plug Roll the tapes | | across the floor, Give the core an | | extra tug And the system is going to | | crash. And the system is going to | | crash. Teletypes smashed to bits. | | Mem'ry cards, one and all, Give the | | scopes some nasty hits Toss out halfway | | down the hall And the system is going | | to crash. And the system is going to | | crash. And we've also found Just flip | | one switch When you turn the power | | down, And the lights will cease to | | twitch You turn the disk readers into | | trash. And the tape drives will crumble | | | | in a flash. Oh, it's so much fun, When | | the CPU Now the CPU won't run Can print | | nothing out but "foo," And the system | | is going to crash. The system is going | | to crash. | | | | -- To the tune of "As the Caissons go | \ Rolling Along" / ----------------------------------------- \ \ /\ /\ //\\_//\\ ____ \_ _/ / / / * * \ /^^^] \_\O/_/ [ ] / \_ [ / \ \_ / / [ [ / \/ _/ _[ [ \ /_/ Johnathan Mantey [email protected] via <https://support.google.com/mail/answer/1311182?hl=en> pdxlinux.org Dec 11, 2020, 9:06 AM (3 days ago) to Portland This message has been deleted. Restore message What is the output from lsusb? On Thu, Dec 10, 2020 at 10:08 PM Ken Stephens <[email protected]> wrote: > I subscribe to a monthly electronic surprise box > <https://www.instructables.com/HackerBox-0061-Props/>. This month's Ken Stephens <[email protected]> Dec 11, 2020, 9:40 AM (3 days ago) to Portland This message has been deleted. Restore message # lsusb Bus 002 Device 003: ID 17e9:4301 DisplayLink Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 009: ID 046d:0802 Logitech, Inc. Webcam C200 Bus 003 Device 004: ID 046d:c318 Logitech, Inc. Illuminated Keyboard Bus 003 Device 003: ID 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0 Bus 003 Device 002: ID 0409:0058 NEC Corp. HighSpeed Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 058f:a014 Alcor Micro Corp. Asus Integrated Webcam Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Ken Stephens <[email protected]> Dec 11, 2020, 10:09 AM (3 days ago) to Portland This message has been deleted. Restore message Just plugging it into the 2.0 port by itself without another cable connected: $dmesg -T . . . [Fri Dec 11 09:45:48 2020] usb 2-1.1: new full-speed USB device number 28 using ehci-pci [Fri Dec 11 09:45:48 2020] usb 2-1.1: device descriptor read/64, error -32 [Fri Dec 11 09:45:48 2020] usb 2-1.1: device descriptor read/64, error -32 [Fri Dec 11 09:45:48 2020] usb 2-1.1: new full-speed USB device number 29 using ehci-pci [Fri Dec 11 09:45:48 2020] usb 2-1.1: device descriptor read/64, error -32 [Fri Dec 11 09:45:48 2020] usb 2-1.1: device descriptor read/64, error -32 [Fri Dec 11 09:45:48 2020] usb 2-1-port1: attempt power cycle [Fri Dec 11 09:45:49 2020] usb 2-1.1: new full-speed USB device number 30 using ehci-pci [Fri Dec 11 09:45:49 2020] usb 2-1.1: device not accepting address 30, error -32 [Fri Dec 11 09:45:49 2020] usb 2-1.1: new full-speed USB device number 31 using ehci-pci [Fri Dec 11 09:45:50 2020] usb 2-1.1: device not accepting address 31, error -32 [Fri Dec 11 09:45:50 2020] usb 2-1-port1: unable to enumerate USB device Exasperated, Ken Johnathan Mantey [email protected] via <https://support.google.com/mail/answer/1311182?hl=en> pdxlinux.org Dec 11, 2020, 10:37 AM (3 days ago) to Portland This message has been deleted. Restore message Do you have a different PC to make the attempt? On Fri, Dec 11, 2020 at 10:09 AM Ken Stephens <[email protected]> Ken Stephens <[email protected]> Dec 11, 2020, 10:52 AM (3 days ago) to Portland This message has been deleted. Restore message Jonathan, I've tried it on Tinkerboard, Jetson Nano, my Fedora Linux Lenovo, wife's Windows 8 Lenovo. Tinkerboard - ubuntu arm7l, Linux Jetson Nano - aarch64, Linux Lenovo's Intels i7 and i5. I am beginning to believe I blew the chip sometime. But, it blinks like the systems are trying to read its ID. Without reading the ID, my systems won't communicate with it. Thanks, Ken Galen Seitz [email protected] via <https://support.google.com/mail/answer/1311182?hl=en> pdxlinux.org Dec 11, 2020, 11:19 AM (3 days ago) to plug This message has been deleted. Restore message On 12/11/20 10:52 AM, Ken Stephens wrote: > Jonathan, > > I've tried it on Tinkerboard, Jetson Nano, my Fedora Linux Lenovo, wife's > Windows 8 Lenovo. > Tinkerboard - ubuntu arm7l, Linux > Jetson Nano - aarch64, Linux > Lenovo's Intels i7 and i5. > > I am beginning to believe I blew the chip sometime. But, it blinks like > the systems are trying to read its ID. Without reading the ID, my systems > won't communicate with it. Did you switch the jumper on the FT232 module to 3.3V? If not, the ft232 might be driving 5V into a pin that is expecting 3.3V. That would likely cause excessive current to flow from the module through a clamp diode in the P8X32 to the 3.3V regulator. Needless to say, this would be problematic. galen -- Galen Seitz [email protected] Ken Stephens <[email protected]> Dec 11, 2020, 11:30 AM (3 days ago) to Portland This message has been deleted. Restore message Galen, Yes I did before I soldered it to the board. Even checked the voltage: 3.22 V. Thanks, Ken Galen Seitz [email protected] via <https://support.google.com/mail/answer/1311182?hl=en> pdxlinux.org Dec 11, 2020, 11:50 AM (3 days ago) to plug This message has been deleted. Restore message On 12/11/20 11:30 AM, Ken Stephens wrote: > Galen, > > Yes I did before I soldered it to the board. Even checked the voltage: > 3.22 V. I suggest disconnecting the ft232 module from the prop board, and then trying to connect the ft232 to a known good USB port with a known good cable. This should tell you whether the ft232 is functional. Regarding drivers, I would expect any contemporary Linux kernel to already have the appropriate driver for an FTDI USB-serial device. Johnathan Mantey [email protected] via <https://support.google.com/mail/answer/1311182?hl=en> pdxlinux.org Dec 11, 2020, 1:07 PM (3 days ago) to Portland This message has been deleted. Restore message > Regarding drivers, I would expect any contemporary Linux kernel to > already have the appropriate driver for an FTDI USB-serial device. I agree. There's no need to do anything to get a FTDI UART operational. Have you asked the vendor about possible failure points? Russell Senior [email protected] via <https://support.google.com/mail/answer/1311182?hl=en> pdxlinux.org Dec 11, 2020, 6:03 PM (3 days ago) to Portland This message has been deleted. Restore message > Regarding drivers, I would expect any contemporary Linux kernel to > already have the appropriate driver for an FTDI USB-serial device. +1 One other suggestion (wild-assed guess based on not reading your full description) is your device might be drawing too much power? Portland Linux/Unix Group (pdxlinux.org) Thanks to all of you for your suggestions. Turned out to be a bad circuit board USB interface. I tried another one. It was recognized immediately. Ken On Fri, Dec 11, 2020 at 6:03 PM Russell Senior <[email protected]> wrote: > > Regarding drivers, I would expect any contemporary Linux kernel to > > already have the appropriate driver for an FTDI USB-serial device. > > +1 > > One other suggestion (wild-assed guess based on not reading your full > description) is your device might be drawing too much power? > _______________________________________________ > PLUG: https://pdxlinux.org > PLUG mailing list > [email protected] > http://lists.pdxlinux.org/mailman/listinfo/plug > Sans Serif _______________________________________________ PLUG: https://pdxlinux.org PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
