<willmore>
ssvb, any pointers to dual SPI you can give would be appreciated. The block diagram in the H5 manual didn't give any indication that such a thing was possible. But I just did a quick look.
<willmore>
I'd be glad to do some testing of possible/reliable speeds once I get my parts in house.
<willmore>
Winbond specs their chips to 104MHz, so if Allwinners spec of 100MHz is true.... I'll eat my shirt.
<willmore>
apritzel, good point. I figured they would be useful for something like that. They've been living in 4MB of flash machines for years. 16MB should feel spacious.
<apritzel>
willmore: indeed, that was my thinking
<apritzel>
IIRC they load everything into RAM, but allow to sync back into flash when needed
<apritzel>
and given that AW boards have plenty of RAM compared to most routers, that should be a nice fit
<ssvb>
willmore: the H5 user manual says the following about SPI: "Supports single and dual read mode"
<ssvb>
willmore: some information is also available in the SPI controller hardware registers descriptions
<willmore>
apritzel, agreed.
<willmore>
ssvb, good point, but I didn't see the signals needed. I guess they have MISO and MOSI in/out. Those could be retasked...
<willmore>
Time to break out the scope.
<ssvb>
willmore: check the "9.2.3.5. SPI Dual Read Mode" section in the manual
<willmore>
I wonder if the necessary pins are available on my Opi1
<ssvb>
yes, they are available
<ssvb>
both MOSI and MISO pins are used to transfer data
<ssvb>
and they are obviously connected to the chip
<willmore>
ssvb, that's what I get for skimming.
<willmore>
Time to break out the scope.
<willmore>
ssvb, the H3 datasheet mentions the dual read mode, but has no similar section to 9.2.3.5
<willmore>
Or I'm just missing it again.
chomwitt has quit [Quit: WeeChat 1.0.1]
<willmore>
But the register definitions seem similar--there's a dual mode read bit.
<ssvb>
willmore: yes, the H3 manual does not have this section, and in fact I did not have this H5 manual when I was experimenting with SPI
<ssvb>
I found the documentation a little bit incomplete/ambiguous
<willmore>
I can use an esp8266 module as a reference comparison as they support SPI, dual-SPI, and QPI with their flash.
<willmore>
ssvb, yeah, no kidding. :)
<willmore>
brb.
fdcx_ has quit [Remote host closed the connection]
Andy-D has quit [Ping timeout: 260 seconds]
cnxsoft has joined #linux-sunxi
fdcx has joined #linux-sunxi
egbert has quit [Disconnected by services]
egbert has joined #linux-sunxi
fdcx has quit [Remote host closed the connection]
apritzel has quit [Ping timeout: 256 seconds]
fdcx has joined #linux-sunxi
tsuggs has quit [Ping timeout: 240 seconds]
ninolein has quit [Ping timeout: 256 seconds]
ninolein has joined #linux-sunxi
LargePrime has quit [Ping timeout: 245 seconds]
LargePrime has joined #linux-sunxi
victhor has quit [Ping timeout: 245 seconds]
crzyp3ck has quit [Ping timeout: 260 seconds]
leviathan_ has joined #linux-sunxi
nOOb__ has joined #linux-sunxi
terra854 has joined #linux-sunxi
LargePrime has quit [Ping timeout: 240 seconds]
pg12 has quit [Ping timeout: 260 seconds]
pg12 has joined #linux-sunxi
nOOb__ has quit [Ping timeout: 240 seconds]
laj has quit [Quit: Page closed]
IgorPec has joined #linux-sunxi
vishnup has quit [Ping timeout: 240 seconds]
xes_ has joined #linux-sunxi
xes has quit [Ping timeout: 258 seconds]
vagrantc has quit [Quit: leaving]
TheSeven has quit [Ping timeout: 258 seconds]
TheSeven has joined #linux-sunxi
nOOb__ has joined #linux-sunxi
chomwitt has joined #linux-sunxi
kaspter has joined #linux-sunxi
montjoie has quit [Ping timeout: 260 seconds]
crzyp3ck has joined #linux-sunxi
montjoie has joined #linux-sunxi
crzyp3ck has quit [Ping timeout: 260 seconds]
kaspter has quit [Ping timeout: 256 seconds]
crzyp3ck has joined #linux-sunxi
foudubassan has joined #linux-sunxi
IgorPec has quit [Ping timeout: 260 seconds]
f0xx has joined #linux-sunxi
msevwork has joined #linux-sunxi
JohnDoe_71Rus has joined #linux-sunxi
walkiry has quit [Quit: Leaving]
IgorPec has joined #linux-sunxi
leviathan_ has quit [Read error: Connection reset by peer]
IgorPec has quit [Ping timeout: 245 seconds]
leviathan_ has joined #linux-sunxi
foudubassan has quit [Quit: Leaving]
ErwinH has joined #linux-sunxi
IgorPec has joined #linux-sunxi
crzyp3ck has quit [Ping timeout: 240 seconds]
fkluknav has joined #linux-sunxi
AneoX_ has joined #linux-sunxi
matthias_bgg has joined #linux-sunxi
matthias_bgg has quit [Read error: Connection reset by peer]
<crzyp3ck>
did anyboady find the uart or jtag pin outs?
leviathan_ has quit [Remote host closed the connection]
leviathan_ has joined #linux-sunxi
leviathan_ has quit [Remote host closed the connection]
msevwork has joined #linux-sunxi
leviathan_ has joined #linux-sunxi
leviathan_ has quit [Remote host closed the connection]
<terra854>
Hey guys, one of the members of the Pine community has figured out why the Pine sometimes doesnt turn on after a shutdown. (As in, running "shutdown -h now" and then holding the power button for a few seconds to turn it back on)
<fatius>
hi! I'm trying to build a mainline kernel for orange pi pc, i'm getting close, I think but I'm stuck at this error, which repeats forever: "sunxi-mmc 1c0f000.mmc: fatal err update clk timeout"
<fatius>
Any pointers on where to look to figure out what I'm doing wrong?
<apritzel>
fatius: this is a known bug nobody has had time yet to investigate
<apritzel>
doesn't happen with 4.9, also linux-next seems to work reportedly
<fatius>
apritzel: oh cool. I'll DL 4.9 and give it a shot.