bschwand

ok so I got it booting fully. I just created a very limited device tree for u boot and linux, that only had what I know is on the board and used. Eventually it booted. I thought it was stuck at some point but after the logs showing the rootfs was mounted an dsome other stuff. I figured the 32GB partitions might be in the process of being resized and remounted... and that was it. I'll have to clean up the patch files I made. Next experiment with I2S and some of the other hardware peripherals on that board... Cheers, thanks for the help !

I found the compilaton log in output/debug/... solved.

I have some patch files, and one of them leads to a .dts file not being compiled. I'd like to find what is wrong with the dtc compilation but I do not know what the exact command the armbian build script runs, so I can't reproduce... Is there a way to make the build totally verbose and see the command being executed ?

yes, I understand that but I am wondering how the armbian devs work in general... since the build process is quite streamlined, I imagined that there exists some tweaks and useful flags so just the kernel or modules can be incrementally built and setup for debugging. I am certainly not the first to want to do kernel debug on armbian build so I am just asking anybody experienced to share his workflow

Hi all, Is there some documentation or How To on how to debug the boot process ? I posted before I am trying to bring up a AW-SOM-A20 board that gets stuck at boot. I am kind of at a loss so I figure next step is to use the kernel debugger, which I have never done on linux (I have experience with darwin/mac OS and freebsd though) Is there a build option for armbian so that the debuggable kernel image is left around in the build process ? All help appreciated, thanks Bruno

more debug with booting with extraargs "debug initcall_debug" after [ 13.181458] initcall axp20x_pctl_driver_init+0x0/0xfff [pinctrl_axp209] returned 0 after 39165 usecs I thought axp20 pinctrl was hanging but it looks like it's init returns we are just hung after that... ??

replying to my own question, I found that I can do at the u-boot prompt setenv extraargs debug to increase the log level. now this is my current boot log it would seem like there is something stuck with the AXP209 ? any ideas ?

Hello, I am working on a board that is essentially the AW-A20-SOM with some peripherals on a backplane in which the AW-A20-SOM plugs into. I built armbian from source in the recommended VM configuration using the existing aw-som-a20.csc config. It boots and runs a special build that is installed in eMMC but I want to create an armbian build for it. First I want to boot it from SD card so I had just to change the following With this change, u-boot starts and loads the linux kernel from SDcard but then ends up in a boot loop with no messages from the linux kernel at all. It just reboots after 45 seconds. I guess my next step is to enable more verbose debug output from the linux kernel to see where it gets stuck, but I can't figure how to do that so far... I thought adding verbose or debug to the bootargs would do that but I guess the armbian boot process is much more complex.

Hi there, I have the same goal: get I2S sound working on a AW-A20-SOM board. Any update on this, any success ? Cheers !