cnxsoft1 has quit [Read error: Connection reset by peer]
cnxsoft has quit [Ping timeout: 256 seconds]
cnxsoft has joined #linux-rockchip
rompelstompel_ has joined #linux-rockchip
kloczek has quit [Remote host closed the connection]
kloczek has joined #linux-rockchip
kloczek has quit [Ping timeout: 240 seconds]
xerpi has quit [Remote host closed the connection]
aalm has quit [Ping timeout: 268 seconds]
rj1_ has quit [Quit: Connection closed for inactivity]
yann has quit [Ping timeout: 256 seconds]
equaa has joined #linux-rockchip
cnxsoft has quit [Quit: cnxsoft]
wzyy2 has joined #linux-rockchip
<sphalerite>
hanetzer: mmind00: thanks for the tips with the usb_uart stuff. I've booted the chromebook with rockchip.usb_uart now, how can I check if it's working? Should there be a device node in /dev for it?
<mmind00>
sphalerite: nope ... that thing really only routes the output of ttyS2 to the usb pins ... so you should not see any new device
<mmind00>
sphalerite: what you should see is one of the usb ports not appearing
<sphalerite>
huh, I don't have ttyS2 in /dev at all
<sphalerite>
only ttyS0
<sphalerite>
never mind yes I do
<mmind00>
sphalerite: and of course your kernel commandline should contain a console= part for ttyS2 I'd think
<sphalerite>
well… it does seem to send data when I echo into it, but it isn't arriving correctly. I'm guessing I've got differnet parity settings across the two or something
<mmind00>
sphalerite: did you try swapping rx+tx? I somehow always mix them up
<sphalerite>
I am getting data on my main laptop, it's just not the right data
<sphalerite>
surely that wouldn't happen if I'd swapped them?
<mmind00>
sphalerite: don't know ... but then if you are getting data it really sounds like a settings issue ... though I remember just running usb-serial with the same 115200 default setting as with a real serial port
<sphalerite>
hm, I've done stty sane on both ends, now the output of stty is the same on each, and there doesn't seem to be any data going through at all :/
<hanetzer>
sphalerite: which is why I assume and configure everything for 115200 :P
<sphalerite>
going to try redoing the wires
indy has quit [Ping timeout: 240 seconds]
<sphalerite>
bleh, it doesn't work.
<sphalerite>
and I can't really rule out physical connection issues because I don't have any proper tools.
<lurchi_>
sphalerite: get yourself a 8$ logic analyzer and hook it to your serial port ;-)
<hanetzer>
sphalerite: I assume your uart device has female pin sockets? or if male, you have female-female jumpers?
<hanetzer>
sphalerite: if so, you can do what I'm doing and get a usb a breakout and put some pin headers on that :)
<sphalerite>
lurchi_: but I don't want to have more stuff :p
<sphalerite>
I don't like having lots of stuff
<sphalerite>
I mean, yes, a USB breakout woudl probably be the best tool for the job. But I don't want to have yet another thing lying around that I'll use every once in a blue moon
<hanetzer>
^my life
<sphalerite>
I'm also not much of an expert in actually using this stuff, which doesn't help :P
<sphalerite>
Like I have no idea to what extent "stick the bare wires into the pin sockets" is likely to work at all.
mbakke has quit [*.net *.split]
icenowy[m] has quit [Ping timeout: 255 seconds]
sphalerit has quit [Ping timeout: 250 seconds]
<sphalerite>
yeah ok it's definitely a physical issue
atopuzov[m] has quit [Ping timeout: 276 seconds]
Easyfab has quit [Quit: Leaving]
<sphalerite>
YES! IT WOOOOORKS
<hanetzer>
noice
<hanetzer>
sphalerite: yeah. I'm thinking something like that uart you got but just a usb breakout with pins :)
<sphalerite>
Bleh, so I got the communication working in a fully booted system, but it doesn't seem to like booting with the hacked USB cable plugged in
<sphalerite>
in fact… it doesn't want to boot even without the hacked cable plugged in.
<sphalerite>
The only change I made was adding console=ttyS2,115200 to the cmdline...
aalm has joined #linux-rockchip
atopuzov[m] has joined #linux-rockchip
<sphalerite>
never mind, I was just silly and put ttyS0 instead of ttyS2
<sphalerite>
yaaaaay I can talk to the blank-screen kernel
<sphalerite>
or at least, hear things from it
<sphalerite>
yaaaaaaaaaay it booted. But it also didn't boot on the first try. Got to love those nondeterministic problems.
ssvb has joined #linux-rockchip
sphalerit has joined #linux-rockchip
icenowy[m] has joined #linux-rockchip
mbakke has joined #linux-rockchip
cnxsoft has joined #linux-rockchip
cnxsoft has quit [Remote host closed the connection]
LargePrime has quit [Quit: Leaving]
aalm has quit [Ping timeout: 260 seconds]
anarsoul has joined #linux-rockchip
lurchi_ has quit [Quit: Konversation terminated!]
lurchi_ has joined #linux-rockchip
tllim has joined #linux-rockchip
lurchi_ has quit [Ping timeout: 240 seconds]
LargePrime has joined #linux-rockchip
<sphalerite>
so I want to flash the original firmware back onto my c201. But flashrom --programmer internal says Processor detection/init failed.
<sphalerite>
Is there something specific I need to do?
<sphalerite>
I have a /dev/mtd0 which seems to contain the firmware, how terrible an idea would it be to just cat original.rom > /dev/mtd0?
<beeble>
will not work
<beeble>
you need the mtdblock layer or have to erase mtd0 first
<beeble>
flashcp from mtd-utils will take care of erasing and verifying the content if you use it with /dev/mtd0
anarsoul|2 has joined #linux-rockchip
anarsoul|2 has quit [Ping timeout: 265 seconds]
lurchi_ has joined #linux-rockchip
<sphalerite>
beeble: I have /dev/mtdblock0 as well, would catting it there be a terrible idea?
<rompelstompel_>
does the rockchip support securebooting? also does it have a TPM ?
<sphalerite>
rompelstompel_: rockchip is a company, not a chip. They have a variety of chipsets, some of them do
<rompelstompel_>
in retrospect I should have clarified RK3328
<beeble>
sphalerite: maybe better to use dd. would have to dig in to see if a stream redirect would cause any issues
<beeble>
sphalerite: but dd will definitely work
<sphalerite>
beeble: ok, here goes nothing. If it's bricked afterwards I'm blaming you ;)
<beeble>
stop
<beeble>
or hmm
<beeble>
no
<beeble>
we are talking about spi flash, so there are no offsets
<sphalerite>
too late anyway
lurchi_ has quit [Remote host closed the connection]
lurchi__ has joined #linux-rockchip
<sphalerite>
If it's bricked I'll get a hardware flasher to fix it
<sphalerite>
if not I'll celebrate
<sphalerite>
it worked! :D
<sphalerite>
thanks
<beeble>
rompelstompel_: the chip does support secure boot. a tpm is usually a dedicated component so you would have to specify a board/device (but i'm not aware of any including one)
<rompelstompel_>
I'm using the rock64 but I also couldn't find one on board
<rompelstompel_>
do you perhaps know if one can be exposed on GPIO?
<beeble>
typical tpms use i2c. there is most likely one exposed on the board and if not you could use a soft i2c bitbang driver in linux
<beeble>
ok some are spi too
<beeble>
but same things are true for that interface
<hanetzer>
rompelstompel_: the SoC does not have a tpm iirc, but individual boards can have one on one of its busses. The asus c201/rk3288-veyron-speedy has one on the i2c bus iirc
<hanetzer>
infineon
<rompelstompel_>
for true secure boot the SoC should be able to communicate with the TPM before linux even loads or not?
<hanetzer>
honestly I have no clue.
<beeble>
no necessarily. you load a payload that is signed und verfied by the bootrom. the information for that is stored inside the cpu, so no tpm interaction needed
<beeble>
not*
<rompelstompel_>
So for say the RK3328 you don't specifically need a TPM?
<beeble>
depends on what you are trying to achieve. but for secure boot as in starting only a signed image you don't need a tpm
<rompelstompel_>
That is all I want to do. Have a secure image (containing potentially critical information like IP/password/encryption keys) and with a full chain of trust eventually boot into a trusted environment
aalm has joined #linux-rockchip
<hanetzer>
has anyone here had sucess with getting the mali kernel driver to work on a 4.16 kernel?
kloczek has joined #linux-rockchip
lurchi__ has quit [Ping timeout: 250 seconds]
anarsoul has quit [Ping timeout: 268 seconds]
lurchi__ has joined #linux-rockchip
lurchi__ has quit [Remote host closed the connection]
lurchi__ has joined #linux-rockchip
kaspter has quit [Read error: Connection reset by peer]