Ukhellfire

Ah OK! Would be interesting to see your results! If this is stock armbian, rsb should work! Do you have repos for your configs? Or is it all local?

Was this using the image I just uploaded with orangepi uboot? Or was this one you built? This is good! It means we're getting somewhere, it means uboot makes no difference. Possibly kernel then!

So apparently stopping isn't in my remit. I've been thinking/playing uboot. I want to experiment... If anyone would be so kind to help me? @sekil @Kamileon @orangepifan @Rockford the Roe?? Basically I'm compiling 2 different images. One with orangepis stock uboot, and armbians kernel etc. Then I'll be compiling a second one, with armbians uboot, and orangepis 5.16 kernel and armbian. This way I will be able to narrow down to whether this is actually a uboot or a kernel issue. My money is on uboot... But you never know... Anyway, here's the link for the first image. This has armbians kernel, with orangepis uboot. https://drive.google.com/file/d/1NAFxJAj9CgHNkrPICbQIKsLXZhutQbCo/view?usp=drivesdk Thanks in advance guys! Look forward to the feedback!

Ah well ill stop where I am then! Haha! I think I'll build that to be honest. And then in the background keep trying out armbian. I'm just annoyed it turned into such a task! Theoretically it should be fairly straightforward. I bet any money it's one tiny line somewhere that needs changing. I can feel it! Haha! Might have to buy a second board in the near future just for developing! Haha!

So I've done another build for the opi3 lts, done with early console turned on, and one for the opi3. I will try booting these shortly, maybe tonight. Been a bit tight on time last night and tonight. I've uploaded the opi3-lts one here: https://drive.google.com/file/d/1s7BKzNnWFvrHC35w4oORbrkzmeos7jkl/view?usp=drivesdk Just incase anyone wants to try it. It's had that patch mentioned above removed. I have no idea if it's even going to do anything. I haven't tested yet. I doubt it though. As soon as I burn it to card and boot it, I'll post up logs and everything too. We will get to the bottom of this! Haha!

It should be asking you to set a root password? This is the armbian setup at the beginning, before you log in...

oh ok thank you! ill do this and get back to you... Found this: https://github.com/armbian/build/commit/6a5363370318c15c25bdee534a61672e6d9ca304 Now orange pi have removed half of this patch. And the commit lightly touches on exactly what we're seeing the the regulators issues...

How do I do that? Early printtk?

This is what makes me think it's possibly voltage related. Don't know if this is possible. But I seem to be getting further than anyone else. And that's the only thing that's different. Although saying that, the orangepi image works, but armbian doesn't. It has to be an armbian codebase issue. I wonder if it's a "build" issue rather than a uboot/kernel issue? 🤔

i dont know who maintains it? heres the dmesg i was able to get. https://drive.google.com/file/d/1GHGrtHVZzMLQ0o1h_B7US2EB40pTL-OU/view?usp=sharing Im pretty certain its nothing were doing wrong. like you said, i think its just buggy. im wondering if porting a different device would work? dont think anything else is similar though. and im pretty certain its about the regulator banks. its the same error every image we try... vcc-pc-supply & vcc-pd-supply, and not finding vcc-pf-supply. vcc-pf isnt even needed for this board! its not listed in allwinners datasheets or anything! As you can see my vcc-pc and vcc-pd regulators are found and seen! But the at the bottom its throws a regulator not found vcc-pf. I don't think that's even defined for h6! It's pulling something else from config wise from somewhere else...

well ive just booted it... the op13 image. ive taken a dmesg, now just about to get it off the card and upload it! pretty sure i saw regulator issues?

I'll do that when I get home. So basically just build for opi3, and boot that. Then if it works, start porting that across to opi3-lts? Which is what I was going to do. Then decided to use orangepis files from their repos instead. Damn. Wish I'd done it from the beginning now! And ill run without any userpatches what so ever? Just armbians stock patches? Run on every build? How long you available for testing?

Basically start again! Lol! OK I'll do that. Thing is though, the dts file I'm using, is the same as the opi3 one. But I'll give it a go. I added a couple of bits into the bootargs, but other than that, opi3 and opi3lts dts file are the same! They are both exactly the same on orangepi repo too. I think think it may be a build issue to be honest. Not sure though...

Yeah they told me that the driver didn't exist! Now all of a sudden it does. Like you say, strange! Ah OK. I haven't looked into it much. And I didn't try connecting anything when i had it working. Have you tried the hciattach methods on orangepis repos?

I haven't tried this yet. From my original understanding, it's never been working. But I'm not sure on what they've done in the latest months. The seem to enable ac200 audio or something? https://github.com/orangepi-xunlong/linux-orangepi/commit/3b75d984852c04151e9bba741473d3810ab72753 I believe the Bluetooth crash is due to the macadress. https://github.com/orangepi-xunlong/linux-orangepi/commit/d15ff3cb548f6ad056a881720cb29860226a2ab3

OK thanks. Will be interesting in what you find! If you use my build repo, and then the patches I gave you, it should fully build without errors or anything. The you should be at the same place I am...

Yes that's right. Then my patches and all the other patches for sunxi get applied. My patches are from the orange pi 5.16 bring up. Which funnily enough, was mainline, and orangepi applied armbians patches to it. https://github.com/orangepi-xunlong/linux-orangepi/commit/00fef0e5e3dea1a3dd45fe35a6da209d005595e6

I'm patching the kernel that armbian downloads. The emmc patch I'd there. I had a different repo. I'll zip up my patches and link you. https://drive.google.com/file/d/1oit5pTA2J68mjmsQqAnoJQIhwC-R071o/view?usp=drivesdk They are my kernel and uboot userpatches.

I don't have a problem at all. If you look at my repos, I've done it. And as you can see from my dmesg, it's working! I have working ethernet, wifi, haven't checked emmc though... Dmesg here: https://drive.google.com/file/d/1LQ5qgTZBLdhauLeqD3OArM8ci2uzLdnb/view?usp=drivesdk

Again, I could boot, but noone else I don't believe?

They also have a 5.16 branch. https://github.com/orangepi-xunlong/linux-orangepi/tree/orange-pi-5.16-sunxi64 https://github.com/orangepi-xunlong/linux-orangepi/commit/6cb6eb3553db63e80b133a13f3868f5ca8d760ab#commitcomment-69513212 I just wanted to get armbian working. I don't see any reason why it shouldn't??

Thanks! That's alot to read through! But it could help! OK I shall do this. I shall do this too! Haha! No in fact, I'm trying to bring up the board as a new board. I've taken orangepis config files, and put them across to armbian. I'll link my repos Build: https://github.com/afaulkner420/build Kernel: https://github.com/afaulkner420/linux-5.15-opi3-lts Uboot: https://github.com/afaulkner420/uboot This is my progress so far... feel free to play! Haha!

I suppose it could do. I'm really at a loss here... and without being able to have the same issues this end, I'm stuffed! Haha!

OK thanks. I wanted to try and replicate this. But still booting this end. I really don't know what to try next? It doesn't make any sense to me? I'm now using the exact setup and files orangepi uses just with armbian. Unless orangepi have modified their kernel in someway or something. All dts files seem good. Even all the regulators and everything. Does anyone know anyone that can help with this?

OK thank you. Just now how the hell do I start Debugging this? Random question, but do you have plugged in when you boot? And to what ports?