<soumar>
where I skipped the blobs fip part as it seems it'S alredy being compiled in, in the hardkernels version of u-boot
<soumar>
I am able to boot linux, but the u-boot always rejects to boot FreeBSD kernel (kernel.bin, to be precise) with an error of wrong kernel image file
<soumar>
when I query the kernel.bin in my FreeBSD box, it simply claims it's an arm64/aarch64 kernel image
<soumar>
but u-boot does not seem to be sharing the same opinion
<soumar>
therefor I am in need to find a proper channel for my problem, which might be u-boot related, hardkernel related or simply FreeBSD related
<soumar>
as I have already stated I had had no experience with coding/u-boot, I am not really sure where to seek the support.
<marex>
soumar: isn't the BSD kernel distributed as an ELF file ?
<soumar>
and that's my main question now. Will be glad if you could point me the correct way
<marex>
soumar: so, you need to relocate it using some bootelf or some such ?
EdSwarthout has joined #u-boot
<marex>
also, you need to have a kernel port compatible with your hardware (ie. the kernel must contain the drivers and you need to somehow pass DT to it (if applicable))
<soumar>
marex sure, but for aarch64/arm64 we have kernel.bin, which identifies itself as linux arch64 boot image
<marex>
oh, that
<marex>
soumar: so, try booti
<marex>
soumar: that is for booting arm64 Image (the linux ones at least)
<soumar>
to be honest, as I am new to this area, I am really not experienced.
<soumar>
booti - yes, I have tried those
<soumar>
but no joy.
<soumar>
regarding the DT
<soumar>
can I reuse those from linux? namely arch?
<marex>
so what does booti print ?
<soumar>
or do I have to recompile them myself?
<marex>
I dont know what bsd does there, the DT is hardware description, so likely yes
<marex>
you should be able to use the .dtb file for your platform, assuming the bsd kernel needs a DT (it likely does)
<soumar>
well, among my tries, booti mostly complains about [rsvmem] get fdtaddr NULL!
<marex>
soumar: pastebin the whole output please
<soumar>
I see
<soumar>
I only have some logs from today from my cutecom sessions
<soumar>
is that approproate?
<soumar>
I guess not really
<soumar>
anyway, can you point me a bit more in this DT stuff please?
<marex>
soumar: well, start logging, turn it on, run the booti attempt, stop logging, pastebin the log
<marex>
soumar: that;s what would be helpful
<soumar>
I have many of those in my log :)
<soumar>
and I have no idea what everything I tried in there
<soumar>
but the last thing was the u-boot was complaining about incorrect/unknown OS
<soumar>
just to be sure: u-boot is a platform independant bootloader, or?
<soumar>
kernel.bin: Linux kernel ARM64 boot executable Image, little-endian
<soumar>
and this is what the kernel.bin identifies itself as
<soumar>
the booti takes basically 3 arguments: the kerneladdr, the ramdiskaddr and the dtbaddr, correct?
<soumar>
I do not have the ramdisk, as we generally do not use it....
<soumar>
could that be the issue?
<marex>
sry, nmi
<soumar>
do you mean new model?
<marex>
aaaargh, pastebin.com now says "We value your privacy" (and that's why you must agree to us collecting data about you) and obscures the entire paste
<marex>
just a moment, video ad is now playing
<soumar>
f*ck
<marex>
ah
<marex>
soumar: u-boot 2015.01 ?
<marex>
soumar: isnt there a newer port for your system ?
<marex>
doesnt mainline support your board ?
<marex>
if so, there is a chance this problem was fixed in the last 6 years
<marex>
LeSpocky: didnt you do something with BSD recently ?
<soumar>
the kardkernel, as far as I know, patches their u-boot
<soumar>
I hope
<soumar>
but I can as well try the mainline u-boot as well ofc
<soumar>
there are "just" some blobs from the hardkernel
<soumar>
to be honest, I have no clue how to get them into the mainline
<soumar>
do I have to (cross)compile this on FreeBSD ordoes it not matter if I use linux/etc.. ?
<marex>
soumar: oh ... go $addr
<marex>
soumar: does it also say what the value of $addr should be ?
<marex>
soumar: if this is not a PIE, then you might need to use specific $addr value (address where to load the kernel in physical address space of the SoC)
<marex>
back in a bit
<soumar>
export CROSS_COMPILE=aarch64-none-elf- <- is this a must or can I use aarch64-linux-gnu- ?
<soumar>
as my ubuntu jail only has binaries for the later... :-/
<soumar>
so, just to be sure
<soumar>
I have simply compiled the mainline u-boot on FreeBSD
<soumar>
CROSS_COMPILE=aarch64-none-elf-
<soumar>
I only set this env variable
<soumar>
and used gnu make to compile it
<soumar>
for the odroid part I need to use linux
<soumar>
as it claims to get some linux toolchain
<soumar>
do you think I can simply compile the odroid part on ubuntu and reuse that?
<soumar>
or do I have to find my way to compile it on fbsd?
<marex>
soumar: you can probably use the aarch64-none-elf- toolchain too
<marex>
soumar: the difference is often only in the user-facing libraries that are included, not in the compiler itself
<soumar>
+1
<soumar>
the mainline compiled ok on my box
<soumar>
just the final u-boot.bin image is larger than 1MB.. if it is a probelm, I have no clue