Kovács Gábor

@sgjavaThanks, then I will give a try next week.

@sgjava Sorry for being away for such a long time, I had lots of things to do. I will be trying again with the odroid c0 next week using a serial console connection. There is one more thing I would like to ask you. Does this new kernel support USB at all? I understand that there is a problem with USB based Ethernet adapters, but in my case I would like to use a 4G USB Stick. In case you confirm that USB works, I will try to make this thing work. Otherwise - if USB is not supported at all - there would be no reason in experimenting. Thanks again.

Hello Everyone, Thanks for all your help. I've got the image compiled, however it doesn't work on the C0. Maybe next week I'll be able to debug via uart to see what is happening (blue LED is blinking as it should). Additional thanks to torz77 for sharing me an image!

Hello sgjava, I used edge, the blue led blinked, but I have got nothing on the hdmi output neither on ssh (with an USB Ethernet adapter because it was a C0 not a C0).

Hello sgjava, In case you succeed with the compilation, would you be so kind to share the image with me? I would like to test your image on my odroid c0-s, perhaps yours would work on my machines.

I am not a git expert, but apparently what partially solved the compilation error was that I done this git clone --depth=1 --branch=master https://github.com/armbian/build instead of this: git clone --depth 1 https://github.com/armbian/build But this is just a hint.

Thanks again! After a complete reinstall of the repo (doing git clone --depth=1 --branch=master https://github.com/armbian/build ) and some "update"-s and "upgrade"-s the compilation worked. That is the good news. The bad news is that the resulting image (more than 2 Gbyte-s big) does not start on the odroid c0. Maybe it is only good for the c1... Thanks again.

Thanks, but still not working. Could you please check one last thing for me? Could you run git log in the build folder? I have been looking around in the commits of the armbian build folder master branch and it seems that there have been changes in around three weeks ago that could cause the problem. But this is just a hint...

Thanks, but I think I will give it up. I have this name for the deb: linux-u-boot-edge-odroidc1_23.02.0-trunk_armhf.deb , but still it wants to build u-boot .

Thanks, I think I understand that. But what should I put instead of linux-u-boot-edge-odroidc1_23.02.0-trunk_armhf.deb ? I guess I should change 23.02.0 to something else, but what should it be?

Hello, It is not working. I cannot fix this problem with the makefile... any help is appreciated!

Just one more question: In step 4, should I change all occurences of "current" to "edge"? The word "current" is written 3 times in step 4. EDIT: it works by just changing the first occurence. I have got an error: 💥] error! [ Failed to fetch Makefile from 'https://raw.githubusercontent.com/hardkernel/u-boot/e7d4447d551ccba5d60be8b11697aa0ab49086c4 b7b8dc21b64b9494618325c9b4d2fbae728aeed6/Makefile' ] I need to check this...

Thanks! I have also some c1-s that are still working and also some c0-s. I will give it a try, because I don't need Wifi. Thanks again.

Hello, Just a quick question. Do I read well that the above steps are good to produce a usable image for odroid c1? I am asking because I was looking for something like this for ages... Regards, Gabor

Hello, In a GOLANG based, RPi 3B+ project I am using the https://github.com/stianeikeland/go-rpio package to read the state of the GPIO-s. I am planning to set up some Banana Pi M2 Berries with the same software. The package - as it was expected - doesn't work with the M2 Berry. I could adapt the package for the Berry, but I don't know which peripheral chip is used in it. Does anyone know which peripheral chip is used in the Berry? (The schematic diagram on BPI's page is useless). Thanks, G.