Quote:
Originally Posted by katadelos
A Kindle is a really crappy candidate for this, especially a KT4.
You’re correct in mentioning that the SoC would support the capabilities that you’re after but it’s not a given that the relevant pins are broken on as a test point on the PCB in the first place or that they’re not already used by one of the built in peripherals.
I’m not sure that it’s even possible to edit/reflash the DTB on the later devices (PW4, KT4 onwards) without hard bricking the device due to the whole secure boot thing?
For this use case I’d seriously consider using a Kobo instead - contrast having to figure out a novel, low level method of adding storage vs just popping out the SD card and cloning it to a larger one.
|
Yeah, i know the KT4 is not the perfect model for this, even a kindle, but it is what i have in hand right now and at least want to give it a try. Before accidentally bricking my kindle, can you tell me more about the secure boot implementation in the kindle? Is there a thread were i can read more about this? Because if i can easily flash DTBs on my kindle, my next step would be to hack-off a rudimentary oscilloscope with an arudino and start searching for the SPI ports. My idea is to use the file "arch/arm/boot/dts/imx6sl.dtsi" (which has the definitions of the 4 SPI ports in software) inside of the source of the linux kernel to create "recognizable" SPI signals as a driver for the kernel, so that i can search them and identify the ports (if do they exist) with my oscilloscope.