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>
<HexC0DE> Hello guys, i am trying to boot Armbian directly from SD CARD. Downloaded latest Armbian_22.08.0-trunk_Rk3318-box_jammy_edge_5.18.10_xfce_desktop.img and extract it on SD CARD using win32diskimager (tried with Etcher too). But when i put the sd card on device and power on, the internal eMMC load the installed inside Android instead of the Armbian. As i remember i use Armbian on same device 1 year ago and was boot from sd card wit
<DC-IRC>
<HexC0DE> Hello guys, i am trying to boot Armbian directly from SD CARD. Downloaded latest Armbian_22.08.0-trunk_Rk3318-box_jammy_edge_5.18.10_xfce_desktop.img and extract it on SD CARD using win32diskimager (tried with Etcher too). But when i put the sd card on device and power on, the internal eMMC load the installed inside Android instead of the Armbian. As i remember i use Armbian on same device 1 year ago and was boot from sd card wit
<DC-IRC>
<Tonymac32> if you're lucky the tv box has a button in it to bypass. Otherwise you need to convince Android to allow the SD boot, or otherwise corrupt the Android boot area
<DC-IRC>
<Tonymac32> unfortunately the TV box folks don't hang out in the discord
<DC-IRC>
<shineworld> Hi all, I'm using latest version for Opi 4 LST and sudo apt-get update or sudo apt update 99% of times freeze:
<DC-IRC>
<shineworld> The ssh console remain in this state forever.
<DC-IRC>
<shineworld> I don't know if its only an issue with Opi 4LTS or happens with other boards.
<DC-IRC>
<shineworld> This when OS run on SD or eMMC.
<DC-IRC>
<shineworld> Any idea about ?
<DC-IRC>
<IgorPec> powering?
<DC-IRC>
<shineworld> 10A industrial power supply with stable +5.00V
<DC-IRC>
<shineworld> Could be however a cable power problem (passive resistance of cable or in USB-C connector)
<DC-IRC>
<shineworld> Um... fan is powered by board pin headers....
<DC-IRC>
<shineworld> bad idea...
<DC-IRC>
<HexC0DE> Thanks for hints.Interesting ,when i try to boot multytool from sd-card ,is booting fine.
<DC-IRC>
<shineworld> YES I've removed fan powering from board Headers and attached to main power
<DC-IRC>
<shineworld> 99% of time are issue of power...
<DC-IRC>
<shineworld> 0.163A are too much of pin headers
<DC-IRC>
<Tonymac32> hmmm maybe it's noise from the fan on the supply, rather than consumption
<DC-IRC>
<Tonymac32> 163 mA seems low to casue any issues
<DC-IRC>
<Tonymac32> although 5V power for anything more powerful than a quad-core A53 is bad design practice, unless a screw terminal header is available. Can you bump that supply to 5.2 V?
<DC-IRC>
<Tonymac32> that will help with voltage sag across the connectors
<DC-IRC>
<shineworld> Mmm.... could be, usually with RPI I attach directly fans to pin headers, but OPi seems a more fragile board
<DC-IRC>
<shineworld> The OPi 4 can be supplied with more than 5.00V ? I don't know that
<DC-IRC>
<Tonymac32> I've never had the problem you describe, but I don't use OPi parts much, if ever
<DC-IRC>
<Tonymac32> stay within the tolerances of the USB input if that's how it's powered
<DC-IRC>
<Tonymac32> there is always a drop across connectors
<DC-IRC>
<shineworld> Was a wrong choice.... to use OP i.
<DC-IRC>
<shineworld> I looked for a RK3399 to have MIPI-CSI2 support but it was a mistake
<DC-IRC>
<shineworld> because none kernel support a working ISC (mentioned in libcamera however).
<DC-IRC>
<Tonymac32> that board has a barrel jack on it
<DC-IRC>
<Tonymac32> yes?
<DC-IRC>
<shineworld> Yes
<DC-IRC>
<Tonymac32> far better power connection than the type c connector
<DC-IRC>
<Tonymac32> I used a pi camera with my tinkerboard on the vendor kernel no problem, the RK3399 is similar IP
<DC-IRC>
<Tonymac32> we even got crappy video out of the mainline drivers in 2018
<DC-IRC>
<Tonymac32> I would hope by now the mainline support for the CSI is good enough
<DC-IRC>
<Tonymac32> was never of much interest to me so I haven't messed with it since
<DC-IRC>
<shineworld> At moment I use 10A 5.00V (I can trimmer it)
<DC-IRC>
<Tonymac32> yeah I'm not doubting the supply, I'm doubting the interconnects and the board side traces leading from the type C connector
<DC-IRC>
<shineworld> I've either way (the original OPi 4 power supply 4A) that I use rarely because I don't trust on it.
<DC-IRC>
<shineworld> I will design a custom power-supply switching module for end-product.
<DC-IRC>
<shineworld> I'm doing an industrial IP camera with OPi, as substitute of an already made based on RPI 4
<DC-IRC>
<shineworld> Asus tinkerboard could be a good choice for CSI-2 support ?
<DC-IRC>
<Tonymac32> it's beena solid 4-5 years since I tried 😄
<DC-IRC>
<Tonymac32> So I can't really speak to it confidently
<DC-IRC>
<Tonymac32> those RPi cameras are rubbish with the I2C stuff bundled in, it's easier for me to do low-res stuff with an ESP32 microcontroller 😄
<DC-IRC>
<shineworld> Eh to have more time....
<DC-IRC>
<shineworld> At moment i use 12Mpx MIPI CSI-2 motorized cameras with goes straight on RPI ...
<DC-IRC>
<shineworld> All food ready with few time to get working
<DC-IRC>
<Tonymac32> yeah, basically everything that has a compatible ribbon cable connector is CSI-2, the Pi was lagging the industry badly with their interfaces. Drivers are the question because of backward Pi Foundation practices with hardware (take the DSI for example, it has a microcontroller on board that has to have its own driver)
<DC-IRC>
<Tonymac32> IIRC the Rockchip --> Pi camera pipeline involved severely limiting the Rockchip IP (cutting down lanes and frequency)
<DC-IRC>
<shineworld> Unfortunately, ignorance on my part led to problems galore, starting with the choice of a replacement board for the RPI 4.
<DC-IRC>
<shineworld> In the camera I use libcamera.
<DC-IRC>
<shineworld> When I saw in the libcamera source code that the RK3399 was mentioned, I went out and bought 10 OPi 4 boards, hoping to be able to use it right away, but then I was confronted with the fact that this is not the case, and to this day I don't have a kernel that can run libcamera on an RK3399.
<DC-IRC>
<Tonymac32> likely you need a device tree overlay
<DC-IRC>
<shineworld> And there my ignorance on the subject.
<DC-IRC>
<shineworld> I have been involved in embedded design for at least 30 years, but I have never delved so deeply into the linux world to handle it. We make equipment with proprietary real time firmware and until now I have never thought of switching to Linux to do anything. I need to bang my head against it and start doing the things I need to do with this system.
<DC-IRC>
<Tonymac32> linux gets in the way a lot, there's a lot of moving parts