lanefu changed the topic of #armbian-rockchip to: Armbian - Linux for ARM development boards | Rockchip SoC | www.armbian.com | This channel is relayed to the equivalent Discord channel | this channel is logged
DC-IRC has quit [Remote host closed the connection]
DC-IRC has joined #armbian-rockchip
<DC-IRC> <kingonename> So I'm about to push the image now. Could someone link the best rkdevtool version for windows, and the loader file for this particular image? I tried with the ones I have 2.96 devtool, and spi_loader_v1.09.111. it finished without error, but it's not booting up after
<DC-IRC> <kingonename> Also, just some confirmation. I have the 2023 model, which is the 4G model sans the 4G module—so should I use the R58X image, or the r58x-4g image?
<DC-IRC> <kingonename> @monkablyat @nicod_sbc I told you I'd keep you apprised... and I think I bricked it 😥😬
<DC-IRC> <kingonename> Something has happened, I don't know if I used the wrong spi file or what, but it almost seems like this thing is now bricked.
<DC-IRC> <kingonename> I flashed successfully according to the rkdevtool, but upon reboot, the wifi LED remains solid, and it doesn't boot.
<DC-IRC> <kingonename> After trying to put it back in loader mode, I get no response, and my PC doesn't register the device.
<DC-IRC> <kingonename> I'm kind of panicking lol. Is there a factory reset option or something I can try?
_whitelogger has joined #armbian-rockchip
<DC-IRC> <Tonymac32> the device tree compiler has decided to be big mad and I'm not sure why.
<DC-IRC> <Tonymac32> arch/arm64/boot/dts/rockchip/rk3399-roc-pc.dtsi:910.29-912.5: ERROR (phandle_references): /syscon@ff770000/usb2phy@e460/port/endpoint: Reference to non-existent node or label "usbc1_hs"
<DC-IRC> <Tonymac32>
<DC-IRC> <Tonymac32> arch/arm64/boot/dts/rockchip/rk3399-roc-pc.dtsi:854.29-856.5: ERROR (phandle_references): /phy@ff800000/dp-port/port/endpoint: Reference to non-existent node or label "usbc1_dp"
<DC-IRC> <Tonymac32>
<DC-IRC> <Tonymac32> arch/arm64/boot/dts/rockchip/rk3399-roc-pc.dtsi:862.29-864.5: ERROR (phandle_references): /phy@ff800000/usb3-port/port/endpoint: Reference to non-existent node or label "usbc1_ss"
<DC-IRC> <Tonymac32> however, those nodes exist
<DC-IRC> <diegdoming> Does anyone's Orange Pi 5 Nvme port report speeds that are under the specs of PCIe2.0? I seem to just get 100M/s as peak
<DC-IRC> <diegdoming> I dont know if it is just the orange pi specs are all wrong or could be something eating all that bandwitdth
<DC-IRC> <diegdoming> All tests were run from a clean install btw
<DC-IRC> <nicod_sbc> @kingonename https://www.youtube.com/watch?v=t8h-cRwwipk&t=2s&ab_channel=NicoD%27sSBCs Version of rkdevtool shouldn't mater if you do it correct. It is the one thing I hate about Meko boards. No sd-card to boot from.
<DC-IRC> <nicod_sbc> @diegdoming Should perform at about 400MB/s if NVMe is ok. 100MB/s seems too slow.
<DC-IRC> <diegdoming> could it be that theres is something else taking the bandwidth? I read that there is people to report that having the Wifi/bluethoot module enabled slow them down
<DC-IRC> <diegdoming> Or something similar?
<DC-IRC> <diegdoming> i am just guessing
<DC-IRC> <nicod_sbc> I don't think so. NVMe and mPCIe are not shared. What drive are you using? Is it cheap chinese knock-off or a real brand? Have you tried it on another device?
<DC-IRC> <tenkawa42> 100MB is too slow even for a bifurcated link (which I have seen.. those run on a pcix2 around 180mb)
<DC-IRC> <nicod_sbc> I know of cheap chinese drives having these performance. But they're mostly sold as 1TB/2TB/4TB drives while actually only having 64GB chip and no ddr. So you loose all data after 64GB write.
<DC-IRC> <tenkawa42> On the slowest x2 link I have right now (Risc-V highly devel) sbcs.. they are still getting around 300mb with all of my drives right now
<DC-IRC> <tenkawa42> yeah some higher capacity and block size ones run slower but not "that" much slower too
<DC-IRC> <tenkawa42> I guess since these controllers can't run full speed I'm not really getting their full benefit...
<DC-IRC> <diegdoming> i was just trying other things ans changing the kernel seemed to have fixed it, dont know why but either way im happy
<DC-IRC> <kingonename> Thanks for getting back to me @Nico, trying again now
<DC-IRC> <kingonename> @nicod_sbc i shorted it successfully, got it registered on the PC as One MASKROM Device (usually it says Loader)
<DC-IRC> <kingonename> I've tried the following to no avail:
<DC-IRC> <kingonename> Method 1:
<DC-IRC> <kingonename> 1: Navigating to the Download Firmware tool 2.96
<DC-IRC> <kingonename> 2: loading the most recent R58X firmware from your link, and the Armbian spi_loader_v1.08.111.bin
<DC-IRC> <kingonename> 3: checking Write to Address
<DC-IRC> <kingonename> 4: clicking Run
<DC-IRC> <kingonename> Outcome: Download was successful, and R58X reboots and is still stuck on the wifi LED with "No Device Found" in the devtool.
<DC-IRC> <kingonename> Method 2:
<DC-IRC> <kingonename> 1: Navigating to the Download Firmware tool 2.96
<DC-IRC> <kingonename> 2: loading the most recent R58X-4G firmware from your link, and the Armbian spi_loader_v1.08.111.bin
<DC-IRC> <kingonename> 3: checking Write to Address
<DC-IRC> <kingonename> 4: clicking Run
<DC-IRC> <kingonename> Outcome: Download was successful, and R58X reboots and is still stuck on the wifi LED with "No Device Found" in the devtool. (Same outcome)
<DC-IRC> <kingonename> Any thoughts?
<DC-IRC> <nicod_sbc> So it's wifi that's missing that's your problem? I've got no idea why that would be.
<DC-IRC> <monkablyat> think there might be still android vendor u-boot somewhere on his eMMC so erase the eMMC first via rkdevtool before you flash armbian
<DC-IRC> <kingonename> Okay I'll try that, and let you all know. Thanks for the continued support
<DC-IRC> <kingonename> Okay I'm in the rkdevtool. How exactly do I erase the emmc?
<DC-IRC> <kingonename> I'm seeing under advanced Function, a list with eMMC as #2 and I can click it. Then there is an option for "Erase LBA" and "Erase All"
<DC-IRC> <kingonename> I don't want to try anything without confirmation first so as to not make things worse lol
<DC-IRC> <koopahtmaniac> did any one try getting imx219 working on rock 4 with 5.15 kernel or newer?
<DC-IRC> <kingonename> Okay @monkablyat I'm in the rkdevtool. How exactly do I erase the emmc?
<DC-IRC> <nicod_sbc> @kingonename I'm about sure it's all.
<DC-IRC> <kingonename> Okay so I did that, and after a few minutes it says "get flash failed"
<DC-IRC> <kingonename> So then I tried to push the loader and firmware again, but now it says:
<DC-IRC> <kingonename> "Download Boot Fail" and "Note: please check DDR, please reset device and retry"
<DC-IRC> <kingonename> Okay so I did that, and after a few minutes it says "get flashinfo failed"
<DC-IRC> <Tonymac32> No one has hints about my device tree puzzle? 🤣🤣🤣😢
<DC-IRC> <tenkawa42> I missed it
<DC-IRC> <Tonymac32> DTC said "nope, not today"
<DC-IRC> <Tonymac32> Seems to be why these older patches failed in the first place, I don't know what's triggering it now vs before
<DC-IRC> <tenkawa42> @MacKahan are those port definitions global?
<DC-IRC> <tenkawa42> or in each block only
<DC-IRC> <Tonymac32> In 5.15 they worked just fine 😆
<DC-IRC> <tenkawa42> I ask because I was wondering if that was why they might be going into oblivion
<DC-IRC> <tenkawa42> something changed them from a global to private address space?
<DC-IRC> <Tonymac32> I'm not sure DT has private address space
<DC-IRC> <tenkawa42> Yeah neither am I
<DC-IRC> <Tonymac32> I was reading the spec last night 😆
<DC-IRC> <tenkawa42> but I know 5 to 6 did change some things "very" oddly
<DC-IRC> <Tonymac32> Yeah trying to track it down 🤷‍♂️
<DC-IRC> <kingonename> @nicod_sbc Okay so I did that, and after a few minutes it says "get flashinfo failed"
<DC-IRC> <kingonename> @nicod_sbc @monkablyat Okay so I did that, and after a few minutes it says "get flashinfo failed"
<DC-IRC> <kingonename> @monkablyat @nicod_sbc okay, so after trying everything multiple times, I realized that there has been no real change in symptoms since the first time I flashed amazingfate's image... So I flashed the rebornOS image that I got to work (poorly) before.
<DC-IRC> <kingonename> And it booted up without issue.
<DC-IRC> <kingonename> So it's not bricked!
<DC-IRC> <kingonename> But it appears to not like amazing fates image. I'm gonna try an older version from Nico's link now, but do we know why this may have happened? And what I can possibly do to get the most recent version?