indigaz has quit [Quit: Ping timeout (120 seconds)]
indigaz has joined #beagle
vagrantc has quit [Quit: leaving]
indigaz has quit [Client Quit]
indigaz has joined #beagle
indigaz has quit [Quit: Ping timeout (120 seconds)]
indigaz has joined #beagle
brook has quit [Remote host closed the connection]
Guest52 has joined #beagle
<Guest52>
Hi
rob_w has joined #beagle
Parduz has joined #beagle
<Parduz>
I want to create an "etcher" image from my running BBB, but googling around to find an answer, i get opposite results (some says it can be done with dd, some says the result is unusable/won't boot/hangs Etcher.
<Parduz>
there's an utility, or a succesfull way, to make an etcher image from the flash of a BBB running Debian 10?
florian has joined #beagle
Parduz has quit [Ping timeout: 252 seconds]
ft has quit [Quit: leaving]
otisolsen70 has joined #beagle
Guest47 has joined #beagle
<Guest47>
HI
brook has joined #beagle
<Guest47>
need just several reviews from many users who test the beagle bone black in real active and continuous working and running for at least one 1 year ,what about the performance ???
<jkridner>
no impact on performance I’ve noticed, but i avoid regular eMMC writes.
<Guest47>
ok, thanks ,any feedback from some users make external connection with ModBus RTU devices over usb to serial converter or TCP/IP connection or using HEADER pins on the beagle itself ,I mean long time continuous running as well ???
<jkridner>
Well, I deploy stuff that has run a few years continuously. maybe 500-600 days for my longest uptimes. Always run from eMMC and avoid needless writes. Been using Balena. TCP over wifi or cellular. Headers connected to sensor boards—just I2C and GPIO.
<jkridner>
kinda want to search for my longest uptime now.
<Guest47>
and everything was going well so far right ???
<jkridner>
yeah.
<Guest47>
thanks for you,.
Guest47 has quit [Quit: Client closed]
shoragan has quit [Ping timeout: 240 seconds]
shoragan has joined #beagle
shoragan has quit [Quit: quit]
shoragan has joined #beagle
shoragan has quit [Client Quit]
shoragan has joined #beagle
brook has quit [Remote host closed the connection]
Parduz has joined #beagle
shoragan has quit [Ping timeout: 268 seconds]
shoragan has joined #beagle
CrazyEddy has quit [Ping timeout: 264 seconds]
brook has joined #beagle
Parduz has quit [Ping timeout: 252 seconds]
CygniX has quit [Remote host closed the connection]
CygniX has joined #beagle
Guest52 has quit [Ping timeout: 252 seconds]
Parduz has joined #beagle
Parduz89 has joined #beagle
brook has quit [Remote host closed the connection]
Parduz72 has joined #beagle
Parduz has quit [Ping timeout: 252 seconds]
Parduz89 has quit [Ping timeout: 252 seconds]
brook has joined #beagle
brook has quit [Remote host closed the connection]
rob_w has quit [Remote host closed the connection]
<zmatt>
make a flasher image of debian 10 ? that's a concerning request
<zmatt>
oh wait never mind, 10 is buster not stretch
brook has joined #beagle
brook has quit [Remote host closed the connection]
brook has joined #beagle
jfsimon1981_b has quit [Remote host closed the connection]
brook has quit [Ping timeout: 252 seconds]
jfsimon1981 has joined #beagle
shoragan has quit [Quit: quit]
shoragan has joined #beagle
shoragan has quit [Ping timeout: 246 seconds]
brook has joined #beagle
shoragan has joined #beagle
brook has quit [Remote host closed the connection]
SJFriedl has quit [Read error: Connection reset by peer]
SJFriedl has joined #beagle
buzzmarshall has joined #beagle
ogra has quit [Changing host]
ogra has joined #beagle
lucascastro has joined #beagle
brook has joined #beagle
florian has quit [Quit: Ex-Chat]
vagrantc has joined #beagle
brook has quit [Remote host closed the connection]
lucas__ has joined #beagle
lucascastro has quit [Read error: Connection reset by peer]
lucas__ has quit [Quit: Leaving]
mag has quit [Ping timeout: 268 seconds]
mag has joined #beagle
mag has quit [Ping timeout: 264 seconds]
mag has joined #beagle
jfsimon1981 has quit [Remote host closed the connection]
jfsimon1981 has joined #beagle
balrog has quit [Quit: Bye]
<jfsimon1981>
Struggling a bit with rs485 hald duplex
<jfsimon1981>
(f)
<jfsimon1981>
i don't quite understand the management of rs to handle the transciever DE/_RE, the line does'nt seem to be returning to high, althgouh i use uart2+rts/cts.
otisolsen70 has quit [Quit: Leaving]
<jfsimon1981>
I have to dig into this.
balrog has joined #beagle
<zmatt>
jfsimon1981: are you enabling rs485 mode on the tty to have the kernel automatically control the rts line as rs485 driver-enable ?
<zmatt>
(cts is not used in rs485 mode)
<zmatt>
(rs485 mode is very different from rts/cts based hardware handshake)
<jfsimon1981>
zmatt, good evening
<jfsimon1981>
I think not, when i write with the cu program the line doesn't return
<jfsimon1981>
i should enable rs485 mode i probably missed it
<zmatt>
well normally you wouldn't use a program like cu to control an rs485 port
<zmatt>
in C it can be enabled like this: https://pastebin.com/r1rJFUfr .. or if you're using python, py-serial also has options to enable it
<jfsimon1981>
thanks let me compile it
<zmatt>
in theory it can be enabled in device-tree, though that didn't seem to work yet in kernel 4.19
<jfsimon1981>
ok i struggled a bit with this, i have libmodbus handle it but the timing is not perfect and get many crc
<jfsimon1981>
hence i switch to kernel / driver solution
<zmatt>
didn't we have a fair amount of discussion about this a while back? or was that with someone else?
<jfsimon1981>
we discussed it
<jfsimon1981>
i think i enabled the cts/rts but i messed up so that the library makes use of it, through its internal timing
<jfsimon1981>
that kind of works, but it's not very reliable
<jfsimon1981>
i mean i don't think the underlying layer handles the rts signal, i'm trouble shooting it now
<zmatt>
the rts signal should be fully managed by the kernel and not touch at all by the library
<zmatt>
*touched
<zmatt>
it looks like libmodbus has support for using kernel rs485 mode though
<jfsimon1981>
yes that's why i did incorrectly, it seems the line never returns high when i send data through the dev. The library works but it through usleep() and writing to the pin, somehow it works.
<jfsimon1981>
Indeed but i had to tweak the timing
<jfsimon1981>
and it's sensitive to interrupt during frames
<zmatt>
that makes no sense if it's implemented correctly
<jfsimon1981>
also has to be tuned precisely to the client device, it's not good enough. Worked for prototyping.
<zmatt>
all this just sounds like stuff is very broken
<zmatt>
but didn't you also have the problem of a client device with broken timing? I seem to vaguely remember that
<jfsimon1981>
Yes the library has a byte length calculation, sends data to the uart, meanwhile it does a usleep() then toggles RTS.
<jfsimon1981>
Yes indeed, they respond instantanesouly
<zmatt>
that shouldn't happen
<zmatt>
I'm looking at the code, it shouldn't get there
<jfsimon1981>
Hence i had to tweak the library to trigger rts sooner, there was a slight overhead which messed up the half duplex for few first bits.
<zmatt>
so it shouldn't do any usleep at all
ft has joined #beagle
<zmatt>
the serial mode should be MODBUS_RTU_RS485, the rts mode should be MODBUS_RTU_RTS_NONE
<jfsimon1981>
ok
<jfsimon1981>
i activated RTS through the lib here
<jfsimon1981>
it should be none if handled by kernel you mean
<zmatt>
yes
<jfsimon1981>
yes that's what i messed precisely, the kernel didn't handle it and i got it throught library instead
<jfsimon1981>
hence timing issues
<jfsimon1981>
i correct it
<zmatt>
the only possible issue I see here is that it doesn't seem to allow configuring the polarity of the rts signal. it's possible you may need to fix that manually by using my code snippet ( https://pastebin.com/r1rJFUfr ) to configure the polarity (active-low or active-high) before using libmodbus
<zmatt>
(if the signal is inverted)
<zmatt>
I don't know what the default is
<jfsimon1981>
i want libmodbus to have not worry about this at all
<zmatt>
well libmodbus can't guess the polarity of the signal, that depends on your hardware
<jfsimon1981>
once the hardware is properly setup i'll have the kernel device handle it properly
<zmatt>
but it also doesn't offer an option to configure the polarity
<zmatt>
it seems
<jfsimon1981>
i think yes it can be configured, there's the option in set rts function.
<zmatt>
that isn't used in rs485 mode
<jfsimon1981>
But libmodbus won't have interface with rts if the device is handled by kernel probably
<jfsimon1981>
i'll work on it
<zmatt>
I'm talking about the polarity of the kernel-managed rs485 mode
<jfsimon1981>
yes
<jfsimon1981>
i'll check it, anyway i inverted with a simple transistors already in hw, because the transciever polarity was wrong
<zmatt>
that is silly since the polarity is determined by software
<jfsimon1981>
right i think i did that because of compatibility with software versions and physical modules
<jfsimon1981>
i have to be a bit careful, the client can update software on other modules too hence i can change it here, it would break the other modules they run if they updated it.
<jfsimon1981>
got to implement the kernel rts support, i'm on it now
brook has joined #beagle
brook has quit [Remote host closed the connection]
brook has joined #beagle
shodan45 has quit [Changing host]
shodan45 has joined #beagle
brook has quit [Remote host closed the connection]
buckket has quit [Remote host closed the connection]
buckket has joined #beagle
brook has joined #beagle
<jfsimon1981>
Hi, well no luck with uart2, though uart4 works, regarding rtscts
<jfsimon1981>
Just need to enable BB-UART4-RTSCTS-00A0.dts, set pinmux to uart.
<jfsimon1981>
(though couldn't get rts to toggle with uart2). Probably will switch to uart4 then, in hw too.
<zmatt>
for some reason that overlay doesn't mux the rxd/txd pins hence needs to be combined with the BB-UART4 overlay: https://pastebin.com/PkdvgViR
<zmatt>
or better, just either a custom overlay (that muxes txd, rxd, and rts) or use cape-universal