e3d3 | How can I enable serial connection with the ch430 driver (for my micro-controllers) ? | 18:00 |
---|---|---|
gnarface | not sure about that one specifically but i think it's just a question of loading the kernel module then connecting to the tty | 18:06 |
gnarface | you might not even need to manually load the module | 18:06 |
gnarface | minicom worked for me | 18:08 |
gnarface | there's probably several other options too though | 18:08 |
e3d3 | minicom, isn't that a serial program ? | 18:08 |
gnarface | yea, isn't that what you're trying to do? | 18:09 |
e3d3 | Yes, but I prefer to have also ch430 support in Arduino IDE | 18:09 |
gnarface | i guess you'd want something lower level | 18:10 |
gnarface | but the point is that it should just show up in /dev/ | 18:10 |
gnarface | and then you can connect to it with anything that can handle a serial device | 18:11 |
gnarface | if it doesn't, try loading the module | 18:11 |
gnarface | if it doesn't show up in /dev/ that is | 18:11 |
comment_system[m | i use picocom and python serial module | 18:12 |
e3d3 | I never checked if the "ch430" boards showed up in /dev | 18:12 |
e3d3 | Yes, I see a ch430 board recognized. Don't know how to find out its port | 18:20 |
e3d3 | sorry dmesg did show it but I missed it | 18:22 |
Xenguy | minicom, that sure takes me back | 18:24 |
e3d3 | I'm not sure if I have a ch430 problem. Arduino find the serial port but don't give me serial connection so I program my microcontrollers with ISP instead of via USB | 18:28 |
djph | normally, /dev/ttyUSB# | 18:30 |
djph | don't forget to be in the dialout group | 18:31 |
e3d3 | djph: that part already works okay. Only 'Chinese' mcu-boards with ch430 serial driver don't work yet. | 18:33 |
djph | e3d3: hm, my ch340s work fine | 18:34 |
djph | oh, 430 is new | 18:34 |
e3d3 | what do you mean with new ? | 18:34 |
djph | new as in I've not seen that before | 18:34 |
djph | sure it's not a 340? | 18:34 |
e3d3 | my ch430 boards are old, ca. 10 years | 18:35 |
djph | huh, haven't seen "ch430" ever :( | 18:35 |
e3d3 | I'm not sure. I'm blond & old, so have to start almost completely new after a long electronics break. I'm also impatient and hate to read/learn everything again. I have a lot of old notes, but not about this. | 18:39 |
djph | plug it in, see what dmesg says about it | 18:40 |
e3d3 | something like; ch341-uart converter now attached to ttyUSB0 | 18:41 |
djph | well, there you go | 18:42 |
djph | it's a 340 and it's /dev/ttyUSB0 | 18:42 |
e3d3 | indeed, but I can't upload code to some boards via USB and Arduino IDE, and use ISP programming. 'Good' board are also recognized as with ch431-uart converter but I don't know where else to look for a remedy | 18:46 |
djph | well, did you trash the arduino bootloader on those boards? | 18:48 |
e3d3 | that wouldn't surprise me. I'm good in trashing | 18:49 |
e3d3 | I even can't burn new bootloaders via ISP on those boards | 18:49 |
e3d3 | guess I have to read again about the fuses | 18:50 |
gnarface | what speed did you use? try a slower speed? | 18:53 |
e3d3 | I tried using a lower speed for burning a new bootloader but that didn't work | 18:54 |
gnarface | did you use dd to actually burn it? | 18:55 |
e3d3 | I tried only 1 or 2 different baudrates. No I didn't use dd. I tried it only with avrdude and Arduino IDE | 18:56 |
e3d3 | I also tried many other online found solutions, like a condensator on resetpin, fuse-resetting via 5V ISP and more | 18:57 |
e3d3 | luckily I have enough MUC's around that are still programmable | 18:59 |
e3d3 | I tried minicom, since long ago, and finally have my usb serial connection | 19:09 |
e3d3 | gnarface: djph I thank you both again very much for your friendly & patience help | 19:12 |
rwp | I am seeing this fetch error. | 22:55 |
rwp | E: Failed to fetch http://deb.devuan.org/merged/pool/DEBIAN-SECURITY/updates/main/c/cyrus-sasl2/libsasl2-modules_2.1.27+dfsg-1+deb10u2_i386.deb Hash Sum mismatch | 22:55 |
rwp | Is this something upstream? Or is it just me? | 22:56 |
rwp | Full details: https://paste.debian.net/plain/1232362 | 22:57 |
rwp | I am thinking that I have latched a failure from one of the several round-robin mirrors. | 22:58 |
bb|hcb | Do you see an ip address in your logs? | 23:00 |
rwp | No. It's a little hard to tell which one it latched onto. If no one else has noticed then I will manually select a particular mirror and update again. | 23:01 |
bb|hcb | I just checked, landed on 146.75.2.132, 2a04:4e42:70::644 and it was ok | 23:02 |
rwp | I selected a specific mirror and did not have the problem. So it must just be one of the mirrors out there. | 23:05 |
bb|hcb | https://paste.debian.net/1232363/ | 23:12 |
bb|hcb | ^^^ onefang | 23:13 |
bb|hcb | rwp: but my test misaligns with your result, because you got the proper file length | 23:14 |
bb|hcb | BTW. the above is a non-forked package, so it comes from a Debian mirror; each Devuan mirror has a different policy for the Debian packages redirect; there it would land on another rr | 23:17 |
rwp | bb|hcb, At least you confirmed that there is at least one mirror out there (Debian in this case) that has a bad copy of that file. | 23:18 |
rwp | So it isn't just me. I was just the lucky one this time. I have now used up my luck for the day. | 23:19 |
rwp | bb|hcb, I find your checksum check clever btw. :-) | 23:20 |
bb|hcb | So the broken one is mirror.vpgrp.io/185.183.113.131 for the above file it gives 404 instead of redirecting to a Debian mirror | 23:26 |
nemo | bb|hcb: huh. report to debian? | 23:27 |
bb|hcb | nemo: No, just the above mirror is misconfigured, that is not a Debian problem | 23:28 |
nemo | bb|hcb: right. I mean, maybe debian should drop them from mirror list if they are misconfigured | 23:29 |
nemo | until it is resolved | 23:29 |
bb|hcb | mirror.vpgrp.io is a Devuan mirror. And its redirects are not proper, onefang will remove it from rr until fixed | 23:31 |
nemo | ahhh | 23:31 |
nemo | ok. report to devuan then ☺ | 23:31 |
nemo | I'm never clear as to how exactly that works. but I guess all requests go through devuan mirrors and then it bounces on up to debian if it is an unmodified debian package, presumably true 95% of the time? | 23:32 |
bb|hcb | exactly | 23:32 |
bb|hcb | JFTR such problems are best solved by retrying - the second request will most probably land on a working mirror | 23:35 |
Guest59 | it's incredible that an entire OS needs to be forked just to mitigate systemd | 23:48 |
Guest59 | I like the all-in-one magnet download, that's actually great | 23:50 |
Guest59 | p.s. last night when I was trying to download the .torrent wouldn't work for me but the magnet link did | 23:50 |
Guest59 | maybe the .torrent has some stale info | 23:51 |
Guest59 | that was from section "Torrent and Magnet Link" at https://www.devuan.org/get-devuan | 23:51 |
bb|hcb | Guest59: Can you share the infohash of the torrent? | 23:52 |
Guest59 | https://files.devuan.org/devuan_chimaera.torrent (I've since removed things from my torrent client, metered bandwidth) | 23:53 |
bb|hcb | Ookay, the magnet is an older one that does not include the newly added -pool ISOs, while the .torrent is newer and may not have enough seed | 23:56 |
libh | Does devuan use the debian key if coming directly from upstream or do you resign packages? | 23:57 |
Guest59 | sounds like the torrent links need updating | 23:58 |
bb|hcb | Unforked packages are used unmodified, hence they are signed by Debian... | 23:58 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!