04:00 <tuxd3v> hello all \o

04:00 <tuxd3v> I came with a problem..

04:01 <tuxd3v> cannot build ATF mailine for rk3399

04:01 <tuxd3v> it gives me a error

04:01 <tuxd3v> make CROSS_COMPILE=aarch64-elf- PLAT=rk3399 DEBUG=0 clean

04:02 <tuxd3v> make CROSS_COMPILE=aarch64-elf- PLAT=rk3399 DEBUG=0 bl31 -j4

04:02 <tuxd3v> make[1]: arm-none-eabi-gcc: Command not found

04:02 <tuxd3v> what??

04:03 <tuxd3v> I am trying to compile a64 bits spl..

04:03 <tuxd3v> does any one know how to do that?

04:03 <tuxd3v> thanks in advance..

04:42 <anarsoul> tuxd3v: "CROSS_COMPILE=aarch64-linux-gnu- make PLAT=rk3399" works for me

04:51 <vagrantc> tuxd3v: you also need to install the baremetal compiler

04:54 <vagrantc> M0_CROSS_COMPILE=arm-none-...

07:46 <wens> probably time to get a pinebook pro?

12:53 <RK3308-CC> Has anyone managed to use OCD with RK3308?

12:54 <RK3308-CC> I can connect and use it over telnet, but as soon as I use GDB, simple things like "set var $pc = ...." fails hard

13:13 <RK3308-CC> turns out GDB sends a request to read memory at $pc-4 for whatever reason, and that happens to be a non existing address -> the target crashes

15:32 <micken> getting crazy (RK3399) setting fc_dbgforce -> no effect skipping that and set vop_bg -> no effect, set up win0 framebuffer -> no effect

15:46 <tuxd3v> vagrantc: thanks, the Idea I got is that it compiled some code for a ARM cortex-M0..

15:46 <tuxd3v> arm-none-eabi-gcc -g -mcpu=cortex-m0 -mthumb -Wall -O3 -nostdlib -mfloat-abi=soft -ffunction-sections -fdata-sections -fomit-frame-pointer -fno-common -Iinclude/ -I../../include/shared/ -MMD -MT /home/tuxd3v/Desktop/H6/edev1/BootLoaders/RockPi4A_arm-trusted-firmware/build/rk3399/release/m0/dram.o -c src/dram.c -o /home/tuxd3v/Desktop/H6/edev1/BootLoaders/RockPi4A_arm-trusted-firmware/build/rk3399/release/m0/dram.o

15:59 <tuxd3v> vagrantc: it seems that I needed that flag ;)

15:59 <tuxd3v> thanks:

16:00 <tuxd3v> "make CROSS_COMPILE=aarch64-elf- M0_CROSS_COMPILE=arm-eabi- PLAT=rk3399 DEBUG=0" did the trick :)

21:14 <fALSO> yo

21:16 <micken> anarsoul: I soolved my problem, I had hdcp enabled should have been off, My display in riscos works now!

21:16 <micken> anarsoul: I have no idea what the problem is in uboot

21:16 <anarsoul> :(

21:16 <anarsoul> maybe it also has hdcp enabled?

21:16 <micken> might be

21:17 <micken> but that cant explain probe errors

21:28 <anarsoul> it probes fine for me

21:28 <anarsoul> how do I check whether hdcp is enabled?

21:31 <micken> check FF950004

21:31 <micken> it is bit 6 and 7

21:32 <micken> (reg mc_clkdis)

21:33 <micken> 0 is enabled

21:38 <anarsoul> OK, thanks

21:38 <anarsoul> can it be changed on the fly?

21:38 <micken> yes

21:39 <micken> I wrote 0xc0

21:39 <anarsoul> great, will check tonight

21:39 <micken> and it started to work

21:39 <micken> right away

21:42 <sphalerite> Anyone here who knows things about gru chromebooks and can help me remove the firmware write protection? I've gone through https://wiki.mrchromebox.tech/Firmware_Write_Protect for my gru-bob and AFAIU done everything to have WP disabled, yet crossystem still reports wpsw_boot and wpsw_cur as 1

21:42 <sphalerite> hanetzer: maybe you have a moment? O:)

21:44 <sphalerite> I've even tried disconnecting the battery, although AFAIU it shouldn't be necessary for this.

22:09 <sphalerite> I've asked at https://www.reddit.com/r/chromeos/comments/drp3ya/removing_firmware_write_protection_on_asus/ as well in case anyone is able and willing to help :)

22:13 <micken> anarsoul: http://www.update.uu.se/~micken/rockpro64.jpg

22:13 <anarsoul> great

22:14 <anarsoul> I'll hope I get it working on rockpro64

22:14 <anarsoul> and then port it to pbp

22:14 <anarsoul> so I can get display output in u-boot

22:14 <micken> yea

22:14 <micken> differnt phy

22:14 <anarsoul> (where's this courier with my PBP...)

22:16 <micken> What display plug is used in pbp?

22:16 <micken> lvds ?

22:16 <anarsoul> eDP

22:16 <micken> ah

22:16 <anarsoul> should be easy enough

22:16 <micken> I no nothing about edp

22:16 <anarsoul> (I hope)

23:12 <micken> anarsoul: the things I did was 1) set vpll to pixelclock 2) set vop0_aclk to gpll with divider I dumped from running linux

23:12 <micken> anarsoul: and disable hdcp clock

23:13 <anarsoul> micken: I see, aclk is not supported atm in u-boot

23:14 <micken> anarsoul: should be easy to add

23:14 <anarsoul> probably

23:14 <anarsoul> I haven't looked into that yet

23:46 <hanetzer> sphalerite: yeah

23:48 <hanetzer> sphalerite: I've been at class but I'm free now.