Hi all,
I just had a very strange experience with USB cables updating my Intellijel Sealegs firmware from 1.1.0.0. to 1.1.1.0. and am hoping someone can shed some light on the cause of this problem. I didn't put this in the Sealegs thread because it's really more about identifying issues with the types of USB cables used to update firmware & I thought it could be common to all formats of modules so put it here.
I have several USB cables that connect to the laptop (Type A) on one end and to the thin wedge shaped end (USB 2.0 Micro-B) which I use to charge and sync my mp3 on the other. I went through about 5 or 6 of this configuration of USB cables until I finally found one that would allow the Sealegs to communicate with the laptop and upgrade the firmware. Then I got curious about these USB cables that didn't work and used them to connect my mp3 to the laptop. To my surprise, they only allowed the mp3 to charge but would NOT provide access to the mp3 file system. Then I tried the cable that worked with the Sealegs, connecting my mp3 to the laptop. This one both charged the mp3 AND allowed access to the file system.
I'd like to buy some new USB cables so don't have to worry about this in the future but I want to first understand what went wrong. So is there an explanation for why this happened? Out of several Type A to USB 2.0 Micro-B USB cables (2 or 3 which had never been used before) did most of them not connect the Sealegs to the PC or both charge and allow access to the MP3 filesystem? Were they just defective cables - but then why do they connect enough to allow the MP3 to charge? Would it have something to do with the Type A end being USB 1.0 vs 2.0?
Thanks!
I just had a very strange experience with USB cables updating my Intellijel Sealegs firmware from 1.1.0.0. to 1.1.1.0. and am hoping someone can shed some light on the cause of this problem. I didn't put this in the Sealegs thread because it's really more about identifying issues with the types of USB cables used to update firmware & I thought it could be common to all formats of modules so put it here.
I have several USB cables that connect to the laptop (Type A) on one end and to the thin wedge shaped end (USB 2.0 Micro-B) which I use to charge and sync my mp3 on the other. I went through about 5 or 6 of this configuration of USB cables until I finally found one that would allow the Sealegs to communicate with the laptop and upgrade the firmware. Then I got curious about these USB cables that didn't work and used them to connect my mp3 to the laptop. To my surprise, they only allowed the mp3 to charge but would NOT provide access to the mp3 file system. Then I tried the cable that worked with the Sealegs, connecting my mp3 to the laptop. This one both charged the mp3 AND allowed access to the file system.
I'd like to buy some new USB cables so don't have to worry about this in the future but I want to first understand what went wrong. So is there an explanation for why this happened? Out of several Type A to USB 2.0 Micro-B USB cables (2 or 3 which had never been used before) did most of them not connect the Sealegs to the PC or both charge and allow access to the MP3 filesystem? Were they just defective cables - but then why do they connect enough to allow the MP3 to charge? Would it have something to do with the Type A end being USB 1.0 vs 2.0?
Thanks!
Statistics: Posted by WytchCrypt — Mon Feb 26, 2024 4:20 pm — Replies 4 — Views 85