Cubitruck - script.bin etc. missing

[soundcheck]

Hi.

I just installed the latest Arch for Cubitruck according to the Wiki instructions.

So far so good. Everything came up. pacman -Syu installed an even more up2date kernel and other stuff.

However.

I can't find uEnv.txt, uImage, script.bin etc. under /boot anymore.

Files that show up under /boot are:
boot.scr boot.txt dtbs mkscr u-boot-sunxi-with-spl.bin zImage

Do I have to create those files on my own?


Otherwise everything seems to be OK.

I'd like to do some changes to the script.bin.fex some boot parameters etc..

Can somebody give directions?

Thx

[soundcheck]

Ok.

Slowly catching up.

* ARCH runs a mainline kernel - that makes a (the) difference
* boot parameters I can change in boot.txt, which needs to get converted to boot.scr with mkimage
* the newer u-boot setups can boot zImage (bootz vs. bootm)

What's still missing in my knowledge base after all is how to edit a similar file like the script.bin.FEX that's been
used before. And script.bin seems to require a uImage kernel. What goes togheter with the zImage setting?Any ideas?

Another issue. I don't get output over HDMI. I'm kind of blind while booting. Is HDMI still an issue
on the mainline kernel?

[soundcheck]

OK. I'm getting up2speed now.

Basically script.bin has been replaced with the mainline kernel device tree.
The board info and configuration that's been stored in the fex-file is now stored in a .dts file within the u-boot sources.
After compiling the kernel and or u-boot a so called device-tree blob (.dtb) is generated. That seems to reflect the script.bin.

Editing and activating the .dts is IMO much more complicated than editing the fexfiles for changing board configurations.
IMO a huge step back.

Beside that the currently used .dts is all but complete. Not sure why the ARCH maintainers take an incomplete kernel and device tree as base. It's IMO useless.

[sehraf]

ALARM is using the .dts file from the Linux kernel: https://github.com/torvalds/linux/blob/ ... etruck.dts

If things are missing i guess the corresponding driver is missing.

[soundcheck]

There's a quite a difference between .dts and the fexfile. I looked into it.
The .dts seems to me like a pretty stripped down version.

Basic functions like HDMI, WLAN etc. are missing. If that's because of missing (not yet ported - they'll might never get ported on such an aged board ) drivers it's a different issue.

That makes the CT board useless with ALARM.

Currently ALARM for Cubitruck I consider broken. (Don't know if more boards are affected)

ALARM should currently not use the mainline kernel!!!!!!!!!!!!!!!!! Please role back to sunxi-kernel.

There's no use to have a bleeding edge mainline kernel without crucial drivers and properly implemented device tree.

[sehraf]

both WLAN and HDMI are working using brcmfmac and simplefb driver (the later needs special setup AFAIK)
WLAN support exists since 3.14
Simple Framebuffer support exists since 3.19
maybe you should update your kernel (4.1 is the latest version) instead of spamming !!!!!!!!!!!!!!!

[soundcheck]

I do run the latest kernel.

Yep. The WLAN and HDMI worked on the good old sunxi kernels. Not on my ALARM mainline base install.

Perhaps you can shed some light where to find the wlan entry in the .dts file? Just as an example.
I am on a steep learning curve.
I also didn't manage to get any HDMI output with ALARM the newest kernel.

Beside that I didn't say anything wrong when comparing dts to fex. That's all but spamming.

[sehraf]

You don't need to mess around with the .dts file. Nevertheless here are the lines you asked for:
WLAN: https://github.com/torvalds/linux/blob/ ... k.dts#L180
Simple FB: https://github.com/torvalds/linux/blob/ ... 0.dtsi#L65

For HDMI to work you need to add some options to the kernel parameters: http://linux-sunxi.org/Display#boot.scr

For WLAN just try:
$this->bbcode_second_pass_code('', '
$ ip link show
')
This should list wlan0 as a network device. You can use wifi-menu or whatever you like to setup WLAN

[soundcheck]

Thx I'll do. I'll try.

Framebuffer is "disabled" in your example. I'd have to put an "OKAY" in there to get it going??
On the contrary I'd have to put a "disable" for "mmc3" to disable brcmf ???
Sorry I'd just wan to get the logic?
Beside that the fexfile clearly showed "wlan0" or similar. It was also well documented on the sunxi pages.

I did "mess" around with the script.bin in the past quite successfully.

I turned off (annoying)LED,BT,IR,WLAN,Audio.... . Basically everything that's not required for a special purpose.
That'll e.g. can save quite some power consumption -- if you're e.g. on batteries.

Unfortunately documentation is pretty fragmented, outdated or even not existing. That makes live not easier.

[kmnns]

Hi. I am trying the exact same right now, without any luck. No HDMI or WLAN.

Are there any updates on this?