cnxsoft has quit [Read error: Connection reset by peer]
cnxsoft has joined #linux-sunxi
wens has joined #linux-sunxi
wens has quit [Ping timeout: 264 seconds]
wzyy2 has joined #linux-sunxi
ErwinH has joined #linux-sunxi
ErwinH has quit [Remote host closed the connection]
ErwinH has joined #linux-sunxi
ganbold has joined #linux-sunxi
<jelle>
MoeIcenowy: ohhh thanks
wens has joined #linux-sunxi
massi has joined #linux-sunxi
ganbold has quit [Quit: This computer has gone to sleep]
ganbold has joined #linux-sunxi
wens has quit [Ping timeout: 240 seconds]
<jelle>
MoeIcenowy: I just enabled the usb port in the orangepi-zero dts and then just suffered from kernel panics
wens has joined #linux-sunxi
ganbold has quit [Quit: This computer has gone to sleep]
<plaes>
o_O
Andy-D has joined #linux-sunxi
<jelle>
well for the extension board that is
<plaes>
power issue?
<jelle>
plaes: not sure, didn't save the backtrace. Will study it later
ErwinH has quit [Read error: Connection reset by peer]
ganbold has joined #linux-sunxi
ErwinH has joined #linux-sunxi
wens has quit [Ping timeout: 256 seconds]
foxx_ has quit [Ping timeout: 240 seconds]
f0xx has joined #linux-sunxi
ganbold has quit [Quit: This computer has gone to sleep]
ganbold has joined #linux-sunxi
<vishnup>
mripard: wens:This is regarding modern clock NKMP.
<vishnup>
can we use NKMP i.e. (Parent*N*K)/P/M, for NKP i.e. (Parent * N *K)/P ?
<vishnup>
considering M as 1.
<vishnup>
Or do we need to define new NKP?
IgorPec has joined #linux-sunxi
ganbold has quit [Quit: This computer has gone to sleep]
<MoeIcenowy>
jelle: dmesg availble now?
ganbold has joined #linux-sunxi
nemunaire has quit [Ping timeout: 240 seconds]
nemunaire has joined #linux-sunxi
<jelle>
MoeIcenowy: nope at work :(
andi_sp has joined #linux-sunxi
florianH has joined #linux-sunxi
<MoeIcenowy>
I tried to enable {e,o}hci{2,3} on my H2+
<MoeIcenowy>
it works
ganbold has quit [Quit: This computer has gone to sleep]
Leepty has joined #linux-sunxi
ganbold has joined #linux-sunxi
ganbold has quit [Client Quit]
<swiftgeek>
I have tried to run meminf on A33 but all i have got was Error: unknown or unhandled Soc: 0x1667
ganbold has joined #linux-sunxi
<swiftgeek>
i have got script.bin from nanda though
<swiftgeek>
and sunxi-fel read 0x42400000 0x82d0 boot1.header seems to glitch A33 completely
hp197 has joined #linux-sunxi
ganbold has quit [Client Quit]
<swiftgeek>
usb_bulk_send() ERROR -7: Operation timed out
ganbold has joined #linux-sunxi
<NiteHawk>
maybe a "bulk" transfer of that size doesn't go through well - you could try to transfer smaller chunks, e.g. 0x1000 at a time
wens has joined #linux-sunxi
ganbold has quit [Quit: This computer has gone to sleep]
wens has quit [Remote host closed the connection]
wens has joined #linux-sunxi
<swiftgeek>
NiteHawk: that doesn't seems to work, it's just glitching usb immediately
<NiteHawk>
:(
<NiteHawk>
the trivial commands like "ver" or "hexdump" of a few bytes do work however, though?
<swiftgeek>
yep
<swiftgeek>
at least ver
<swiftgeek>
not sure what would be safe to hexdump on A33
<NiteHawk>
hang on - with 0x42400000 you're reading DRAM, not SRAM. so you *did* initialize DRAM by loading and running SPL, right?
maz has quit [Ping timeout: 245 seconds]
wens has quit [Ping timeout: 256 seconds]
<swiftgeek>
i used key combination/sequence to enter FEL
wens has joined #linux-sunxi
matthias_bgg has joined #linux-sunxi
mhlavink has joined #linux-sunxi
<NiteHawk>
if you can read SRAM (e.g. "./sunxi-fel read 0x2000 0x1000 test.bin"), then I nevertheless suspect that DRAM isn't initialized
Andy-D has quit [Ping timeout: 240 seconds]
wens has quit [Ping timeout: 245 seconds]
<swiftgeek>
for now it looks like device bricked itself and stays on logo ^^'
Leepty has quit [Remote host closed the connection]
Leepty has joined #linux-sunxi
<swiftgeek>
NiteHawk: that works
Leepty has quit [Remote host closed the connection]
<NiteHawk>
then it looks as if FEL has trouble accessing DRAM...
<swiftgeek>
i guess those devices using nand tend to brick themselves easily? xD
maz has joined #linux-sunxi
Leepty has joined #linux-sunxi
wens has joined #linux-sunxi
<swiftgeek>
i guess i will need to fetch some firmware and move it to VM to flash
<NiteHawk>
well... FEL is somewhat fragile, as it doesn't seem to do exception handling. so once the ARM cpu borks up, FEL is expected to fail (it will no longer return / respond to queries)
<MoeIcenowy>
you can low down the boot frequency in U-Boot
<MoeIcenowy>
but it must be admitted Banana Pi did a bad board design here
<willmore>
Yeah, you're seeing options in a EXT4 that aren't supported by that old kernel.
<parazyd>
willmore: meaning i made the filesystem with a recent e2fsprogs?
<parazyd>
probably
<parazyd>
MoeIcenowy: can you point me to some documentation on this uboot voltage control?
<MoeIcenowy>
not voltage control
<MoeIcenowy>
but frequency control
<willmore>
parazyd, do what MoeIcenowy said and use EXT3. It's more likely to be compatable with an old kernel
<MoeIcenowy>
the Banana Pi M2+ board supports no voltage control
<MoeIcenowy>
this is weird
<parazyd>
yeah it's an unusual board indeed
<Ke>
IIRC using nouid32 mount option helped for me on ext4
<Ke>
or option
<Ke>
anyway ext4 is definitely recommended, just figure out what the feature is
<MoeIcenowy>
I'm trying to criticize the guys from BPi ;-)
<MoeIcenowy>
P.S. currently the new Banana Pi vendor is no longer Sinovoip -- a new company called BPi Technology （比派科技） is splited up from Sinovoip
<willmore>
MoeIcenowy, try harder.
<jelle>
MoeIcenowy: ugh and they both make banana's?
florianH has quit [Quit: Connection closed for inactivity]
<MoeIcenowy>
The part that procudes bananas in Sinovoip is now independent as BPi
<KotCzarny>
MoeIcenowy: lol, again?
<parazyd>
lol
<MoeIcenowy>
the BPi Technology is still funded by Sinovoip
* jelle
doesn't buy banana's period :)
<MoeIcenowy>
it only changed a name
* MoeIcenowy
only have BPi M2U as it's the earliest R40
netlynx has quit [Quit: Ex-Chat]
cobra_koral has quit [Ping timeout: 264 seconds]
<KotCzarny>
bpi-m1 was actually good
<KotCzarny>
and bpi-r1 isnt THAT bad neither
<MoeIcenowy>
WHAT THE ****
<MoeIcenowy>
THE BPI GUY SAY THAT THE FIXED VOLTAGE IS BY DESIGN
<MoeIcenowy>
AND IT'S DESIGNED TO CLOSE CORES
<BenG83_>
oO
<MoeIcenowy>
"嗯，故意的 为了下面一些型号的开发板铺路 不能让M2P影响销量"
<KotCzarny>
designed to WHAT ?
<MoeIcenowy>
designed to make the board not able to work properly ;-)
<jelle>
lol
<MoeIcenowy>
You can try to google translate my sentence above
<MoeIcenowy>
"价格便宜的板子肯定不能让你舒服的用，大概说白了就是这么个意思"
<MoeIcenowy>
WHAT THE ***
<BenG83_>
what is M2P?
<MoeIcenowy>
P = Plus
<NiteHawk>
MoeIcenowy: weren't they forced to transfer the "BPi" name to a non-profit intermediate as a result of the constant bickerings between LeMaker and SinoVoip?
<MoeIcenowy>
NiteHawk: nope
<jelle>
MoeIcenowy: this translates to a weird sentence: "Affordable board certainly can not make you comfortable with, probably white is such a meaning"
<parazyd>
f'ing china
<MoeIcenowy>
the BPi Techonology is fully funded by Sinovoip
<MoeIcenowy>
jelle: you got it
<NiteHawk>
m-kay
OtakuNekoP has joined #linux-sunxi
* willmore
makes popcorn
<TheLinuxBug>
KotCzarny: welcome back :D
dave0x6d has quit [Quit: Connection closed for inactivity]
foxx_ has quit [Ping timeout: 264 seconds]
<KotCzarny>
:)
<KotCzarny>
hullo
<MoeIcenowy>
maybe someone should make the default frequency lower in Banana Pi M2+'s U-Boot defconfig?
tkaiser has joined #linux-sunxi
<tkaiser>
MoeIcenowy: Maybe 9 months ago I reviewed M2+ and said that I don't understand why they did not at least use SY8113B to switch between 1.1V and 1.3V. Then Lion Wang (SinoVoip CEO) said that it would be hard to source this IC. Later I realized that there is SY8113B on the board but they forgot GPIO regulation.
<MoeIcenowy>
Ah-oh
<MoeIcenowy>
tkaiser: another problem
<willmore>
Face, meet palm. Palm, meet face.
<tkaiser>
MoeIcenowy: I still don't get who does the ODM work (obviously not SinoVoip judged on how less they know about their own hardware) and who produces stuff. But also that doesn't matter that much.
<MoeIcenowy>
what's the real voltage of VDD_CPUX on M2+ ?
<MoeIcenowy>
on schematics it says 1.2V
<MoeIcenowy>
on linux-sunxi wiki it says 1.3V
<tkaiser>
MoeIcenowy: According to their schematic it's 1.2V but in reality 1.3V. Confirmed by super moron called @sinovoip in their forum.
<tkaiser>
But of course they don't update schematic. And they don't kick out this guy responsible for all this mess (doing 'documentation' while giving a sh*t about correctness)
<tkaiser>
MoeIcenowy: Several people measured and it's 1.3V. Anyway... simple conclusion: Stay away since it's not worth the hassles :)
<willmore>
^^^^
<MoeIcenowy>
tkaiser: can BPi M2+ work properly without throttling at 816MHz?
apritzel has joined #linux-sunxi
<swiftgeek>
Thx to anyone who fixed audio :D
OtakuNekoP has quit [Remote host closed the connection]