lurchi__ has quit [Quit: Konversation terminated!]
lurchi_ has joined #linux-sunxi
lurchi_ has quit [Quit: Konversation terminated!]
lurchi_ has joined #linux-sunxi
lurchi_ has quit [Quit: Konversation terminated!]
lurchi__ has joined #linux-sunxi
lurchi__ has quit [Quit: Konversation terminated!]
lurchi__ has joined #linux-sunxi
lurchi__ has quit [Quit: Konversation terminated!]
lurchi_ has joined #linux-sunxi
lurchi_ is now known as lurchi__
lurchi__ has quit [Quit: Konversation terminated!]
lurchi__ has joined #linux-sunxi
cnxsoft has joined #linux-sunxi
<MoeIcenowy>
jernej: don't worry, the chip won't hang if no ext losc is present
craigo has joined #linux-sunxi
<rr123>
Write-error on swap-device (254:1:108360) -- uname -a Linux orangepizero 4.19.59-sunxi #5.91 SMP Mon Jul 15 14:09:32 CEST 2019 armv7l GNU/Linux
<rr123>
sunxi-mmc 1c10000.mmc: data error, sending stop command
<rr123>
xradio_wlan mmc1:0001:1: missed interrupt
<rr123>
quite some concerning dmesgs from H2+ on orangepi zero lts
<rr123>
the wifi will fail actually, the zram write-error could be ok or fatal
RichardG867 has joined #linux-sunxi
TheSeven has quit [Ping timeout: 252 seconds]
TheSeven has joined #linux-sunxi
NeuroScr has quit [Quit: NeuroScr]
NeuroScr has joined #linux-sunxi
Perlovka has joined #linux-sunxi
dddddd has quit [Remote host closed the connection]
<jernej>
MoeIcenowy: wens: I'm not worried about hanging, but I'm researching why HDMI-CEC doesn't work on OrangePi PC2 (H5) and I noticed that it doesn't have 32 kHz crystal.
<jernej>
I didn't do any tests, but that could be a reason
<jernej>
it certainly was for Tanix TX6 (H6)
<jernej>
I think we have to introduce a way to tell driver to select either internal or external 32 kHz source
night199uk has quit [Ping timeout: 245 seconds]
<jernej>
easiest way would be by removing or adding ext losc phandle to RTC node
night199uk has joined #linux-sunxi
<jernej>
but driver has a check for that and fails if no clock is specified
<jernej>
maybe that can be changed
_whitelogger has joined #linux-sunxi
<MoeIcenowy>
jernej: what clock accuracy is needed for HDMI-CEC?
<jernej>
not sure, internal LOSC seems to be just fine
<MoeIcenowy>
have you tried to remove the code to enable ext OSC?
<jernej>
I'm more worried that auto switching might not work correctly
<MoeIcenowy>
so first try to remove it
<MoeIcenowy>
I think it should be working
<jernej>
as I said, I didn't do any tests with H5 yet, but I plan to do these days
<jernej>
but I think it's misleading to have ext LOSC specified in DT if there isn't any
<MoeIcenowy>
BTW
<MoeIcenowy>
I remember there's some SoC that have a wrongly tweaked internal OSC
<MoeIcenowy>
but forgot whether it is H3, H5 or A64
<MoeIcenowy>
the wrongly tweaked internal OSC runs at 22K rather than 32K
<jernej>
are you sure?
<jernej>
that could also explain why it doesn't work
<jernej>
anyway, all A64 boards that I currently use have ext LOSC crystal and H5 one does not
<jernej>
so I can't tell which one has the issue, but I would bet on H5 then
<jernej>
hm... I could check frequency with the scope, but I have to prepare test image for that
<jernej>
next week
<jernej>
oh, it could be also H3, because I currently use bitbanged HDMI-CEC
<jernej>
I'll test all three
_whitelogger has joined #linux-sunxi
vagrantc has joined #linux-sunxi
xqdzn has quit [Ping timeout: 260 seconds]
lurchi_ has joined #linux-sunxi
Putti has quit [Ping timeout: 268 seconds]
sunshavi has quit [Read error: Connection reset by peer]
lurchi__ has quit [Ping timeout: 246 seconds]
sunshavi has joined #linux-sunxi
tllim has joined #linux-sunxi
s_frit has quit [Remote host closed the connection]
s_frit has joined #linux-sunxi
airwind has joined #linux-sunxi
selfbg has joined #linux-sunxi
TheSeven has quit [Ping timeout: 245 seconds]
TheSeven has joined #linux-sunxi
vagrantc has quit [Quit: leaving]
reinforce has joined #linux-sunxi
ldevulder_ has joined #linux-sunxi
ldevulder has quit [Ping timeout: 246 seconds]
ldevulder_ is now known as ldevulder
warpme_ has joined #linux-sunxi
warpme_ has quit [Quit: warpme_]
tdebrouw has joined #linux-sunxi
matthias_bgg_ has joined #linux-sunxi
yann has quit [Ping timeout: 246 seconds]
nashpa has quit [Remote host closed the connection]
nashpa has joined #linux-sunxi
tllim has quit [Read error: Connection reset by peer]
NeuroScr has quit [Quit: NeuroScr]
tnovotny has joined #linux-sunxi
suprothunderbolt has quit [Ping timeout: 276 seconds]
suprothunderbolt has joined #linux-sunxi
yann|work has joined #linux-sunxi
netlynx has joined #linux-sunxi
netlynx has joined #linux-sunxi
diego71_ has joined #linux-sunxi
diego71 has quit [Ping timeout: 246 seconds]
warpme_ has joined #linux-sunxi
gaston1980 has joined #linux-sunxi
nexgen2 has joined #linux-sunxi
nexgen2 has quit [Ping timeout: 276 seconds]
ldevulder has quit [Quit: Leaving]
florian has quit [Read error: No route to host]
florian has joined #linux-sunxi
nexgen2 has joined #linux-sunxi
ldevulder has joined #linux-sunxi
AneoX has joined #linux-sunxi
<willmore>
Is there an issue with H6 boards that cause them to take a long time to reboot? My Orange Pi One Plus takes several minutes to reboot. I guess I should hook a serial line off of it and see if it's saying anything...
<KotCzarny>
bad value in hw watchdog?
<KotCzarny>
getting interpreted as minues instead of seconds?
<KotCzarny>
but that's assuming it's not an OS issue
nexgen2 has quit [Ping timeout: 265 seconds]
diego71_ has quit [Ping timeout: 245 seconds]
Mangy_Dog has joined #linux-sunxi
diego71 has joined #linux-sunxi
nexgen2 has joined #linux-sunxi
netlynx has quit [Quit: Ex-Chat]
<libv>
willmore: plaes documented something about the latest debian version
<libv>
true, but the delay there can be adjusted as well
<libv>
and no uart will come back to bite you
<libv>
unless you're a proper embedded developer... then, then, you use jtag
<tdebrouw>
well, I'm trying to replace that unknown bootloader with uboot
<tdebrouw>
but I need the register settings
<tdebrouw>
for the ddr
<libv>
and you have to first have the proper cable made and when you've gotten approval from your manager to spend the money, and completed the process, then your work is done for the next 2 weeks, as you wait for the cable to be crimped.
<libv>
*sigh*
<libv>
tdebrouw: it will be uboot
<KotCzarny>
tdebrouw: have you tried booting mainline uboot from sdcard?
<KotCzarny>
maybe r/v40 support is already good enough for your device
<libv>
no-one goes out and develops its own bootloader for a single android tablet
<libv>
i think some of the dashcam devices might do without uboot
<KotCzarny>
i'm booting android on h3 using mainline uboot and it works well
reinforce has quit [Quit: Leaving.]
<KotCzarny>
it might require few obscure settings in compilation/boot script though
florian_kc has joined #linux-sunxi
florian_kc is now known as florian
<jernej>
tdebrouw: Currently U-Boot uses only one timing settings for each type of DRAM for each Allwinner SoC IIRC.
<jernej>
as long as SoC and DRAM type combo is supported, it should just work
tobiasBora has joined #linux-sunxi
<jernej>
well, there is adjustable frequency, but that should be relatively easy to find out from android logs
<tobiasBora>
Hello,
<KotCzarny>
or by reading memory markings
tnovotny has quit [Quit: Leaving]
<jernej>
not necessarily, because frequency depends also on board routing
cnxsoft has quit [Quit: cnxsoft]
<tobiasBora>
I have an orange pi that I bought a while ago. I used it for a few weeks without any issue, and then it suddently stoped working after some holidays. When I boot with uart I've an error ### ERROR ### Please RESET the board ###. I'm not even sure what "reset the board" means, so I tried to put on the sd card some other systems, and now, this error is not displayed, but I suspect that it's because the uart
<tobiasBora>
interface is enabled only for uboot, and then when the kernel boot I think it's disabled
<tobiasBora>
however, I'm not even sure to know how to enable uart to continue debuging
<KotCzarny>
tobiasBora: unstable power?
<tobiasBora>
I tried to look into the partition 1, there is a semi binary file containing a line with bootargs: setenv bootargs "console=ttyS0,115200 console=tty1 root=/dev/mmcblk0p2 init=/sbin/init rootwait rootfstype=ext4 panic=10 consoleblank=0 enforcing=0 loglevel=7"
<mru>
probably a u-boot script file
<tobiasBora>
KotCzarny: I was also thinking the same, and I tried to move from a phone power supply to a much better power supply (still on the OTG port however) I'm using for my raspberry pi
<mru>
which is just text with a binary header added with mkimage
<tobiasBora>
mru: so I can still modify this file by end?
<jernej>
tdebrouw: anyway, possible reason why you can't read controller registers from Linux is that kernel might have CONFIG_STRICT_DEVMEM=y set
<mru>
yep, it's a u-boot script
<tobiasBora>
I see some people mentionning overlays=sun8i-h3-uart1, but not sure where to add that in my case
<KotCzarny>
mru, lack of uboot script doesnt result in internal uboot error
<tobiasBora>
(and I have h2+, not h3, don't know if it can still work)
<KotCzarny>
doesnt matter
<tobiasBora>
KotCzarny: I'm interested by this script just to enable uart again to see if I still have the same error (I guess I do however because the orange pi does not connect to the network)
<KotCzarny>
h2+ is marketing rebrand of h3
<tobiasBora>
it's funny, h2+ sounds like h2+ < h3
<KotCzarny>
nah
<KotCzarny>
just marketing
<mru>
that u-boot error is printed if something happens that shouldn't happen
<tobiasBora>
ok
<mru>
like an unexpected exception
<tobiasBora>
and is it possible to know what kind of exception it is?
<KotCzarny>
tobiasBora: write new armbian/h3droid to the card and boot?
<KotCzarny>
might be faster
<KotCzarny>
but i bet on power/sdcard troubles
<tobiasBora>
I can try with armbian or h3droid sure
<tobiasBora>
which one is the easier to setup/debug, or are you more familiar with?
<KotCzarny>
you can also just write uboot part
<tobiasBora>
(I remember using armbian when I first used it)
<tobiasBora>
if it's enough sure. What file should I use for that? I still don't understand lot's of stuff concerning uboot
<tobiasBora>
(even if last time you helped me a lot understanding new stuff)
<KotCzarny>
uboot is first megabyte of sdcard skipping first 8kB
<KotCzarny>
\ie. 8kb-1023kb
<tobiasBora>
and to get it I should download armbian, and then dd only 1023kb?
<KotCzarny>
do you have spare sdcard?
<KotCzarny>
might be easier since you arent proficient with dd
<tobiasBora>
you mean like another sd card?
<KotCzarny>
yes
<tobiasBora>
I have another one, but I don't really trust the other sd card, I had very strange errors with it...
matthias_bgg_ has quit [Read error: Connection reset by peer]
<KotCzarny>
sdcard errors are often result of bad power
matthias_bgg_ has joined #linux-sunxi
<tobiasBora>
well this error was on my desktop computer
<tdebrouw>
I'm sorry for the late respons -> someone on the telephone
<tobiasBora>
lot's of file were renamed with strange binary names
<tobiasBora>
but I can use it if you want
<tdebrouw>
i tried mainline uboot, as is, on a SD card
<tdebrouw>
and I see the SPL line, and that's it
<tdebrouw>
it should state something on memory, but I don't see it. :)
<tdebrouw>
[ 0.33]HELLO! BOOT0 is starting!
<tdebrouw>
I don't think uboot is outputting this. :]
<MoeIcenowy>
KotCzarny: it's not only for legacy kernel
<MoeIcenowy>
it's for the whole BSP
<MoeIcenowy>
also contains config for BSP U-Boot and boot0
craigo has quit [Ping timeout: 246 seconds]
rah_ is now known as rah
return0e has quit [Read error: Connection reset by peer]
return0e has joined #linux-sunxi
Putti has quit [Remote host closed the connection]
tdebrouw has quit [Quit: Leaving.]
marekbelisko has joined #linux-sunxi
Putti has joined #linux-sunxi
marekbelisko has quit [Quit: This computer has gone to sleep]
marekbelisko has joined #linux-sunxi
<willmore>
libv, it's on reboot, so without a serial console, I don't know if it's in the shutdown or startup side of things. I'll hook up serial and see what I get. Interestingly, I'm in the middle of debugging some serial adapter problems, so I have a bunch of them handy.
marekbelisko has quit [Quit: This computer has gone to sleep]
<Mangy_Dog>
when sending and receiving USB data... is it handled in a similar way to standard serial like in arduino? just faster? So if i wanted to I could setup my USB HID to allow for receiving data as well as sending it. And on my host machine run a scrip that would send data through a serial.write type of command?
<Mangy_Dog>
would i need to create an allownace for receiving data in the USBs disciptor?
<willmore>
Mangy_Dog, do you mean to ask on #arduino or something?
<Mangy_Dog>
no its a pi and usn HID question
<Mangy_Dog>
just a more generalised question
vagrantc has quit [Quit: leaving]
<wens>
willmore: Orange Pi seemed to have gotten a bad batch of chips, in that the normal watchdog does nothing
<wens>
willmore: reboot on the Pine H64 works fine with either watchdog
<wens>
willmore: IIRC we patched the DT to only use R_WDOG
ed_peguillan has joined #linux-sunxi
warpme_ has quit [Quit: warpme_]
<slapin>
have anybody had success with X11 + silead touch? I try to make it work sanely on poky, it sort of works but inprecise and not linear.... and calibration seems to be ignored too; is there some tool I miss?
<slapin>
looks like it multiplies coordinates by 2 and offsets for a few pixels on both dimentions
<slapin>
the results are consistent though
<slapin>
wens: ^
<wens>
slapin: it might be the touchscreen dimension isn't the same as the display?
tdebrouw has joined #linux-sunxi
tdebrouw has quit [Client Quit]
<slapin>
wens: dunno, it is strange, the fex data says 800x480 same as screen, I set it to that value
return0e has quit [Ping timeout: 246 seconds]
<slapin>
the problem is that I use firmware which is not from driver tablet uses, but from another .ko in the same directory; but firmware I extract from driver tablet uses in Android for some reason does not work on mainline silead driver
tuxillo has quit [Remote host closed the connection]
<slapin>
maybe I just need to hack silead.c's output values with hack patch
<slapin>
will see about this
<willmore>
wens, thank you for the heads up.
<willmore>
slapin, I may be completely misremembering this, but the 'firmware' for that chip may just be calibration data--dimensions, resolution, etc.
<willmore>
I'm probably wrong on that.
NeuroScr has joined #linux-sunxi
<wens>
the mainline driver will not scale values for you. maybe the bsp one does
florian has quit [Ping timeout: 245 seconds]
<willmore>
It strikes me that would be a good thing for the driver to do--with values from dts
<slapin>
willmore: I think the problem is dts, as it seems like when you switch x/y everything is messed up inconsistengly, so I will try to write resolution in revers and maybe it will fix scaling of coordinates
tuxillo has joined #linux-sunxi
curlybracket has joined #linux-sunxi
s_frit has quit [Remote host closed the connection]
s_frit has joined #linux-sunxi
ldevulder__ has joined #linux-sunxi
ldevulder_ has quit [Ping timeout: 265 seconds]
florian has quit [Ping timeout: 245 seconds]
<willmore>
slapin, good luck.
return0e has joined #linux-sunxi
ganbold_ has joined #linux-sunxi
ganbold has quit [Ping timeout: 245 seconds]
Mangy_Dog has quit [Ping timeout: 265 seconds]
Mangy_Dog has joined #linux-sunxi
juri_ has joined #linux-sunxi
Mangy_Dog has quit [Remote host closed the connection]