mboehmer

Members
  • Content Count

    79
  • Joined

  • Last visited

 Content Type 

Forums

Member Map

Store

Crowdfunding

Raffles

Applications

Posts posted by mboehmer


  1. Hi,

     

    after a very successful deployment last year we will start a new sub sea C2 deployment next year (next to the old installation, in Northern Pacific, down at 2600m).

    Things work out nicely, but now we reached a state where some help from experts is welcome.

     

    I need to include some changes into the filesystem generated by Armbian build system, and hope someone can give me a hint on how to do it best way:

     

    - include some packages into the image (list available)

    - add some files to /etc/udev/rules.d/

    - add some lines to /etc/rc.local

    - have a preinstalled user plus home directory (optional)

     

    Any help is appreciated, and sorry for my dumb questions :(

     

    Michael


  2. HI guys,

     

    sorry for not giving earlier feedback (been busy with payload for our sounding rocket, no C2 included this time, guess it doesn't like 15g)...

    I just created a new image today (ARMBIAN 5.86 user-built Debian GNU/Linux 9 (stretch) 4.19.43-meson64), and console seems to be operational again.

    Thanks to everybody involved to fix that issue!

     

    Michael


  3. On 4/26/2019 at 6:26 PM, martinayotte said:

    The "-h" means "halt" ... Simply use the "reboot" command !

    I don't remember the issue here, could you restate it ?

     

    Simply said, I want to switch off the C2 by "shutdown -h now" - which seems to work when it is powered by the small connector.

    If it is powered by +5V pins of expansion port, it doesn't work: it shuts down, enters Uboot and starts again.

    For our deep sea operation we need both: powering by expansion port, and switching it off reliably.

    The first version of this board (with old kernel, approx. one year ago) did that job, and as there were no changes on powering scheme on my board, I assume that there is some problem with C2 switching off its power.

    I think it would be worth checking the AO bank - the "broken" console is there, and the VCCK regulator is being controlled from there. I will try to locate the signal on the PCB and check the signal by scope, in case that helps.

     

    EDIT: issue solved. The Odroid C2 doesn't like any voltage applied to GPIOs while it's off. I have two pins which are used to switch a DC/DC converter, in normal operation 3.0V are present there (by 10k0 resistor).

    This is sufficient to power some stuff inside the SoC and "boot through" in case of powerdown. Lines cut, and shutdown works as expected.


  4. Indeed, the readback of input status revealed it in the end. Could have thought of that earlier.

    Still, console problem is present, but that's another story.

    As well, a "shutdown -h now" allows the C2 to reboot, instead of powering down (which is not a good idea in a system on the sea floor).


  5. ISSUE SOLVED.

     

    I found a really tiny and well hidden solder bridge on a "strategical" point where the I/O lines 475, 480 and SDA came close (and were not insulated by solder stop due to vias).

    Using "busybox devmem" I could readback the I/O line states and trace that one back.


  6. 1 hour ago, martinayotte said:

    It appear normal. So, we don't have clues how it could interfering with I2C ...

    Well, fact is, that activating GPIO 475 or 480 (see table above) kills I2C access.

    Just checked with the logic analyer: exporting the pin doesn't do any harm, chaning its direction to "out" sets SDA low and leaves SCL high.

     

    In more details:

    (1) C2 bootet, i2cdetect finds all I2C slaves, I2C accesses are normal on logic analyzer.

    (2) exporting 475 doesn't change anything

    (3) setting 475 as output sets SDA low and leaves SCL high (pullup or active driven? don't know)

    (4) setting 475 as input again releases the SDA line again

    (4) I2C works again

    steps (3) and (4) can be repeated several times, no changes.

     

    So for me it looks like the SDA pin direction is "by chance" set also when accessing GPIO 475.

    Same applies for GPIO 480.

     

    If I can provide more input, please let me know. I urgently need working GPIO...

     

    EDIT: how can I peek/poke registers on the SoC directly? Would be the easiest way to see changes in I/O registers...

    EDIT2: busybox is your friend...


  7. Here we are: after booting, I2C works fine, and "cat /sys/kernel/debug/gpio" says:

    gpiochip1: GPIOs 378-496, parent: platform/c8834000.periphs:pinctrl@4b0, periphs-banks:
     gpio-378 (Eth MDIO            )
     gpio-379 (Eth MDC             )
     gpio-380 (Eth RGMII RX Clk    )
     gpio-381 (Eth RX DV           )
     gpio-382 (Eth RX D0           )
     gpio-383 (Eth RX D1           )
     gpio-384 (Eth RX D2           )
     gpio-385 (Eth RX D3           )
     gpio-386 (Eth RGMII TX Clk    )
     gpio-387 (Eth TX En           )
     gpio-388 (Eth TX D0           )
     gpio-389 (Eth TX D1           )
     gpio-390 (Eth TX D2           )
     gpio-391 (Eth TX D3           )
     gpio-392 (Eth PHY nRESET      |mdio-reset          ) out hi    
     gpio-393 (Eth PHY Intc        )
     gpio-394 (HDMI HPD            )
     gpio-395 (HDMI DDC SDA        )
     gpio-396 (HDMI DDC SCL        )
     gpio-397 (                    )
     gpio-398 (eMMC D0             )
     gpio-399 (eMMC D1             )
     gpio-400 (eMMC D2             )
     gpio-401 (eMMC D3             )
     gpio-402 (eMMC D4             )
     gpio-403 (eMMC D5             )
     gpio-404 (eMMC D6             )
     gpio-405 (eMMC D7             )
     gpio-406 (eMMC Clk            )
     gpio-407 (eMMC Reset          |reset               ) out hi    
     gpio-408 (eMMC CMD            )
     gpio-409 (                    )
     gpio-410 (                    )
     gpio-411 (                    )
     gpio-412 (                    )
     gpio-413 (                    )
     gpio-414 (                    )
     gpio-415 (                    )
     gpio-416 (SDCard D1           )
     gpio-417 (SDCard D0           )
     gpio-418 (SDCard CLK          )
     gpio-419 (SDCard CMD          )
     gpio-420 (SDCard D3           )
     gpio-421 (SDCard D2           )
     gpio-422 (SDCard Det          |cd                  ) in  hi    
     gpio-423 (                    )
     gpio-424 (                    )
     gpio-425 (                    )
     gpio-426 (                    )
     gpio-427 (                    )
     gpio-428 (                    )
     gpio-429 (                    )
     gpio-430 (                    )
     gpio-431 (                    )
     gpio-432 (                    )
     gpio-433 (                    )
     gpio-434 (                    )
     gpio-435 (                    )
     gpio-436 (                    )
     gpio-437 (                    )
     gpio-438 (                    )
     gpio-439 (                    )
     gpio-440 (                    )
     gpio-441 (                    )
     gpio-442 (                    )
     gpio-443 (                    )
     gpio-444 (                    )
     gpio-445 (                    )
     gpio-446 (                    )
     gpio-447 (I2C A SDA           )
     gpio-448 (I2C A SCK           )
     gpio-449 (I2C B SDA           )
     gpio-450 (I2C B SCK           )
     gpio-451 (PWM D               )
     gpio-452 (PWM B               )
     gpio-453 (Revision Bit0       )
     gpio-454 (Revision Bit1       )
     gpio-455 (                    )
     gpio-456 (J2 Header Pin35     |onewire@1           ) in  hi    
     gpio-457 (                    )
     gpio-458 (                    )
     gpio-459 (                    )
     gpio-460 (J2 Header Pin36     |onewire@2           ) in  hi    
     gpio-461 (J2 Header Pin31     )
     gpio-462 (                    )
     gpio-463 (                    )
     gpio-464 (                    )
     gpio-465 (TF VDD En           |TFLASH_VDD          ) out lo    
     gpio-466 (J2 Header Pin32     )
     gpio-467 (J2 Header Pin26     )
     gpio-468 (                    )
     gpio-469 (                    )
     gpio-470 (J2 Header Pin29     )
     gpio-471 (J2 Header Pin24     |cs                  ) out hi    
     gpio-472 (J2 Header Pin23     |sck                 ) out lo    
     gpio-473 (J2 Header Pin22     |cs                  ) out hi    
     gpio-474 (J2 Header Pin21     |miso                ) in  hi    
     gpio-475 (J2 Header Pin18     )
     gpio-476 (J2 Header Pin33     )
     gpio-477 (J2 Header Pin19     |mosi                ) out hi    
     gpio-478 (J2 Header Pin16     )
     gpio-479 (J2 Header Pin15     )
     gpio-480 (J2 Header Pin12     )
     gpio-481 (J2 Header Pin13     )
     gpio-482 (J2 Header Pin8      )
     gpio-483 (J2 Header Pin10     )
     gpio-484 (                    )
     gpio-485 (                    )
     gpio-486 (                    )
     gpio-487 (                    )
     gpio-488 (                    )
     gpio-489 (J2 Header Pin11     )
     gpio-490 (                    )
     gpio-491 (J2 Header Pin7      |onewire@0           ) in  hi    
     gpio-492 (                    )
     gpio-493 (                    )
     gpio-494 (                    )
     gpio-495 (                    )
     gpio-496 (                    )
    
    gpiochip0: GPIOs 497-511, parent: platform/c8100000.bus:pinctrl@14, aobus-banks:
     gpio-497 (UART TX             )
     gpio-498 (UART RX             )
     gpio-499 (VCCK En             )
     gpio-500 (TF 3V3/1V8 En       |TF_IO               ) out lo    
     gpio-501 (USB HUB nRESET      |usb-hub-reset       ) out hi    
     gpio-502 (USB OTG Power En    |USB_OTG_PWR         ) out hi    
     gpio-503 (J7 Header Pin2      )
     gpio-504 (IR In               )
     gpio-505 (J7 Header Pin4      )
     gpio-506 (J7 Header Pin6      )
     gpio-507 (J7 Header Pin5      )
     gpio-508 (J7 Header Pin7      )
     gpio-509 (HDMI CEC            )
     gpio-510 (SYS LED             |c2:blue:alive       ) out hi    
     gpio-511 (                    )

    After this little script:

    #!/bin/sh
    echo 475 > /sys/class/gpio/export
    echo out > /sys/class/gpio/gpio475/direction
    echo 0   > /sys/class/gpio/gpio475/value

    it says:

    gpiochip1: GPIOs 378-496, parent: platform/c8834000.periphs:pinctrl@4b0, periphs-banks:
     gpio-378 (Eth MDIO            )
     gpio-379 (Eth MDC             )
     gpio-380 (Eth RGMII RX Clk    )
     gpio-381 (Eth RX DV           )
     gpio-382 (Eth RX D0           )
     gpio-383 (Eth RX D1           )
     gpio-384 (Eth RX D2           )
     gpio-385 (Eth RX D3           )
     gpio-386 (Eth RGMII TX Clk    )
     gpio-387 (Eth TX En           )
     gpio-388 (Eth TX D0           )
     gpio-389 (Eth TX D1           )
     gpio-390 (Eth TX D2           )
     gpio-391 (Eth TX D3           )
     gpio-392 (Eth PHY nRESET      |mdio-reset          ) out hi    
     gpio-393 (Eth PHY Intc        )
     gpio-394 (HDMI HPD            )
     gpio-395 (HDMI DDC SDA        )
     gpio-396 (HDMI DDC SCL        )
     gpio-397 (                    )
     gpio-398 (eMMC D0             )
     gpio-399 (eMMC D1             )
     gpio-400 (eMMC D2             )
     gpio-401 (eMMC D3             )
     gpio-402 (eMMC D4             )
     gpio-403 (eMMC D5             )
     gpio-404 (eMMC D6             )
     gpio-405 (eMMC D7             )
     gpio-406 (eMMC Clk            )
     gpio-407 (eMMC Reset          |reset               ) out hi    
     gpio-408 (eMMC CMD            )
     gpio-409 (                    )
     gpio-410 (                    )
     gpio-411 (                    )
     gpio-412 (                    )
     gpio-413 (                    )
     gpio-414 (                    )
     gpio-415 (                    )
     gpio-416 (SDCard D1           )
     gpio-417 (SDCard D0           )
     gpio-418 (SDCard CLK          )
     gpio-419 (SDCard CMD          )
     gpio-420 (SDCard D3           )
     gpio-421 (SDCard D2           )
     gpio-422 (SDCard Det          |cd                  ) in  hi    
     gpio-423 (                    )
     gpio-424 (                    )
     gpio-425 (                    )
     gpio-426 (                    )
     gpio-427 (                    )
     gpio-428 (                    )
     gpio-429 (                    )
     gpio-430 (                    )
     gpio-431 (                    )
     gpio-432 (                    )
     gpio-433 (                    )
     gpio-434 (                    )
     gpio-435 (                    )
     gpio-436 (                    )
     gpio-437 (                    )
     gpio-438 (                    )
     gpio-439 (                    )
     gpio-440 (                    )
     gpio-441 (                    )
     gpio-442 (                    )
     gpio-443 (                    )
     gpio-444 (                    )
     gpio-445 (                    )
     gpio-446 (                    )
     gpio-447 (I2C A SDA           )
     gpio-448 (I2C A SCK           )
     gpio-449 (I2C B SDA           )
     gpio-450 (I2C B SCK           )
     gpio-451 (PWM D               )
     gpio-452 (PWM B               )
     gpio-453 (Revision Bit0       )
     gpio-454 (Revision Bit1       )
     gpio-455 (                    )
     gpio-456 (J2 Header Pin35     |onewire@1           ) in  hi    
     gpio-457 (                    )
     gpio-458 (                    )
     gpio-459 (                    )
     gpio-460 (J2 Header Pin36     |onewire@2           ) in  hi    
     gpio-461 (J2 Header Pin31     )
     gpio-462 (                    )
     gpio-463 (                    )
     gpio-464 (                    )
     gpio-465 (TF VDD En           |TFLASH_VDD          ) out lo    
     gpio-466 (J2 Header Pin32     )
     gpio-467 (J2 Header Pin26     )
     gpio-468 (                    )
     gpio-469 (                    )
     gpio-470 (J2 Header Pin29     )
     gpio-471 (J2 Header Pin24     |cs                  ) out hi    
     gpio-472 (J2 Header Pin23     |sck                 ) out lo    
     gpio-473 (J2 Header Pin22     |cs                  ) out hi    
     gpio-474 (J2 Header Pin21     |miso                ) in  hi    
     gpio-475 (J2 Header Pin18     |sysfs               ) out lo    
     gpio-476 (J2 Header Pin33     )
     gpio-477 (J2 Header Pin19     |mosi                ) out hi    
     gpio-478 (J2 Header Pin16     )
     gpio-479 (J2 Header Pin15     )
     gpio-480 (J2 Header Pin12     )
     gpio-481 (J2 Header Pin13     )
     gpio-482 (J2 Header Pin8      )
     gpio-483 (J2 Header Pin10     )
     gpio-484 (                    )
     gpio-485 (                    )
     gpio-486 (                    )
     gpio-487 (                    )
     gpio-488 (                    )
     gpio-489 (J2 Header Pin11     )
     gpio-490 (                    )
     gpio-491 (J2 Header Pin7      |onewire@0           ) in  hi    
     gpio-492 (                    )
     gpio-493 (                    )
     gpio-494 (                    )
     gpio-495 (                    )
     gpio-496 (                    )
    
    gpiochip0: GPIOs 497-511, parent: platform/c8100000.bus:pinctrl@14, aobus-banks:
     gpio-497 (UART TX             )
     gpio-498 (UART RX             )
     gpio-499 (VCCK En             )
     gpio-500 (TF 3V3/1V8 En       |TF_IO               ) out lo    
     gpio-501 (USB HUB nRESET      |usb-hub-reset       ) out hi    
     gpio-502 (USB OTG Power En    |USB_OTG_PWR         ) out hi    
     gpio-503 (J7 Header Pin2      )
     gpio-504 (IR In               )
     gpio-505 (J7 Header Pin4      )
     gpio-506 (J7 Header Pin6      )
     gpio-507 (J7 Header Pin5      )
     gpio-508 (J7 Header Pin7      )
     gpio-509 (HDMI CEC            )
     gpio-510 (SYS LED             |c2:blue:alive       ) out hi    
     gpio-511 (                    )

    Hope that one helps.

    Edit: output from 4.19.6 stretch build, neweset kernel has console problems as discussed in other thread.

     

     


  8. Hi,

     

    just could test now the 4.19.6 stretch compilation - that one works as expected, and gives me a console on /dev/ttyAML0.

    Console works again, I can log in.

    GPIO problem with I2c interference is still there, i.e. exporting and setting GPIO 475 to out kills I2C access.

     

    Michael


  9. 40 minutes ago, martinayotte said:

    Of course ! Starkbier can be dangerous if drank too fast ... :lol:

    I see, you are taking the issue "beer" very serious. But all that bottles seem to share a problem: they are empty :)

    For me, my bottles are stored in the cellar - not empty (but opened). But Vodka doesn't expire really :) while beer does (not in your place, dude, I guess).

     

    Starkbier is something which should be enjoyed with care. I remember some American students visiting us when I was a young boy - they made archeological excavations of some Germanic site nearby. We had some barbecue, and my dad served Starkbier instead of the normal "beer" they were used to from the States (and he warned them to take care). It was hell of a fun to watch them after the first bottle...

     


  10. 53 minutes ago, martinayotte said:

    I'm a bit too far, I'm in Quebec ... But I like Hefeweizen ... :P

    I'm suggest to try Mainline Dev 5.0.y first, since A0 bank is working on my NanoPiK2, which is currently on 5.0.4.

    Otherwise, all tags can been seen in this github https://github.com/torvalds/linux/  , there is a "branch" dropdown with two tabs, one for branch and one for tags.

    I may show up sooner or later again in Victoria. Too far from Quebec, I assume - but the Odroids will go to Canadian shore :)

    Hefeweizen... yes. We have such kind here. And many more styles, like the Starkbier.

    Will start some new compilations tomorrow, just finished a test with stretch, but the setup is at university.


  11. 32 minutes ago, martinayotte said:

    This is because Jessie is EoL since June 6, 2018 ...

    Args. More coffee... Need a stretch image.

    Hope you guys are sometimes around Munich, I owe you a beer or two :)

    BTW, where do I find the available version numbers for kernels? Or better, the kernel sources?

    Maybe I can try to see if there were changes in code to touch AO banks?


  12. 1 hour ago, Igor said:

    Add KERNELBRANCH="tag:v4.19.6" or which kernel version you want to build to userpatches/lib.config

    Did I tell you already that the build system is really a miracle? :)

    Will try, had problems building Jessie today, apparently packages couldn't be downloaded. Starting new attempt right now.


  13. 38 minutes ago, Igor said:

     


    It looks like 4.19.y is broken. Will do more tests when possible.

    Indeed. Seems to be bank AO related (while that could also be somehow quirky in 5.77, as switching off failed there, too, but that's just my feeling).

    Is there any way to force the Armbian build system to use an older version? I had 5.77 running at least, so while you look at it (much appreciated!) I could continue with the GPIO stuff.


  14. Another observation, which indicates that the AO bank may have problems: one pin AO_BIT2 is used to control the main DC/DC regulator (VCCK), and switching off the Odroid C2 leads to a reboot instead of shutdown.

    So my best guess is that something in bank AO goes wrong, and both effects have the same root.


  15. Found something strange in both bionic and jessie dmesg output:

     

    [    1.677916] GPIO line 501 (usb-hub-reset) hogged as output/high
    [    1.684494] gxbb-aoclkc c8100000.sys-ctrl:clock-controller: Clock registration failed
    [    1.684533] gxbb-aoclkc: probe of c8100000.sys-ctrl:clock-controller failed with error -17
    [    1.685152] soc soc0: Amlogic Meson GXBB (S905) Revision 1f:c (0:1) Detected
    [    1.687516] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled

    According to C2 schematics, UART_AO_A is on AO bank.

    Maybe we should check on that part?

    Edit: seems to be located in drivers/clk/meson/meson-aoclk.c, according to the error message meson_aoclkc_probe() failed.

    Edit: I'm lost in tracing back the error number. Could be KDB_BADREG. Seems to happen in clk_hw_register() or clk_create_clk().


  16. 1 hour ago, Igor said:

    This is mine. 

    
    root@odroidc2:~# w
     06:11:08 up 16:13,  1 user,  load average: 0.00, 0.00, 0.00
    USER     TTY      FROM             LOGIN@   IDLE   JCPU   PCPU WHAT
    root     ttyAML0  -                Wed14    2.00s  0.12s  0.00s w

    Try to build the exact image: bionic - default. I didn't try Jessie since its EOL.

    Sir, yes, sir!

    Edit: I use "stretch", not "jessie".

    Welcome to ARMBIAN 5.78 user-built Debian GNU/Linux 9 (stretch) 4.19.34-meson64
    System load:   0.67 0.28 0.10   Up time:       1 min
    Memory usage:  4 % of 1976MB    IP:            10.162.208.175
    CPU temp:      33°C
    Usage of /:    8% of 15G

    Edit: bionic compiled. Same result, no console.

    Welcome to ARMBIAN 5.78 user-built Ubuntu 18.04.2 LTS 4.19.34-meson64
    System load:   0.46 0.11 0.04   Up time:       0 min
    Memory usage:  4 % of 1976MB    IP:            10.162.208.175
    CPU temp:      27°C
    Usage of /:    6% of 15G

     


  17. 1 hour ago, mboehmer said:

    I just changed to "verbosity=7" and don't get any messages after

    
    GXBB:BL1:08dafd:0a8993;FEAT:EDFC318C;POC:3;RCY:0;EMMC:0;READ:0;CHK:0;
    TE: 376888
    no sdio debug board detected
    
    BL2 Built : 11:44:26, Nov 25 2015.
    gxb gfb13a3b-c2 - jcao@wonton
    
    Board ID = 8
    set vcck to 1100 mv
    set vddee to 1050 mv
    CPU clk: 1536MHz
    DDR channel setting: DDR0 Rank0+1 same
    DDR0: 2048MB(auto) @ 912MHz(2T)-13
    DataBus test pass!
    AddrBus test pass!
    Load fip header from eMMC, src: 0x0000c200, des: 0x01400000, size: 0x000000b0
    Load bl30 from eMMC, src: 0x00010200, des: 0x01000000, size: 0x00009ef0
    Sending bl30........................................OK.
    Run bl30...
    Load bl301 from eMMC, src: 0x0001c200, des: 0x01000000, size: 0x000018c0
    Wait bl30...Done
    Sending bl301.......OK.
    Run bl301...
    00, des: 0x10100000, size: 0x00011130
    
    
    --- UART initialized after reboot ---
    [Reset cause: unknown]
    [Image: unknown, amlogic_v1.1.3046-00db630-dirty 2016-08-31 09:24:14 tao.zeng@droid04]
    bl30: check_permit, count is 1
    bl30: check_permit: ok!
    chipid: ef be ad de d f0Load bl33 from eMMC, src: 0x00034200, des: 0x01000000, size: 0x00078fa0
     ad ba ef be ad de not ES chip
    [0.492576 Inits done]
    secure task start!
    high task start!
    low task start!
    NOTICE:  BL3-1: v1.0(debug):4d2e34d
    NOTICE:  BL3-1: Built : 17:08:35, Oct 29 2015
    INFO:    BL3-1: Initializing runtime services
    INFO:    BL3-1: Preparing for EL3 exit to normal world
    INFO:    BL3-1: Next image address = 0x1000000
    INFO:    BL3-1: Next image spsr = 0x3c9
    
    
    U-Boot 2019.01-armbian (Apr 10 2019 - 13:22:25 +0200) odroid-c2
    
    DRAM:  2 GiB
    MMC:   mmc@72000: 0, mmc@74000: 1
    Loading Environment from EXT4... Card did not respond to voltage select!
    In:    serial@4c0
    Out:   serial@4c0
    Err:   serial@4c0
    Net:   eth0: ethernet@c9410000
    Hit any key to stop autoboot:  0
    Card did not respond to voltage select!
    switch to partitions #0, OK
    mmc1(part 0) is current device
    Scanning mmc 1:1...
    Found U-Boot script /boot/boot.scr
    3048 bytes read in 2 ms (1.5 MiB/s)
    ## Executing script at 08000000
    172 bytes read in 1 ms (168 KiB/s)
    4705956 bytes read in 116 ms (38.7 MiB/s)
    15253512 bytes read in 370 ms (39.3 MiB/s)
    35547 bytes read in 9 ms (3.8 MiB/s)
    687 bytes read in 3 ms (223.6 KiB/s)
    Applying kernel provided DT overlay meson-w1-gpio.dtbo
    901 bytes read in 3 ms (293 KiB/s)
    Applying kernel provided DT overlay meson-ina219.dtbo
    232 bytes read in 3 ms (75.2 KiB/s)
    Applying kernel provided DT fixup script (meson-fixup.scr)
    ## Executing script at 34000000
    ## Loading init Ramdisk from Legacy Image at 13000000 ...
       Image Name:   uInitrd
       Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
       Data Size:    4705892 Bytes = 4.5 MiB
       Load Address: 00000000
       Entry Point:  00000000
       Verifying Checksum ... OK
    ## Flattened Device Tree blob at 08008000
       Booting using the fdt blob at 0x8008000
       Loading Ramdisk to 7dad8000, end 7df54e64 ... OK
       reserving fdt memory region: addr=8008000 size=6f000
       Loading Device Tree to 000000007da66000, end 000000007dad7fff ... OK
    
    Starting kernel ...

    Will try with a different Odroid C2, and also check with a freshly compiled image.

    As I can enter the u-boot menu and see that messages, at least I can exclude wiring problems with RxD and TxD :)

    Edit: removing the overlays doesn't change anything on console.

    Edit: second C2 shows same behaviour with compiled image from yesterday.

    Edit: freshly compiled kernel shows same behaviour. "verbosity=7" doesn't give any information after "kernel starting..."

     


  18. 5 hours ago, martinayotte said:

    Maybe corruption while writting the image to SDCard ... Did you used "etcher" ?

    I use only eMMC card, no SD cards. I tried with two images, and yes, I use etcher (on Windows, sorry, it's my main machine here).

    Even tried a different USB serial converter, and checked output of console header with scope. No edges after "starting kernel..."

     

    Just for understanding: /dev/tty1 should be routed to the J2 Rxd/TxD pins, so "echo BLA > /dev/tty1" should give some edges on J2 UART?


  19. 20 hours ago, martinayotte said:

    It seems that "spi-gpio" is not in the symbol table, so in such case "target" is not working ... But I gave it a try with "target-path" and it worked :

    
    /dts-v1/;
    
    / {
    	compatible = "amlogic,meson-gxbb";
    
    	fragment@0 {
    		target-path = "/spi-gpio";
    
    		__overlay__ {
    			status = "disabled";
    		};
    	};
    };

     

    A lot to learn I have. More complex simple things are. :)

     

    Will try tomorrow morning!

    EDIT: confirmed working! Thanks :)