ftg has quit [Read error: Connection reset by peer]
apritzel has quit [Ping timeout: 480 seconds]
radxanaoki has joined #linux-sunxi
junari has quit [Remote host closed the connection]
Hypfer has quit [Ping timeout: 480 seconds]
Hypfer has joined #linux-sunxi
jnn has joined #linux-sunxi
jn has quit [Ping timeout: 480 seconds]
hexdump0815 has joined #linux-sunxi
hexdump02 has quit [Ping timeout: 480 seconds]
hexdump02 has joined #linux-sunxi
hexdump01 has quit [Ping timeout: 480 seconds]
gsz has joined #linux-sunxi
gsz has quit [Ping timeout: 480 seconds]
aggi has quit [Ping timeout: 480 seconds]
aggi has joined #linux-sunxi
<wens>
welcome to my world. this is called second sourcing
apritzel has joined #linux-sunxi
apritzel has quit [Ping timeout: 480 seconds]
psydroid|2 has joined #linux-sunxi
psydroid|2 has quit []
apritzel has joined #linux-sunxi
evgeny_boger has joined #linux-sunxi
radxanaoki has quit [Quit: radxanaoki]
<apritzel>
Lightsword: there is a nvmem device in sysfs, which should show the fuses. Alternatively you can access the MMIO region directly, via /dev/mem (kernel config permitting)
<apritzel>
Lightsword: but most of the fuses should read all 0 on a device with the secure boot fuse set
<Lightsword>
apritzel, yeah, most were 0 when read from Linux, that one fel tool you made I remember showed all of them though, was just wondering if there's a way to make that work from Linux as well
Schimsalabim has quit [Ping timeout: 480 seconds]
Schimsalabim has joined #linux-sunxi
chewitt has joined #linux-sunxi
gsz has joined #linux-sunxi
<apritzel>
Lightsword: conceptually the SID is a secure device, that should not be accessible from the kernel at all
<apritzel>
It just happens to be because the secure boot fuse is typically not burnt, and AW somehow thinks this means TrustZone should not be in effect - which is just wrong
<apritzel>
Lightsword: what bits are you after, exactly? You can still read them in the SPL or in TF-A, then could copy them somewhere
<apritzel>
but for newer SoCs the interesting bits (serial number, thermal calibration value) *are* accessible even from a Secure boot device
<junari>
apritzel: my P85T have a different version of the motherboard. And in addition to RX and TX, there are GND and FEL contacts :D
<apritzel>
junari: ah, a FEL button is even better. I found this on my P80
<apritzel>
... P80T (A133) tablet as well, and it helps for experiments
<junari>
The bad news is that the emmc microchip has the label NAND
<junari>
aah and dram chip is lpddr3
<apritzel>
junari: NAND> oh no, but it is really raw NAND, or just labelled as such?
<junari>
don't know. It's BIWIN BWCTA1511X64G.
<junari>
Some document mentions that it is emmc 5.0
<junari>
But I haven't come across a datasheet for this chip yet.
<apritzel>
looks like it's eMMC, just using "qNAND" as a brand name, according to some product brief
<cousin_luigi>
bbl
cousin_luigi has left #linux-sunxi [#linux-sunxi]
aggi has quit [Remote host closed the connection]
aggi has joined #linux-sunxi
chewitt has quit [Ping timeout: 480 seconds]
gsz has quit [Ping timeout: 480 seconds]
junari has quit [Remote host closed the connection]
chewitt has joined #linux-sunxi
JohnDoe_71Rus has joined #linux-sunxi
tlwoerner_ has joined #linux-sunxi
tlwoerner has quit [Ping timeout: 480 seconds]
junari has joined #linux-sunxi
<junari>
It seems that the UART is not working. There is no 3.3V voltage. There should be a jumper somewhere
junari has quit [Quit: Leaving]
<apritzel>
junari: are you sure you got the right UART and the right pins? On my tablet the vendor firmware was outputting on UART0 muxed to the SD card pins, not on PB9/PB10.
<apritzel>
so what shall we do with the Radxa Wiki pages? There are full of atrocious and pathetic BSP build instructions :-(
<apritzel>
for the A5E I would at the very least like to move those to the end of the page. Shall they be made hidden, under some collapsible element (like we do for some bootlogs)?
<apritzel>
or moved to a separate (sub)page, like Radxa_Cubie_A5E/BSP ?
<Lightsword>
apritzel, was trying to pull the anti-rollback number from the efuse
<apritzel>
Lightsword: which version number are you tracking? The firmware (SPL/TF-A/U-Boot) one? Or the linux kernel or rootfs? Or some all-encompassing image version number?