LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
<LEBot>
[slack] <chewitt> Just ask the question
<LEBot>
[slack] <chewitt> then lots of people see the question and someone who knows the answer might reply
<LEBot>
[slack] <chewitt> I’m probably the person you’re looking for .. but that depends on the question?
chewitt has joined #libreelec
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
GNUmoon has quit [Remote host closed the connection]
GNUmoon has joined #libreelec
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
<hays>
my question is--what are the different files for and particularly how do i flash for emmc, sd, or usb media? I have an s922x based chip
<hays>
the instructions on u-boot website say to use dd twice in a kind of unusual way
<hays>
but they do not specify the media, and use the .sd.bin files
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
lolek has joined #libreelec
lolek has left #libreelec [#libreelec]
Bardon has quit [Ping timeout: 252 seconds]
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
Bardon has joined #libreelec
<LEBot>
[slack] <chewitt> You build u-boot for your board then follow the signing instructions in u-boot documentation, or crib things from the Makefile for the board in the FIP repo, to sign u-boot. Then you dd the signed u-boot to emmc twice (using the offsets you found) - also covered in u-boot documentation
<LEBot>
[slack] <chewitt> The FIP files are organised per-board and contain a mix of Amlogic standard files, and things like acs.bin which are unique to a specific board.
UndrWater has quit [Quit: ZNC 1.7.5+deb4 - https://znc.in]
<LEBot>
[slack] <chewitt> There are rare exceptions, but generally using FIP sources for some other board results in a non-booting board and as the SoC is normally hardwired to boot from eMMC first you have to resort to doing nasty things like shorting pins on the eMMC chip to disable it and allow boot from SD or USB to happen
UndrWater has joined #libreelec
<LEBot>
[slack] <chewitt> Before you leap further into attempting an “internal” install on some random TV box; be aware that most folks have low interest in walking you through recovery from this particular self-inflicted problem when it doesn’t work :)
<LEBot>
[slack] <chewitt> Amlogic burning tool and the factory Android ROM are the main way out of bricked box syndrome
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
arch3r has quit [Ping timeout: 248 seconds]
arch3r has joined #libreelec
LEBot has quit [Read error: Connection reset by peer]
LEBot has joined #libreelec
<hays>
chewitt: let me provide more details. I've read the u-boot docs. My board is an odroid n2l, which is rather new to mainline uboot, but has instructions. the instructions use the .sd.bin file and the 2 dd commands. My question is -- does that work for just sd cards? What about emmc and USB?
<hays>
I ask because I see 4 files, and maybe there is utility for them
<hays>
to be clear, the emmc is removable on this board
<hays>
Maybe of interest--the mfg u-boot just has you flash u-boot.bin.. they probably add the files you are speaking of during the build process though.
<chewitt>
hays: S905X and newer all look for the magic header at the same offsets on SD/USB/eMMC so u-boot.bin.sd.bin works for all
<hays>
oh that's nice. great
<chewitt>
older S905 requires some jumping through hoops as the magic header for eMMC is in the same places as the MBR data
<hays>
and i just found a way to keep a "hole" in the write using genimage.cfg
<hays>
so I think we're good let me give this a run
<chewitt>
^ in case you can't be bothered to build it yourself
<hays>
ooh careful that's a different board. nahh I've built it
<hays>
-n2l is on u-boot master
<chewitt>
ahh, I read N2 :)
<chewitt>
Yeah, I don't build N2L as I can't see anyone using it for LE use with it's lack of connectivity
<hays>
thankfully you helpfully provide the files
<chewitt>
Yup, people started to submit FIPs for other devices and we're happy to accept them to keep everything in a single upstream location
<chewitt>
It's used with Armbian as well as LE these days, and a couple of other minor distros too
arch3r has quit [Ping timeout: 260 seconds]
mave has quit [Quit: WeeChat 3.8]
arch3r has joined #libreelec
mave has joined #libreelec
tsal has quit [Quit: ZNC 1.6.5+deb1+deb9u2 - http://znc.in]
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
<hays>
hrm.. no dice but maybe its because im on a mac and I had to dd the image file
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
Fenster has quit [Ping timeout: 248 seconds]
notacactus has joined #libreelec
notacactus has quit [Quit: Client closed]
Fenster has joined #libreelec
nikolay_ has joined #libreelec
hjckr has quit [Ping timeout: 260 seconds]
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
<chewitt>
dd works the same on macOS as Linux
<chewitt>
are you trying to build an LE image? .. or some other distro?
tsal has joined #libreelec
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
minimal has joined #libreelec
<hays>
chewitt: dd is being a pain. I can't access the disk directly due to some new permissions error. and I can't find my vmware fusion license I guess they stopped storing it for you on the web... grr. so anyways I dd'ed it to the .img and then used balena. The image is custom.
<hays>
yeah i was sudo.. its some stupid mac thing im sure
<hays>
I could dual boot into asahi maybe I will. I just don't have a lot over on that partition
<chewitt>
in the past you had to do /dev/rdisk2 not /dev/disk2 .. rdisk was something like raw-disk which was needed for dd'ing things
<chewitt>
ahh, batocera
<chewitt>
@ntemis hangs around in our Slack instance :)
<hays>
chewitt: yeah i tried rdisk... i've flashed a lot before but Ventura did something
<hays>
Let me get linux up and running that is step 1 to rule out something weird going on with Balena and the .img
<hays>
chewitt: ahh yes hi @ntemis :)
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
<hays>
The wiki hasn't published a specific partition table for N2L, but shows the N2 partition table as 512B for BL1/MBR
<hays>
Then U'boot from sectot 1-1919
<hays>
followed by an environment partition
<hays>
0-2047 sectors
<hays>
u-boot.bin.sd.bin is 1,453,424 bytes or 2838 sectors
<hays>
seems like file should be 1048576 bytes
<hays>
There is free space marked off in the partition table... so maybe that's a red herring
narf has quit [Quit: narf]
<chewitt>
Just copy/paste whatever build recipe batocera uses for N2/N2+
<chewitt>
N2L will be identical
<chewitt>
other than the dtb file to include
<hays>
yeah I started there :)
<hays>
This was my approach-- (1) patch u-boot to include n2l defconfig from master branch (2) patch kernel from linux-next for same (3) lightly revise the build recipe
<hays>
Now I have cloned uboot master outside the build system and am trying things
<hays>
Also i can't seem to get a serial console which is annoying so im flying blind
LEBot has quit [Remote host closed the connection]