mag_ has joined #beagle
mag has quit [Ping timeout: 272 seconds]
ikarso has quit [Quit: Connection closed for inactivity]
starblue1 has quit [Ping timeout: 240 seconds]
starblue1 has joined #beagle
thinkfat_ has joined #beagle
thinkfat has quit [Ping timeout: 256 seconds]
Shadyman has joined #beagle
frostsnow has quit [Ping timeout: 256 seconds]
buzzmarshall has quit [Quit: Konversation terminated!]
vagrantc has quit [Quit: leaving]
Jessica has joined #beagle
Jessica has quit [Client Quit]
ikarso has joined #beagle
JarrettB has joined #beagle
<JarrettB> hello, I've been given what I believe to be a BeagleBoard rev D (if the sticker by "ASSY REV" on the silkscreen is what indicates that). I've been trying to get it to work by following the "getting started" page but haven't had much luck. I used the "Stretch for BeagleBoard via microSD card" image and burned it to an 8GB SD card with balenaEtcher.
<JarrettB> when I plug in the BeagleBoard to my computer (mac OS Catalina 10.15.5), it *seems* like it's booting. the USR0 LED flashes in the heartbeat pattern and USR1 looks like what I'd expect to see while it's loading the OS off the SD card. but I never get a network device enumerated on my computer. I tried using an FTDI USB-serial adapter to look at
<JarrettB> what's coming out of the serial port, and while I *am* getting data that looks like, well, a linux bootup, it's garbled. it looks like what you'd get with the wrong baud rate, but I have my software set exactly the way all the docs expect (115200, 8-N-1, no flow control). I've tried multiple serial terminal programs and they all give the same
<JarrettB> results. I've tried different baud rates all the way down to 9600 and they all give the same results.
<JarrettB> the one thing I haven't tried yet is just plugging something into the HDMI (well, DVI) out and see if it displays anything, but I don't know if it would?
<JarrettB> (I just tried with the Angstrom image from 2012-01-11 with the same results as well)
otisolsen70 has joined #beagle
otisolsen70 has quit [Remote host closed the connection]
otisolsen70 has joined #beagle
rob_w has joined #beagle
frostsnow has joined #beagle
<singyee> hi
singyee has joined #beagle
singyee49 has joined #beagle
<singyee49> I would like to ask more about BBB
<singyee> Add sram to bbb
<singyee> any recommendation?
<rob_w> sram? why that ?
florian has joined #beagle
starblue1 has quit [Ping timeout: 256 seconds]
starblue1 has joined #beagle
otisolsen70 has quit [Quit: Leaving]
singyee49 has quit [Quit: Client closed]
singyee has quit [Quit: Client closed]
<zmatt> JarrettB: beagleboard or beaglebone?
<zmatt> JarrettB: also, why are you trying to flash an ancient stretch image? all current images are buster
<zmatt> JarrettB: and angstrom is prehistoric and long dead
<zmatt> JarrettB: is the ftdi serial adapter maybe one for 5V rather than for 3.3V ?
kveremitz has quit [Ping timeout: 256 seconds]
kveremitz has joined #beagle
M-blaise has joined #beagle
florian has quit [Quit: Ex-Chat]
<lucascastro> Where can I get the cape manager patch?
Duality has joined #beagle
<Duality> hi
SJFriedl has quit [Read error: Connection reset by peer]
SJFriedl has joined #beagle
SJFriedl has quit [Read error: Connection reset by peer]
SJFriedl has joined #beagle
rah has joined #beagle
<rah> are there Debian images for bullseye or bookworm?
akaWolf has quit [Ping timeout: 256 seconds]
SJFriedl has quit [Ping timeout: 240 seconds]
SJFriedl has joined #beagle
<Duality> Question about like linux I am running Ubuntu on A am335x but we were having power issues it seems that at a reboot Linux puts a certain value into the tps which sets vdd_mpu to a low voltage
<Duality> and at boot (after a reboot) this voltage is to low to run the RAM reliably
<Duality> But it is linux setting this value at reboot I am trying to figure out which process does that
<Duality> any ideas?
<Duality> or maybe it's the tps driver doing that
SJFriedl has quit [Ping timeout: 240 seconds]
SJFriedl has joined #beagle
<JarrettB> zmatt: I'm trying to flash stretch (2018-10-07) because the buster images don't list the original beagleboard on their compatibility lists. is the board I have, though slightly different from the pic I think because the pic is an earlier rev. is where I got the image, it's
<JarrettB> the third one in the "recommended debian images" section
JarrettB has quit [Ping timeout: 256 seconds]
kveremitz has quit [Ping timeout: 260 seconds]
<zmatt> lucascastro: cape manager has been deprecated for quite a while, nowadays cape detection is done by u-boot, which applies the overlays to the DT before passing it to the kernel
<zmatt> rah: there are testing images / snapshots:
akaWolf has joined #beagle
JarrettB has joined #beagle
das has joined #beagle
<das> hi, what's the usual max admissible heat for SMC resistors? think I fried a bunch when resoldering @350°C
otisolsen70 has joined #beagle
M-blaise has quit [Quit: WeeChat 2.8]
<zmatt> Duality: ehh, your description doesn't make quite sense... the ram isn't powered by vdd_mpu, it has its own supply, also the pmic voltages are reset by u-boot as early as possible in SPL to try to deal with erratum 1.0.24 (boot being unreliable if a warm reset happens while vdd_mpu or vdd_core is configured as OPP50 level in the pmic, since the awful tps65217 has no mechanism to ensure its voltages ...
<zmatt> ...get reset at warm reset)
<zmatt> Duality: if the voltage gets set too low for reliable operation once the kernel is running, that would be a major bug in either the kernel driver or the dts (or maybe the power management firmware if it's involved, but I think it only messes with the pmic on entering/exiting deep sleep)
<zmatt> Duality: is this a BBB or a custom board?
<zmatt> Duality: if custom, and you're using an AM335x that's not speedbinned for 1 GHz, beware when basing your dts on that of the BBB, since the BBB modifies the OPP tables (declared in the base am33xx.dtsi) to inform the kernel that 1 GHz operation is always supported (since all BBBs support 1 GHz but a very early batch had an AM335x whose efuse bits erroneously didn't indicate 1 GHz support)
<zmatt> Duality: accidently using that modification on an am335x that doesn't support 1 GHz would cause the kernel to unintentionally overclock/overvolt the cortex-A8
<rcn-ee> zmatt: kinda wonder how 'speed' binned the parts are really... or just market segements... but OC'ing is not recommended...
<zmatt> rcn-ee: me neither, but you probably don't want to find out in production ;)
<rcn-ee> in the field, when it's 40F below, with a wind... ;)
vagrantc has joined #beagle
buzzmarshall has joined #beagle
<zmatt> Duality: slight correction to what I said earlier: I think u-boot might actually lower the PLL frequencies first (super early) and then raise them again later once the pmic has been configured, not sure though, too lazy to dig through it to see what it actually does nowadays
<rcn-ee> Duality: did you clone the Beaglebone's eeprom value? this is one place in u-boot:
rob_w has quit [Quit: Leaving]
<zmatt> fixing the erratum of the pmic voltage not being reset at reset is one of various improvements the tps65218 has over the tps65217 ... (though the BBB would break that anyway with the huge capacitor on the reset line that completely absorbs the low-pulse the cpu generates on warm reset)
<zmatt> :P
<zmatt> prior to the new BBB revision that is
kveremitz has joined #beagle
kveremitz has quit [Ping timeout: 240 seconds]
kveremitz has joined #beagle
JarrettB has quit [Ping timeout: 256 seconds]
lucascastro has quit [Quit: Leaving]
Duality has quit [Remote host closed the connection]
kveremitz has quit [Ping timeout: 240 seconds]
kveremitz has joined #beagle
ketas has quit []
das has quit [Remote host closed the connection]
JarrettB has joined #beagle
<jkridner> anyone else having problems with the irccloud app?
<jkridner> zmatt: fyi, now has #beagle and #beagle-* as a registered project space (whatever the term for that is)
kveremitz has quit [Quit: ZNC -]
ketas has joined #beagle
kveremitz has joined #beagle
ikarso has quit [Quit: Connection closed for inactivity]
<JarrettB> the documentation seems to imply that I should be able to connect from the beagleboard to a monitor with an HDMI cable... is that the case, or is an HDMI -> DVI cable required? right now my monitor is seeing *something* but it's unhappy and says the mode is unsupported
<JarrettB> I just want to see if this damn thing is working lol
<JarrettB> am I gonna have to break out the oscilloscope's serial decoder, geez
<JarrettB> OKAY. I managed to find an HDMI -> DVI adapter and *it is booting and showing a desktop yay!* now why doesn't it work with just HDMI
<JarrettB> I guess that's just a monitor compatibility thing, oh well
lucascastro has joined #beagle
<lucascastro> zmatt: what about the 0002-U-Boot-BeagleBone-Cape-Manager.patch that it's generated when git format-patch
<lucascastro> 0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch implement uname_boot
<lucascastro> the 0002-*.patch is not needed?
<JarrettB> alright it *does* work with HDMI, it just takes like 15 seconds before it switches into a mode that the monitor likes. so I think I'm good now. still wondering about what image is best to use with the plain old beagleboard, and I think you may be onto something wrt. the 3.3V/5V issue with my FTDI zmatt, but at least I know the thing is working so
<JarrettB> the serial is secondary
<rah> zmatt: where are they?
<rah> zmatt: that page only talks about them but doesn't say anything about where to get them
<rah> s/page only/page/
<JarrettB> seems like there are downloads a little further down the page rah
<rah> JarrettB: not here
<JarrettB> it's not showing up for you?
<rah> hmm, apparantly that page needs javascript to.. display the page
<JarrettB> ahh lol
<JarrettB> the unfortunate reality of the modern web
<rah> I found the image on that page earlier and tried it, it came up but the network interface showed the link as being down for no apparent reason so I moved on
<rah> currently doing a dist-upgrade from buster
<rah> I'm using an X15
<rah> presumable the image hasn't been tested on that board
<rah> *presumably
<rcn-ee> rah: what issue? please reply on that thread.. the v5.10.x kenrel is a little new, so still working out all the regressions.
<rcn-ee> ti changed the network driver, cpsw-new now... so on am335x we were fighting issues.. on teh bbai, it seemed to work, wonder what broke on the x15 for you..
<rcn-ee> it's also the first time with systemd-networkd, wonder if it got confused with teh dual ethernet on the x15..
<JarrettB> *oh,* apparently the serial port outputs 12Vpp cause it's compliant RS-232... I hope that didn't do anything to my FTDI
<rcn-ee> JarrettB: which version do you have BeagleBoard Classic Bx or Cx revision?
<rah> rcn-ee: to be honest, interacting with that mailing list in the past has drained me of all interest in doing so again
<JarrettB> rcn-ee I think it's D. the "ASSY REV" sticker says D
<JarrettB> the one by the user/reset buttons
<rcn-ee> rah: it's even worse now... ti rewrote the driver.. we have no fixup for phy... going forward..
<rcn-ee> JarrettB: ah so the last BeagleBoard Classic..
<JarrettB> yeah
<rah> rcn-ee: worse than why you just stopped communicating about it for no reason?
<rah> s/than why/than when/
<rcn-ee> rah: sorry, i do have a day job... BeagleBoard is my free time..
m-atoms has joined #beagle
<rcn-ee> rah the bullseye image: uses u-boot v2021.10 which has that fix... which still doesn't work 100%..
<rcn-ee> JarrettB: this is the serial pinout on that old board... Look at teh Schematic of this adapter...
<rcn-ee> it was based on an old rs232 motherboard spec..
<JarrettB> oh I actually have one of those pin-header-to-DB9 cables, but it's not much use to me cause I don't have a serial port on any of my computers
<JarrettB> I've only ever needed the FTDI to do serial before cause I've only used things that did low-voltage UART
<rcn-ee> JarrettB: ah! i use the usb-ftdi with a real rs232 header on it... but be very very careful, the original Beagle lacks a lot of protection..
<JarrettB> good to know!
<JarrettB> thanks!
kveremitz has quit [Ping timeout: 245 seconds]
lucascastro has quit [Ping timeout: 240 seconds]
JarrettB has quit [Quit: Client closed]
lucascastro has joined #beagle
otisolsen70 has quit [Quit: Leaving]
ikarso has joined #beagle
<zmatt> rah: note that the latest bbb revision allows the phy to be reset using a gpio, so what we really need is some code in u-boot that checks if the phy is in a weird state and resets it until it works properly
<zmatt> rah: that forum thread does seem confusing... it does looks like mainline u-boot contains the fix, currently at least
m-atoms has quit [Quit: Leaving]
kveremitz has joined #beagle
waldo323 has quit [Ping timeout: 256 seconds]