Replies: 4 comments 34 replies
-
|
You should probably check /var/log/syslog it sounds like the device is disconnecting and reconnecting from the USB bus. |
Beta Was this translation helpful? Give feedback.
-
|
It would seem that is the case. It does seem to disconnect after a short time then when I try to access it it re-connects, fails to respond and then will respond. The 'enable experimental.hotplug' in line 6 is interesting. Not sure what to do about this. Again, any suggestions? Use a different computer maybe, or different version of linux. I do not have issues with other usb devices like Hard Drives, flash drives or my mouse/keyboard. |
Beta Was this translation helpful? Give feedback.
-
|
Do you have a good power supply to the greaseweazel? I'm wondering if it's dipping. |
Beta Was this translation helpful? Give feedback.
-
|
Well, it's just powered from the notebook. Voltage at the floppy power connector is 5.09 volts, steady. I don't see a dip. I'll install the software on a different computer and see how that goes. Thank you for the quick replies. I have another intel computer with 18.04 and also some Raspberry Pi 3 and 4's. |
Beta Was this translation helpful? Give feedback.
-
|
Ok, I installed the software on a RPI-4 and it seems to work reliably. Must be some kind of conflict with my notebook or Ubuntu 20.04. I'm off to next steps. Have to read 5 1/4 and 8" disks from Cromemco with different format on track 0 side 0. Single density vs Double Density on the rest of the disk. Double Sided. This is true for both sizes. I'll try to figure out the command line for that. Thanks for the help. I might need help with the correct arguments to 'read' for this type of disk. |
Beta Was this translation helpful? Give feedback.
-
|
This seems to be along the same lines as issues #120 and #195, both closed inconclusively. Now, I use Ubuntu myself, so I'm sure this is not a universal issue. But somehow related to the combo of GW + maybe specific USB controller(s) + Linux kernel management of USB. Things to try:
|
Beta Was this translation helpful? Give feedback.
-
|
Agreed, it does seem to be a similar issue to #120 and #195. I did try a different cable, port and hub to no avail. I have not had an issue, so far, using the V4 on a Raspberry Pi 4. For my purposes, that is a reasonable solution. I suspect, though have not tested yet, an RPI 2 or 3 would also work. |
Beta Was this translation helpful? Give feedback.
-
|
Probably this actually comes down to Artery chips not behaving strictly to spec and Linux being stricter than Windows (which bends over backwards for shoddy devices). As an example, the Artery chips state in the datasheet that the built-in full-speed pull-up resistor has value between 1k and 1.5k, average 1.25k. That's a bit different than the USB spec requirement of 1.5k +/- 5% !! It works for maybe 99.9% of users but the spec is spec for a reason. |
Beta Was this translation helpful? Give feedback.
-
|
That would definitely explain why some work and others not. |
Beta Was this translation helpful? Give feedback.
-
|
If you email me your address (it is on my GitHub profile) then I could send you another to try. It's from a new batch using a slightly revised Artery MCU. |
Beta Was this translation helpful? Give feedback.
-
|
Posted. Please update us here when you test it! |
Beta Was this translation helpful? Give feedback.
-
|
I am having exactly the same problem on Arch. Has there been any further investigation/result on this? Here is my config and troubleshooting.
Everything works on Windows. On Linux, I get the following: When connecting the greaseweazle, this is the log: Then running the command: The log now shows that the board is reset and device enumerated again. FYI, one in a while, say 1 in 20 times, I would actually get proper output from "gw info". However, trying "gw info" again would reset the board again. Regards, Miki. |
Beta Was this translation helpful? Give feedback.
-
|
Sorry, small mistake. On SUCCESS, the log is: |
Beta Was this translation helpful? Give feedback.
-
|
Another very interesting observation! When I spam commands, i.e. send them with less than a second interval, the board seems to work! But if I delay for several seconds, the next command results in a crash invariably. The log is partial, because scrolling up seems to send some characters via serial and it resets the greaseweazle: |
Beta Was this translation helpful? Give feedback.
-
|
Thank you very much for this. I think that the hex string in parentheses is a packet not understood by Greaseweazle. Probably rejected and Linux reacts badly. Probably devices are required to handle this packet and so Linux determines we are in a bad state and resets the device. I'm away this week but this is enough info for me to dig into for now. Thanks again! |
Beta Was this translation helpful? Give feedback.
-
So it's a regular |
Beta Was this translation helpful? Give feedback.
-
|
Tracking the work in #282 |
Beta Was this translation helpful? Give feedback.
-
|
Please download and test the fixed firmware linked at the bottom of https://github.com/keirf/greaseweazle-firmware/actions/runs/4172267986 |
Beta Was this translation helpful? Give feedback.
-
|
Have you previously found that automatic entry to the bootloader works, or was this a first time for trying that? It would be weird if the very latest fix made it suddenly not work. |
Beta Was this translation helpful? Give feedback.
-
|
Jumper on two GND pins is fine for storage. |
Beta Was this translation helpful? Give feedback.
-
|
You can test the mode switching without update side effects by the way. |
Beta Was this translation helpful? Give feedback.
-
|
I had time to test this myself today, and it works fine for me. I forgot that I didn't even clock bump the bootloader. So probably the auto-mode switching isn't working for you for other reasons, but unrelated to this fix. |
Beta Was this translation helpful? Give feedback.
-
|
When I was updating to 2cc411c, auto bootloader switch did not work. My memory is not 100%, but I think I tried updating again after the update, and update was failing if I did not push the board to bootloader mode. But... I just tried both I also spent some quality time with greaseweazle in general, and all other operations are working well. |
Beta Was this translation helpful? Give feedback.
-
I just received a V4 and am having difficulty with the software. I'm using Ubuntu 20.04. I installed the Greaseweazle V4 sofltware/utility.
My issue: When I connect the device, the first time I try gw info I get device: not found. If I wait a couple of seconds then it works. If I continue trying repeatedly every few seconds, it continues to work. If I wait 5 or so seconds, I get not found then if I wait a couple seconds and try again, it responds and will continue to respond until I wait again.
If I poll it too many times in a row I get a python error. The error persists even if I disconnect and re-connect the V4. I waited an hour and the error went away temporarily.
I have tried different cables and different ports on the computer with the same results.
Examples below.
Any thoughts or suggestions?
R
richard@richard-Inspiron-15-3511:
$ gw info$ gw infoHost Tools: 1.3
Device:
Not found
richard@richard-Inspiron-15-3511:
Host Tools: 1.3
Device:
Port: /dev/ttyACM0
Model: Greaseweazle V4
MCU: AT32F403, 144MHz, 96kB SRAM
Firmware: 1.2
Serial: GW135194F34205400002919705
USB Rate: Full Speed (12 Mbit/s)
richard@richard-Inspiron-15-3511:~$
ERROR: After polling about 6 times in a row.
richard@richard-Inspiron-15-3511:
$ gw info$Host Tools: 1.3
Device:
Port: /dev/ttyACM0
Model: Greaseweazle V4
MCU: AT32F403, 144MHz, 96kB SRAM
Firmware: 1.2
Serial: GW135194F34205400002919705
USB Rate: Full Speed (12 Mbit/s)
Traceback (most recent call last):
File "/usr/local/bin/gw", line 8, in
sys.exit(main())
File "/home/richard/.local/lib/python3.8/site-packages/greaseweazle/cli.py", line 69, in main
res = main(argv)
File "/home/richard/.local/lib/python3.8/site-packages/greaseweazle/tools/info.py", line 122, in main
latest_version = latest_firmware()
File "/home/richard/.local/lib/python3.8/site-packages/greaseweazle/tools/info.py", line 47, in latest_firmware
tag = rsp.json()['tag_name']
KeyError: 'tag_name'
richard@richard-Inspiron-15-3511:
Beta Was this translation helpful? Give feedback.
All reactions