whitequark[cis] changed the topic of #glasgow to: https://glasgow-embedded.org · digital interface explorer · https://www.crowdsupply.com/1bitsquared/glasgow · code https://github.com/GlasgowEmbedded/glasgow · logs https://libera.irclog.whitequark.org/glasgow · matrix #glasgow-interface-explorer:matrix.org · discord https://1bitsquared.com/pages/chat
jn has quit [Ping timeout: 248 seconds]
jn has joined #glasgow
SophiaNya has quit [Remote host closed the connection]
SophiaNya has joined #glasgow
Alexeyan[m] has quit [Quit: Idle timeout reached: 172800s]
josHua[m] has quit [Quit: Idle timeout reached: 172800s]
lekapuz85_ has quit [Quit: Connection closed for inactivity]
Eli2_ has joined #glasgow
Eli2 has quit [Ping timeout: 252 seconds]
tom has joined #glasgow
tom has quit [Quit: leaving]
tom has joined #glasgow
<_whitenotifier-4> [glasgow] turmoni reviewed pull request #736 commit - https://github.com/GlasgowEmbedded/glasgow/pull/736#discussion_r1930971617
<_whitenotifier-4> [glasgow] turmoni synchronize pull request #736: Add ATmega8 and fix some minor bugs with program-avr-spi applet - https://github.com/GlasgowEmbedded/glasgow/pull/736
<_whitenotifier-4> [libfx2] bifferos closed issue #22: printf example code with baud 57600 and CPUCS = 0; - https://github.com/whitequark/libfx2/issues/22
Guest64 has joined #glasgow
Guest64 has quit [Client Quit]
<_whitenotifier-4> [libfx2] bifferos opened issue #24: No easy way to use the output of GPIF designer (version 1) - https://github.com/whitequark/libfx2/issues/24
<_whitenotifier-4> [libfx2] whitequark commented on issue #24: No easy way to use the output of GPIF designer (version 1) - https://github.com/whitequark/libfx2/issues/24#issuecomment-2616870405
<_whitenotifier-4> [glasgow] whitequark reviewed pull request #736 commit - https://github.com/GlasgowEmbedded/glasgow/pull/736#discussion_r1931178728
alephbias[m] has joined #glasgow
<alephbias[m]> When running the UART applet (`glasgow run uart -V 3.3 --pin-tx 1 --pin-rx 0 --port A -a tty`), I'm getting this message fairly often on start:
<alephbias[m]> > E: g.cli: cannot set I/O port(s) A pull resistors to low={} high={0}
<alephbias[m]> with it then shutting down (although still providing power to the DUT). What could be going on here? I'm using V, the second GND, 0, and 1.
<whitequark[cis]1> what are you powering with it?
<whitequark[cis]1> the pull resistor IC is using the DUT power, so if the DUT power (V pin) is sagging for some reason you will see this message
<whitequark[cis]1> if there's a big capacitor or something this will happen frequently
<alephbias[m]> I'm powering a small smart device I'm looking at. Could it be that I'm using long cables? Specifically the ones that come with PCB Bites.
sigstoat[m] has joined #glasgow
<sigstoat[m]> so you're charging up all the caps and regulators on the device. dunno what constitutes 'a big capacitor' but i'd wager you've hit the next nearest thing.
<alephbias[m]> That helped a lot, thank you you two. It ended up being an artifact of how I've been testing the DUT. a cheap power supply I had been using for other testing on this device was still connected, and that was the problem I believe.
<sigstoat[m]> ah, charging up its output capacitors or something perhaps?
<_whitenotifier-4> [glasgow] turmoni reviewed pull request #736 commit - https://github.com/GlasgowEmbedded/glasgow/pull/736#discussion_r1931261504
<alephbias[m]> Seems a likely explanation. I didn't realize that could happen, but :themoreyouknow:
<_whitenotifier-4> [libfx2] bifferos commented on issue #24: No easy way to use the output of GPIF designer (version 1) - https://github.com/whitequark/libfx2/issues/24#issuecomment-2617178325
<_whitenotifier-4> [libfx2] whitequark commented on issue #24: No easy way to use the output of GPIF designer (version 1) - https://github.com/whitequark/libfx2/issues/24#issuecomment-2617212793
bgamari has quit [Ping timeout: 252 seconds]
bgamari has joined #glasgow