mmind00 changed the topic of #linux-rockchip to: Rockchip development discussion | public log at https://libera.irclog.whitequark.org/linux-rockchip
stikonas has quit [Remote host closed the connection]
vagrantc has quit [Ping timeout: 265 seconds]
smaeul_ is now known as smaeul
System_Error has quit [Remote host closed the connection]
System_Error has joined #linux-rockchip
HackerBikepacker has quit [Quit: No Ping reply in 180 seconds.]
mriesch has quit [Remote host closed the connection]
HackerBikepacker has joined #linux-rockchip
mriesch has joined #linux-rockchip
Daanct12 has joined #linux-rockchip
dustinm`_ has quit [Ping timeout: 252 seconds]
dustinm` has joined #linux-rockchip
vagrantc has joined #linux-rockchip
vagrantc has quit [Ping timeout: 276 seconds]
System_Error has quit [Remote host closed the connection]
System_Error has joined #linux-rockchip
System_Error has quit [Remote host closed the connection]
System_Error has joined #linux-rockchip
naoki has joined #linux-rockchip
cbeznea_ has joined #linux-rockchip
mriesch has quit [Remote host closed the connection]
HackerBikepacker has quit [Remote host closed the connection]
HackerBikepacker has joined #linux-rockchip
mriesch has joined #linux-rockchip
raster has joined #linux-rockchip
mripard has joined #linux-rockchip
warpme has joined #linux-rockchip
ldevulder has joined #linux-rockchip
<warpme> detlevc : i see initial ffmpeg ext for sps/rps. nice!. It is for ffmpeg7.0. I''m using in mine myth/kodi/mpv ffpmeg7.1. Direct port your sps/rps/ ext (prepared for ffmpg7.0) to ffmpeg7.1 not works due diffs between 7.0 and 7.1. Is it possible to get ext for sps/rps code for ffmpeg7.1? This will allow me to easily test and report how it goes....
ldevulder has quit [Quit: Leaving]
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
warpme has joined #linux-rockchip
<mmind00> CounterPillow: in your rock-4d audio-enable patchset ... patch4 (hdmi audio) should work independently, right?
<CounterPillow> yes
<mmind00> CounterPillow: great, so I'll pick this one first, because the rest needs the input maintainer
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
warpme has joined #linux-rockchip
<diederik> is 'fastboot' (in u-boot) needed for MASKROM to work?
<mmind00> diederik: I wouldn't think so ... i.e maskrom is meant to allow writing software to an "empty" device
<mmind00> diederik: so pushing any maskrom button does that directly
<diederik> mmind00: makes sense, thanks :)
<mmind00> diederik: though part of me (possibly wrongly) remembers something about some "reboot to maskrom" thing ... but I could be wrong
<diederik> yeah, from what I read (which doesn't automatically mean I also understand it), there seem to be at least some similarities
<diederik> context: I'm trying to figure out how to make the maskrom functionality work on my NanoPi R5S ... and not having much success
<diederik> (and when I actually understand how to make it work, try to 'convert' PineNote's u-boot to be based on upstream's u-boot)
<mmind00> diederik: of course finding out how to trigger maskrom mode externally is somewhat important for bootloader work, because if something happens, that is the only way to fix a broken u-boot
* mmind00 was so happy to see that qnap left the maskrom switch as jumper-header on the ts433 board
<a3f> From my limited exposure to Rockchip boards, maskrom buttons were not really talking to the maskron but were just shorting eMMC clock or the like, so Maskrom falls back into well maskrom mode
<diederik> yeah. That's why I want to figure it out on the R5S (next to wanting it there too) as it's easy to recover from that if I fsck up. That's an entirely diffferent story for the PineNote
<a3f> I haven't followed what your issue is, but if you can upload something initially and then can't flash it, you might need to take your finger (or jumper cable) off the maskrom pins
<mmind00> a3f: correct ... though at least on rk3588 that was not the case anymore :-)
<mmind00> but everything before that
<a3f> mmind00, oh, interesting. But the PineNote is RK3566 it seems like?
darfo_ has joined #linux-rockchip
<diederik> I have a vague memory about bootloader 'protocol' version 2, which is used in rk356x/rk3576/rk3588, but I don't know if and how v2 is different.
<diederik> PineNote is indeed rk3566
<mmind00> a3f: probably ... on the rk3588 the maskrom buttons seem to end in the saradc
<mmind00> so the bootrom seems to handle boot media selection itself in some way
darfo has quit [Ping timeout: 260 seconds]
<a3f> diederik, what problem are you running into in particular?
<diederik> a3f: I enabled several options, but when pressing the maskrom button I doesn't go into maskrom mode, it just keeps booting
<a3f> diederik, booting from what medium?
<diederik> I'm currently using an SD-card, but I don't think that matters?
<a3f> diederik, it matters if the maskrom button shorts the eMMC clock signal, because maskrom will just boot from SD ;)
<a3f> you need to take out the SD-Card
<diederik> I'll try again, but I think I've tried that as well
naoki has quit [Quit: naoki]
<diederik> This is what I have thus far: https://git.sr.ht/~diederik/u-boot/log/nanopi-r5s-maskrom
<robmur01> beware that the "recovery" button on many devices is just an ADC key that signals the BSP U-Boot go into "rockusb" mode, which is functionally similar but not the same as the actual boot ROM
<a3f> robmur01, why don't they drop down to maskrom instead? at least on rk356x, there is a pmugrf register to instruct the maskrom to do that
<robmur01> a true "maskrom" button physically disables the boot devices so the ROM can't see them
<diederik> that's another issue I'm indeed running into. Some use 'recovery' while others use 'maskrom' so I thought they were the same thing ... and then the Rock 5B has both ...
<diederik> and I haven't been able to find documentation which explains how it really works (which would hopefully allow me to figure out what I'm doing wrong)
<a3f> diederik, does u-boot notice the button being pressed?
<robmur01> a3f: maybe the newer SoCs might do that - all of my experience is from the RK3288/RK3399 era - but either way it still relies on bootloader code to read the key and do the thing
<diederik> a3f: I haven't noticed that it did notice it
<a3f> I'd suggest adding some printfs in the relevant rockusb code in u-boot and see if a) it's loaded/probed b) the button is sampled
<a3f> If it turns out that the button is read, but rockusb in u-boot behaves strangely, you can try writing the magic value for get me into maskrom mode into the pmugrf and reboot. Context: https://github.com/barebox/barebox/blob/master/arch/arm/dts/rk356x.dtsi#L70
<robmur01> Historical context: https://opensource.rock-chips.com/wiki_Rockusb
<diederik> when I don't press the maskrom button, it boots up and then seems to be in a loop to try pxe. When I do press the maskrom button and then plug the power in ... nothing happens (at least I see nothing on serial)
<robmur01> That "Miniloader Rockusb mode" was the devious annoying one IIRC :)
<mmind00> diederik: looking at the nanopi r5s schematics ... it shows something called "mask_emmc"
<diederik> yep ... very close to the NC for the reset button ;)
<mmind00> though it also touches emmc_d0, not the clk line as "most" boards do?
<robmur01> diederik: "nothing happens" might be the correct behaviour - the ROM is silent on the UART, you need to look for it on the USB OTG port
<a3f> mmind00, the clk part was a guess. I didn't recall the specifics ^^
<diederik> mmind00: and that leads to GPIO1_B4 ...
<mmind00> a3f: parts of me do remember it being clk ... but me and memory don't match ;-)
<mmind00> diederik: the nanopi r5s wiki just says "Disconnect the power from NanoPi-R5S, hold down the MASK button, connect the power, and release the button after 4 seconds."
<diederik> yep. So I must be missing something. One of the things I found in FriendlyElec's uboot-rockchip was the fastboot stuff, which is basically where my question came from
<diederik> robmur01: good suggestion :) ... but I'm still not seeing the maskrom usb device ("No devices in rockusb mode found")
<mmind00> diederik: is your usb-a-a cable connected to the correct usb port?
<diederik> yep
<diederik> but let me try it on my laptop as well. I regularly had problems with the PineNote in maskrom mode on my PC, but not with my laptop.
<diederik> LOL I see a Fuzhou Rockchip ... device with lsusb :-O \o/
<mmind00> diederik: also, is it the type-c port, or one of the a ports? ... at least with type-c ports I remember having orientation problems on some boards
<diederik> on the R5S, there's only 1 type-c port and that is for power, thus the type-a port is needed for maskrom mode
<diederik> and after 'boot'-ing the spl_loader, ``rkdeveloptool test-device`` returns "Test Device OK" :-D
unkraut has quit [Remote host closed the connection]
<diederik> on my PC the type-c port sometimes gives issues (resolved with a reboot), but I've never had a problem with my type-a ports ... until maskrom came into play
unkraut has joined #linux-rockchip
<diederik> a3f: thanks for your suggestions as well :-)
<diederik> one of the issues I run into is that I don't (really) understand U-Boot (and MASKROM), so it's quite difficult for me to figure out what and where things aren't working
<diederik> I was wondering why I can go into MASKROM mode on my PineNote while it has a normally working system ... but that could very well be that it only uses eMMC, so using the SD-card may in fact be the crucial factor why my tests failed
manawyrm has quit [Quit: Read error: 2.99792458 x 10^8 meters/second (Excessive speed of light)]
manawyrm has joined #linux-rockchip
<diederik> plugging the other end of the cable in a Q64-A also works ...
ungeskriptet has quit [Read error: Connection reset by peer]
ungeskriptet has joined #linux-rockchip
manawyrm has quit [Quit: Read error: 2.99792458 x 10^8 meters/second (Excessive speed of light)]
manawyrm has joined #linux-rockchip
ungeskriptet has quit [Ping timeout: 276 seconds]
ungeskriptet has joined #linux-rockchip
<diederik> also works when plugged into a RockPro64 ... and it also works if I plug it in my other usb-a port on my PC ... :-O
erikbeck has joined #linux-rockchip
erikbeck has quit [Changing host]
erikbeck has joined #linux-rockchip
erikbeck is now known as tahomasoft
tahomasoft is now known as TahomaSoft
<a3f> diederik, A-A cables aren't allowed by the spec for a reason, you can fry stuff if vbus is driven from both ends. You may want to disconnect the vbus line (haven't done so with a rockchip soc in particular, not sure the maskrom requires vbus to be there)
<detlevc> warpme: It is based on 7.1, with the v4l2-requests patches from minimyth2 (https://github.com/warpme/minimyth2/tree/master/script/lib/ffmpeg7.1/), but still in very early stages: It compiles and doesn't fail or crash, but still won't work in a lot of situations, I only guessed some fields and didn't check values yet
<detlevc> warpme: Actually, I haven't pushed the 7.1 version yet haha
<detlevc> sorry, coffee didn't hit yet
<diederik> a3f: I have no idea how I'd disconnect a/the vbus line. And until just now, I hadn't managed to get it to work with a USB-A-to-C cable ... but it just succeeded on the RockPro64's USB-C port
<a3f> diederik, you splice up the cable and cut the vbus wire, or use something like https://shop.linux-automation.com/lxa_tools_00033_en
<diederik> yeah, I'm not going to do that ;-)
<detlevc> warpme: you can use v4l2-request-ext-sps-rps-n7.1
<detlevc> but don't expect miracles yet
<diederik> I really don't understand any of this. I've tried it again with a USB-A-to-C cable to my laptop and it doesn't work. I've only had it work (once?) on the RockPro64 ... which I actually find funny/interesting as DTB validation tells me it's missing a required property/node on usb-c: connector
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
raster has quit [Quit: Gettin' stinky!]
<diederik> (something different) on a rk3576 device, do ppl see this kernel warning: "rockchip-thermal fec00000.tsadc: Missing rockchip,grf property" ?
warpme has joined #linux-rockchip
Daanct12 has quit [Quit: WeeChat 4.6.3]
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
warpme_ has joined #linux-rockchip
<CounterPillow> yes, it's just the driver being dumb
<CounterPillow> it shouldn't print that warning for the SoCs that don't need it, but adding the logic for that means extending the per-SoC variant stuff with even more stuff
warpme_ has quit [Quit: My MacBook Air has gone to sleep. ZZZzzz…]
warpme_ has joined #linux-rockchip
<warpme_> detlevc: nice work. now all 13 hevc samples i'm using for testing are: decoding with v4l2, no more iommu errors in demsg for 5 failing samples - only visual defects on samples which are failing. tested on 3566, 3576 ad 3588.
warpme_ has quit [Quit: My MacBook Air has gone to sleep. ZZZzzz…]
<diederik> thanks :) And I agree. It just checks if the property is there, whether it's used or not, and prints a warning if it's not present
<diederik> and AFAICT it should be required for several versions and not be present at all for others
dsimic has quit [Ping timeout: 276 seconds]
dsimic has joined #linux-rockchip
warpme_ has joined #linux-rockchip
wens has quit [Ping timeout: 240 seconds]
vagrantc has joined #linux-rockchip
warpme has joined #linux-rockchip
<detlevc> warpme: Cool, I'll check the data later, the parsing of the source file is a bit different than gstreamer, so I have to make it match
warpme_ has quit [Quit: My MacBook Air has gone to sleep. ZZZzzz…]
raster has joined #linux-rockchip
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
warpme_ has joined #linux-rockchip
<diederik> looks like my u-boot changes didn't have an effect at all :-/ With an older u-boot version the maskrom button works too ...
wens has joined #linux-rockchip
warpme_ has quit [Quit: My MacBook Air has gone to sleep. ZZZzzz…]
stikonas has joined #linux-rockchip
warpme_ has joined #linux-rockchip
raster has quit [Quit: Gettin' stinky!]
warpme has joined #linux-rockchip
warpme_ has quit [Quit: My MacBook Air has gone to sleep. ZZZzzz…]
raster has joined #linux-rockchip
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
warpme has joined #linux-rockchip
warpme_ has joined #linux-rockchip
warpme has quit [Ping timeout: 245 seconds]
warpme has joined #linux-rockchip
warpme_ has quit [Quit: My MacBook Air has gone to sleep. ZZZzzz…]
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
warpme_ has joined #linux-rockchip
ungeskriptet has quit [Remote host closed the connection]
ungeskriptet has joined #linux-rockchip
cbeznea_ has quit [Ping timeout: 260 seconds]
<Ermine> I assume that RK3288 is well supported upstream?
warpme_ has quit [Quit: My MacBook Air has gone to sleep. ZZZzzz…]
Ermine has quit [Ping timeout: 260 seconds]
Ermine has joined #linux-rockchip
erikbeck has joined #linux-rockchip
erikbeck has quit [Changing host]
erikbeck has joined #linux-rockchip
TahomaSoft has quit [Ping timeout: 260 seconds]
erikbeck has quit [Read error: Connection reset by peer]
erikbeck has joined #linux-rockchip
erikbeck has quit [Ping timeout: 260 seconds]
raster has quit [Quit: Gettin' stinky!]
vagrantc has quit [Quit: leaving]
System_Error has quit [Read error: Connection reset by peer]
stikonas has quit [Quit: Konversation terminated!]
System_Error has joined #linux-rockchip