sbach has quit [Read error: Connection reset by peer]
sbach has joined #openocd
nerozero has joined #openocd
c4017w_ has joined #openocd
c4017w__ has quit [Ping timeout: 240 seconds]
ericonr has quit [Ping timeout: 256 seconds]
Fist0urs has joined #openocd
ericonr has joined #openocd
Krazubu has joined #openocd
c4017w__ has joined #openocd
c4017w_ has quit [Ping timeout: 250 seconds]
Hawk777 has quit [Quit: Leaving.]
Krazubu has quit [Quit: My Mac Pro has gone to sleep. ZZZzzz…]
c4017w_ has joined #openocd
c4017w__ has quit [Ping timeout: 256 seconds]
Haohmaru has joined #openocd
<Xogium>
well time to try and fix sound on the board… what did I break ;)
<Xogium>
hmm
<Xogium>
I have stm32 SAI and i2s drivers, the driver of the cs42l51 chip, the audio-graph sound card driver, and everything is set to okay by default anyway in the device tree… so what did I miss
c4017w__ has joined #openocd
c4017w_ has quit [Ping timeout: 256 seconds]
<PaulFertser>
Xogium: does "aplay -l" show any non-dummy devices?
<Xogium>
PaulFertser: nop. Just the null device
<Xogium>
PaulFertser: I'm comparing my .config with the st one again ;)
<PaulFertser>
Xogium: as another datapoint, modules that are loaded on my netbook: snd_soc_tegra_machine snd_soc_tegra_utils snd_soc_alc5632 snd_soc_tegra20_i2s snd_soc_tegra_pcm
<Xogium>
I think it's clear you have a tegra ;)
<Xogium>
:D
<PaulFertser>
Tegra2, yes
<Xogium>
PaulFertser: how's that working out for you ?
<PaulFertser>
Xogium: 512 MiB RAM is quite limiting these days. Also, the LVDS cable between the display and the motherboard is damaged and I can't fix it or buy new replacement, so the screen flickers like mad and I can only use it with external HDMI display now.
<PaulFertser>
Xogium: that said, I used it for many year happily before that. Even though suspend to RAM never worked.
<Xogium>
damn poor display
<Xogium>
and yep I agree on the 512 mb of ram…
<PaulFertser>
Also, current Firefox is impossible to build without NEON (some FPU extensions) and this old Tegra2 lacks it, so of modern web-browsers only chromium can work.
<Xogium>
for years I ran with a pc that had only 2 gb of ram, and that was already very very limiting. I needed to use a desktop yet many of them are not usable with a screen reader so basically my only 2 choices back then were gnome 3 or mate
<Xogium>
both of which are heavy, then you add the screen reader and web browser on top… I often ran out of ram and lagged like insane due to swa
<Xogium>
*swap
<Xogium>
there's only 5 usable desktop these days, of which one is dead far as I know, and one other must be manually added in the autostart.desktop of the screen reader: gnome, mate, cinamon, unity and lxde
<Xogium>
PaulFertser: you mean, in my own dmesg or in the st one ?
<PaulFertser>
Xogium: in both
<Xogium>
I took dmesg about 5 minutes after the board powered up for the st image, and 40 minutes on mine
<Xogium>
even the modules for alsa are loaded I can see them in lsmod
<PaulFertser>
Hm, I see it's not in my kernel either, probably the debug level was reduced.
<Xogium>
ah yeah the probably don't print that if you use quiet
<Xogium>
but… still
<PaulFertser>
Xogium: do you have /sys/kernel/debug/asoc ?
<Xogium>
the drivers do get loaded, surely it must mean that it detect the hardware ?
<Xogium>
or does it just blindly load any modules it find ?
<PaulFertser>
Not sure how yocto integrates alsa.
<Xogium>
on the st kernel it is also all loaded as modules
<Xogium>
I tripple checked that everything is enabled in my cevice tree just in case and it definitely is, since it is identical to the one st had in the yocto image
<Xogium>
er device tree
<Xogium>
so that part at least we don't have to worry about
<PaulFertser>
Xogium: so what do you have in /sys/kernel/debug/asoc ?
<Xogium>
I found the issue. As usual it was something very, very stupid ;)
<Xogium>
for whatever totally crazy the fsck reason, the snd_soc_cs42l51 module got loaded automatically. However, the snd_soc_cs42l51_i2c *never* was
<Xogium>
don't ask me why, I don't know
c4017w__ has joined #openocd
c4017w_ has quit [Ping timeout: 250 seconds]
Krazubu has joined #openocd
c4017w_ has joined #openocd
c4017w__ has quit [Ping timeout: 256 seconds]
c4017w__ has joined #openocd
c4017w_ has quit [Ping timeout: 260 seconds]
crab_ has joined #openocd
<crab_>
I'm trying to use a JLink EDU mini with OpenOCD on OpenBSD and keep running into the error "No J-Link device found." I also am not seeing the device come up in dmesg so this is likely to do with drivers, but I wanted to know if anyone had gotten a similar set up to work
<crab_>
in order to lead me the right direction
<karlp>
if you don't even see it in dmesg/lsusb, then your problem is well before openocd...
<karlp>
is there a jumper or something to power it or disable it?
<crab_>
you mean on the J-Link? I don't believe so, an LED on it is flashing
<karlp>
are you using a usb cable with data pins? not a shitty trap cable that just does power?
<crab_>
ah I didn't think to check that, I think that's it
<karlp>
(if that's the case, cut the cable right now, so it never catches you again)
<karlp>
so fucked,
crab_ has quit [Quit: Lost terminal]
<karlp>
my wife put one helpfulyl in my desk draw
crab_ has joined #openocd
<crab_>
yeah I didnt realize they even made cables like that
Krazubu has joined #openocd
<crab_>
I do still get the same error, though the device now shows up
<PaulFertser>
crab_: if that's the same if you run it as root
c4017w_ has joined #openocd
<karlp>
ifthe device shows up, yes, next step is permissions on the device :)
<crab_>
as root it's "error connecting DP: cannot read IDR"
c4017w__ has quit [Ping timeout: 250 seconds]
<karlp>
ok, now you're at the target level :)
<crab_>
progress, hurrah
<karlp>
so. what have you got, what's wired where, is _that_ powered, is any of this known to work at all?
Krazubu has quit [Quit: My Mac Pro has gone to sleep. ZZZzzz…]
<crab_>
all that's going on right now is I have a J-Link EDU Mini plugged into the computer and a pinetime(nRF52832) connected to the J-Link as directed by pine64 and the J-link's documentation, with the pinetime using battery power
<crab_>
so they are hooked up on GND, SWDCLOCK, and SWDIO
<crab_>
the nrf52 does have flash protection im not sure if I need to solve that or if I would be getting a different error
<PaulFertser>
crab_: missing target reference line
<PaulFertser>
Vcc
<PaulFertser>
Should go to the pin 1 of jtag connector
<crab_>
if I do that I should be disconnecting the battery
<PaulFertser>
crab_: why?
<PaulFertser>
crab_: jtag adapter needs a voltage reference from the target
<PaulFertser>
Because different targets have different Vcc voltages.
<PaulFertser>
crab_: jlink doesn't normally supply voltage to the target, and when you use that jump start feature it gives 5 V from pin 19 or something.
<crab_>
It just said that on the pine website, "If you don't disconnect the battery, also don't connect the 3.3V pin from the SWD cable when debugging or updating firmware."
<PaulFertser>
crab_: you do not have an "SWD cable", you have a proper jlink debugger, right?
<crab_>
yes
<crab_>
I just didn't know what an SWD cable was and assumed it applied
<PaulFertser>
crab_: this applies to some shitty stlink clones I guess
<crab_>
I'm pretty certain the wiring is all correct now and still getting same error
<crab_>
I hooked up the VTREF and the 3.3V
<PaulFertser>
crab_: please show full output via some pastebin