Putti has quit [Remote host closed the connection]
Putti has joined #linux-sunxi
gaston1980 has quit [Remote host closed the connection]
gaston1980 has joined #linux-sunxi
mayer has quit [Quit: mayer]
coco3431 has joined #linux-sunxi
cnxsoft has joined #linux-sunxi
iyzsong has joined #linux-sunxi
<coco3431>
I've got a Pine Clusterboard and I've been unable to get it to reboot, it just shuts down. It looks like it should just use the watchdog to reboot the sopine. I'm not sure where to even start with as it works perfectly in the baseboard. Is it possible this is a U-Boot or ATF issue? Or is this probably a kernel issue? I've done some kernel debugging
<coco3431>
but mostly related to i2c devices so I'm happy to accept any suggestions of where to start
tuxillo has quit [Ping timeout: 256 seconds]
<gnarface>
coco3431: pine64.org has their own irc server, you might have better luck asking in there
Benjojo has quit [Ping timeout: 246 seconds]
ullbeking has quit [Ping timeout: 240 seconds]
Benjojo has joined #linux-sunxi
suprothunderbolt has joined #linux-sunxi
ullbeking has joined #linux-sunxi
iyzsong has quit [Read error: Connection reset by peer]
iyzsong has joined #linux-sunxi
TheSeven has quit [Ping timeout: 260 seconds]
TheSeven has joined #linux-sunxi
gaston1980 has quit [Quit: Konversation terminated!]
kaspter has quit [Ping timeout: 240 seconds]
kaspter has joined #linux-sunxi
dddddd has quit [Ping timeout: 258 seconds]
JohnDoe_71Rus has joined #linux-sunxi
lurchi_ has joined #linux-sunxi
gediz0x539 has joined #linux-sunxi
lurchi__ has quit [Ping timeout: 240 seconds]
tl_lim has quit [Ping timeout: 260 seconds]
tl_lim has joined #linux-sunxi
camus1 has joined #linux-sunxi
kaspter has quit [Ping timeout: 246 seconds]
camus1 is now known as kaspter
netlynx has joined #linux-sunxi
netlynx has quit [Changing host]
netlynx has joined #linux-sunxi
tl_lim has quit [Read error: Connection reset by peer]
coco3431 has quit [Remote host closed the connection]
kaspter has quit [Read error: Connection reset by peer]
kaspter has joined #linux-sunxi
AneoX has joined #linux-sunxi
kaspter has quit [Ping timeout: 240 seconds]
kaspter has joined #linux-sunxi
vpeter has quit [Ping timeout: 264 seconds]
cmeerw has joined #linux-sunxi
vpeter has joined #linux-sunxi
JohnDoe1 has joined #linux-sunxi
JohnDoe_71Rus has quit [Ping timeout: 264 seconds]
[CONSTANTS] has quit [Quit: "Not dangerous, but surprising."]
arti has quit [Quit: arti]
<damex>
how low power sunxi system could get? looking for something to collect info from sensors and be powered from battery.
[KAZAN] has joined #linux-sunxi
<mru>
how low power are you looking for?
<mru>
for that kind of application something like an stm32 might be better
<damex>
mru: well, stm32 with ultra low power is great but it is not as easy to get compared to using some sunxi machine. i think around 100ma with everything off should be a good start?
arti has joined #linux-sunxi
<damex>
i originally planned to start with rpi zero but then no stock or crazy pricing like 20-50$ for each board and it killed the idea for me
<willmore>
STM32 chips on blue pill boards are easy to find and cheap. ESP8266 board are also very cheap and easy to find--and include wifi. ESP32 similar.
<buZz>
ESP32-S2 looks sooo nice
<damex>
i heard there is lots of fakes
<buZz>
cant wait for availability
<buZz>
there are no fake ESP's
<damex>
'fakes' aka clones that does not work properly
<damex>
buZz: really?
<buZz>
yes
<KotCzarny>
H3 goes down to ~100-150mA
<KotCzarny>
and ~40mA in fake-off
<damex>
thanks, i will research a bit into the esp/stm territory then. 100-150ma for h3 is kinda too much for that purpose.
<KotCzarny>
if you are fine with ~40mA, then you can program ARISC on H3
<damex>
i think 40ma should be fine. even 50
<KotCzarny>
but you will not be able to use arm cores or dram
<KotCzarny>
if you want to stay in that power envelope
<KotCzarny>
and of course you will have to program without operating system
<KotCzarny>
plain c
<smaeul>
KotCzarny: I have A64 down to 31mA in standby (not off), so you can wake up Linux to do work and then immediately go back to sleep
<KotCzarny>
smaeul: nice, thats with arm/dram online?
<smaeul>
lol no
<KotCzarny>
:)
<KotCzarny>
so initializing it everytime?
<smaeul>
no, the dram is in self-refresh
<KotCzarny>
and im calling standby as fake-off
<KotCzarny>
nice about dram
<smaeul>
the difference is that your fake-off has to reboot to recover. that's not standby. standby is when all state is maintained and userspace doesn't notice that anything happened
<KotCzarny>
yeah
<willmore>
There are a lot of STM32F103 clones, but most of them are actually very good chips--if you know how to treat them. It's just people selling them in place of the actual STM32 chips that's the problem.
<damex>
KotCzarny: could it actually be close to 100ma?
<damex>
on h3
<damex>
let's say on some less demanding boards
<KotCzarny>
damex, search armbian forums for power related threads
<buZz>
h3 isnt a board :P just the soc
<smaeul>
I don't have any numbers for H3 boards, but e.g. OrangePi PC2 (H5) is about 67mA in standby
<damex>
smaeul: 67mA is really something. specifically when it is h5 board
<smaeul>
damex: if you want to run off battery power, you'll want a board with a real PMIC, which means something A64-based
<smaeul>
I have a Pinebook sitting on my lap right now using 38mA from the battery, as measured by the PMIC
<damex>
smaeul: i think it has to be battery powered. see no other option for now when you need to keep board atleast 5-10m away from power socket (it does not even mean it is empty for use) or even keep it outside
gaston1980 has quit [Ping timeout: 260 seconds]
<damex>
thanks, i will check what a64 boards could offer
gaston1980 has joined #linux-sunxi
<damex>
maybe i can just go for pine a64 board
<willmore>
The OpiPC (and 2) boards use PMICs.
<willmore>
Actually, don't everything *but* the Zero and One families?
<smaeul>
SY8106A on the PC2 is just a voltage regulator. and not even all AXP PMICs have a battery charger (e.g. AXP805 in H6 boards doesn't)
<willmore>
You want a battery management type PMIC
<willmore>
?
<buZz>
5-10M powercables would be fine
<buZz>
maybe up the voltage a tiny bit
<willmore>
You could run a higher voltage to it and put a step down converter at the device itself.
<willmore>
Then cable losses would be less and not really matter.
<buZz>
yeah, thats smarter
<buZz>
i would just crank the 5V to 6V perhaps
<buZz>
or 5.5
<willmore>
12V.
<buZz>
ah, it runs on 12V?
<willmore>
buZz, you'd put a switching converter at the device itself to make 5V.
<willmore>
So, you could send it anything the DC/DC converter could take.
<willmore>
Probably up to 35V or so depending on the board.
<willmore>
Since the voltage would be higher, the current would be lower and hence the resistive losses in the wire would be less.
<willmore>
I think all of the opi boards use the input 5V directly on the output USB connectors, so that would make feeding the board with anything higher than 5.25V a very bad idea.
<buZz>
willmore: yeah i know the concept, its nicer
<willmore>
But, if you're not using the USB, you could check the schematics and see what else is attached to the input voltage. If it's just the power regulators, they might be able to tolerate higher voltages--say 7V or so.
<willmore>
If I had to mount a board remotely, that's how I'd power it.
<Werner>
nevertheless it might be a good idea to crank up the voltage at the source a bit to compensate voltage drop across wire and connectors.
<willmore>
steal a pair off of the ethernet (100BT) and send the power along that way.
<willmore>
Werner, the risk in that is that the load current will change and hence the voltage at the board will vary a lot.
<willmore>
Highest when off or at idle--which is where you'd expect it to spend most of its time.
<Werner>
Obviously not a good idea without measurement at the target to find a sweet spot ;)
<buZz>
heh, yolo
<willmore>
If even that
andy25225 has quit [Ping timeout: 264 seconds]
andy25225 has joined #linux-sunxi
s3b0 has quit [Quit: Konversation terminated!]
igraltist has quit [Remote host closed the connection]
igraltist has joined #linux-sunxi
<smaeul>
it took me a while to find a battery I could hook up to my Pine A64 board. the board draws 27-28mA in suspend with HDMI disabled
<smaeul>
it's 75mA with HDMI enabled, but I'm assuming you don't need HDMI for collecting sensor data
ganbold_ has quit [Read error: Connection reset by peer]
jonasbits has quit [Ping timeout: 258 seconds]
jonasbits has joined #linux-sunxi
qschulz has quit [Remote host closed the connection]
cmeerw has quit [Ping timeout: 246 seconds]
qschulz has joined #linux-sunxi
zoobab has quit [Ping timeout: 260 seconds]
zoobab has joined #linux-sunxi
jstein has quit [Quit: quit]
ldevulder_ has joined #linux-sunxi
ldevulder__ has quit [Ping timeout: 256 seconds]
Mangy_Dog has quit [Ping timeout: 260 seconds]
Guest38887 has quit [Quit: issued !quit command]
<mirko>
i'm already guessing "no", but just to be sure i'm not overlooking sth.: when using h3/h6 hw video decoding via cedrus, is there any way i can capture the video output and provide/pass it towards v4l as input? use case: addressing an RGBW led strip depending on video content (aka TV ambilight)