Jump to content

mboehmer

Members
  • Posts

    141
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Have you tried the etcher software? So far I only use eMMC, but this one works really fine.
  2. Did you check console output? This would be really helpful.
  3. Hi, just returned to start working on a FLIR Lepton camera, with Odroid C4, hooked up to SPI (faster than the C2). WIth the official image from download page (Armbian 22.08 Jammy, kernel 5.10.144) I get the following message on console as soon as I try any access to spidev: [ 77.660325] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000 [ 77.666930] Mem abort info: [ 77.670400] ESR = 0x86000004 [ 77.673801] EC = 0x21: IABT (current EL), IL = 32 bits [ 77.677915] SET = 0, FnV = 0 [ 77.681367] EA = 0, S1PTW = 0 [ 77.684796] user pgtable: 4k pages, 48-bit VAs, pgdp=000000000f26b000 [ 77.690454] [0000000000000000] pgd=0000000000000000, p4d=0000000000000000 [ 77.697196] Internal error: Oops: 86000004 [#1] PREEMPT SMP [ 77.702645] Modules linked in: spidev rfkill cpufreq_powersave cpufreq_conservative lz4hc lz4hc_compress lz4 snd_soc_hdmi_codec snd_soc_meson_axg_tdmout snd_soc_meson_axg_sound_card snd_soc_meson_g12a_tohdmitx panfrost snd_soc_meson_card_utils gpu_sched snd_soc_meson_codec_glue snd_soc_meson_axg_frddr snd_soc_meson_axg_fifo meson_gxbb_wdt meson_vdec(C) v4l2_mem2mem ir_nec_decoder videobuf2_dma_contig meson_rng dw_hdmi_i2s_audio videobuf2_memops videobuf2_v4l2 videobuf2_common meson_saradc videodev rc_odroid mc meson_ir rc_core snd_soc_meson_axg_tdm_interface snd_soc_meson_axg_tdm_formatter snd_soc_core ac97_bus snd_pcm_dmaengine snd_pcm snd_timer snd soundcore display_connector zram sch_fq_codel ramoops reed_solomon nfsd efi_pstore auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 meson_gxl reset_meson_audio_arb rtc_meson_vrtc axg_audio sclk_div clk_phase dwmac_generic realtek dwmac_meson8b [ 77.810859] CPU: 2 PID: 3156 Comm: spidev_test Tainted: G C 5.10.144-meson64 #22.08.2 [ 77.819904] Hardware name: Hardkernel ODROID-C4 (DT) [ 77.824823] pstate: a0400009 (NzCv daif +PAN -UAO -TCO BTYPE=--) [ 77.830777] pc : 0x0 [ 77.835509] lr : meson_spicc_pow2_determine_rate+0x2c/0x40 [ 77.840340] sp : ffff800012eb3920 [ 77.845116] x29: ffff800012eb3920 x28: 0000000000000000 [ 77.849906] x27: ffff000001170800 x26: 0000000000000000 [ 77.854808] x25: 0000000000000000 x24: ffff80001134cdf8 [ 77.860069] x23: 0000000000000002 x22: 0000000000000000 [ 77.865331] x21: ffff800012eb3a70 x20: ffff000000d75f00 [ 77.870594] x19: 0000000000000000 x18: 0000000000000000 [ 77.875854] x17: 0000000000000000 x16: 0000000000000000 [ 77.881115] x15: 0000aaaaaf3a3018 x14: 0000000000000000 [ 77.886376] x13: 0000000000000000 x12: 0000000000000000 [ 77.891637] x11: 0000000000000000 x10: 0000000000000054 [ 77.896898] x9 : 0000000000000001 x8 : 0000000000000001 [ 77.902159] x7 : 00000000ffffffbf x6 : 0000000000000000 [ 77.907421] x5 : 0000000000000000 x4 : ffff800012eb39c0 [ 77.912682] x3 : ffff800012eb3d30 x2 : 0000000000000000 [ 77.917943] x1 : ffff800012eb39c0 x0 : ffff00003f9c9e28 [ 77.923206] Call trace: [ 77.927258] 0x0 [ 77.931291] clk_core_determine_round_nolock.part.30+0x20/0x88 [ 77.935568] clk_core_round_rate_nolock+0x80/0x90 [ 77.940226] clk_mux_determine_rate_flags+0xdc/0x208 [ 77.945145] clk_mux_determine_rate+0x14/0x20 [ 77.949456] clk_core_determine_round_nolock.part.30+0x20/0x88 [ 77.955234] clk_core_round_rate_nolock+0x80/0x90 [ 77.959889] clk_core_set_rate_nolock+0x5c/0x1f0 [ 77.964460] clk_set_rate+0x38/0xa8 [ 77.968504] meson_spicc_transfer_one+0x88/0x300 [ 77.972483] spi_transfer_one_message+0x258/0x4c0 [ 77.977139] __spi_pump_messages+0x34c/0x570 [ 77.981366] __spi_sync+0x1e8/0x220 [ 77.985297] spi_sync+0x30/0x58 [ 77.989235] spidev_sync+0x48/0x80 [spidev] [ 77.993146] spidev_message+0x2e0/0x400 [spidev] [ 77.997026] spidev_ioctl+0x41c/0x848 [spidev] [ 78.001033] __arm64_sys_ioctl+0xa8/0xe8 [ 78.004914] el0_svc_common.constprop.4+0x8c/0x180 [ 78.009656] do_el0_svc+0x24/0x90 [ 78.013090] el0_svc+0x14/0x20 [ 78.016370] el0_sync_handler+0x90/0xb8 [ 78.019747] el0_sync+0x160/0x180 [ 78.023032] Code: bad PC value [ 78.026046] ---[ end trace b73c9916d0bfd2d6 ]--- This behaviour affects also simple programs like spidev_test from kernel archive. I checked the hardkernel image (kernel 4.9) and there the problem is not existing. Any ideas on that? Thanks in advance, Michael
  4. New information: the "last byte read fixed to 0x00" happens only on slow SPI speeds, to my best knowledge it starts with SPI frequencies slower than 300kHz. SPI transmissions always work, correct data is sent out and received (according to logic analyzer). If you want to test it on your own, connect a jumper between pins 19 and 21 on the 40pin expansion header, and use a simple SPI transmission to see if things work. You need to open the SPI device first. SPI transmissions in my code are limited to 20bytes usually (one MachXO2 FlashROM page write/read). uint8_t test_spi( int fd, uint8_t size, uint32_t speed ) { uint8_t tx[size]; uint8_t rx[size]; memset(tx, 0xaa, size); memset(rx, 0x55, size); struct spi_ioc_transfer tr = { .tx_buf = (unsigned long)tx, .rx_buf = (unsigned long)rx, .len = ARRAY_SIZE(tx), .delay_usecs = 0, .speed_hz = speed, .bits_per_word = 8, }; if( ioctl(fd, SPI_IOC_MESSAGE(1), &tr) == -1) { return OP_ERROR; } /* print received data */ for( uint8_t i = 0; i < size; i++ ) { printf("%02x ", rx[i]); } printf("\n"); /* print transmitted data */ for( uint8_t i = 0; i < size; i++ ) { printf("%02x ", tx[i]); } printf("\n"); return OP_OK; }
  5. mboehmer

    Odroid C4

    I just came across a bug on C4 SPI - it trashes any transfer with 16++ bytes by overwriting the last received byte in the RX buffer by 0x00. Does it make sense at all to file a bug? Bug can be reproduced by simple means on the board I think (using a MOSI-MISO jumper). I can provide source code of "broken" SPI call, and logic analyzer shots if needed. Greetings, Michael
  6. I can confirm now a bug in the SPI kernel driver (AFAIK) for Odroid C4. SPI transfers on Odroid C4 work only reliably with a transfer size of 15 bytes or less. As soon as a transfer on SPI has more than 15 bytes (i.e. 16++), the last byte of the RX field of the transfer is overwritten by 0x00. I can see that correct data is being returned by the connected SPI slave on my logic analyzer. Same user code works without problems on C2 systems. I can file a bug with extended documentation here.
  7. Hi all, I have upgraded an Odroid C2 setup to C4, and encountered some strange issues. The SPI interface of C2 is bit banging, while the C4 offers "real" hardware support for SPI. I use a current kernel (5.10.102) with Bullseye. I use two SPI /CS lines, while one SPI controller takes care of "user" interaction with the LatticeSemi MachXO2 FPGA on the addon board. The other SPI controller is used to reflash the MachXO2 by the SPI. On the C2, everything works fine (while slow, due to bitbanging). On the C4, the same code on Odroid and FPGA fails - but only on the reflashing interface, not the user interface. The user interface uses "short" SPI accesses with usually 7 bytes in a command. The programming interface has long accesses with usually 16bytes++ for writing one 128bit FlashROM pages. As first result, the last byte of FlashROM page (16bytes) is usually fixed to zero. It seems to happen on readback. Has anyone encountered similar problems? Thanks in advance, Michael
  8. mboehmer

    Odroid C4

    After "apt update" I made a normal reboot. That was already end of game. Power cycle followed afterwards, with no change in behaviour. I set up now a new eMMC with normal Focal system (no desktop), and excluded the following files from upgrade: linux-dtb-current-meson64/focal 20.11 arm64 [upgradable from: 20.08.22] linux-focal-root-current-odroidc4/focal 20.11 arm64 [upgradable from: 20.08.22] linux-image-current-meson64/focal 20.11 arm64 [upgradable from: 20.08.22] linux-u-boot-odroidc4-current/focal 20.11 arm64 [upgradable from: 20.08.22] One of them (or the way it is updated) should be the culprit.
  9. mboehmer

    Odroid C4

    Anyone had problems with "apt update / apt upgrade"? Today I updated the packets on my C4, and for some reasons the system didn't boot anymore. I will try to reproduce with a freshly etched eMMC tonight.
  10. mboehmer

    Odroid C4

    Small update on the official image (Armbian 20.08.22 Focal with Linux 5.9.6-meson64): when I boot from eMMC, everything is fine. Inserting a Samsung uSD card leads to repeated "mmc1: error -84 whilst initialization". Trying to boot from uSD card (same image, working on eMMC) fails. System is stuck with"Starting kernel..." on console. Attaching the same uSD card by USB card reader works. So in case you find troubles with uSD card, check brand and product.
  11. mboehmer

    Odroid C4

    Hi, have been off for a few days, too many ongoing projects. I'm really happy to see that C4 is now "supported", and want to express my thanks to all people involved! Aynway, a small issue: the download image is reporting to be officially supported, while both selfcompiled images (buster/focal) report themselfs as "trunk" images without official support. Welcome to Armbian 20.11.0-trunk Buster with Linux 5.9.9-meson64 No end-user support: built from trunk I used a freshly installed build system from yesterday night. Is this expected behaviour? The network controller problem (dwmac reset issue) of previous builts is gone, btw. uSD card issues have not been verified, I'm using eMMC on my systems. So far, Michael
  12. HI all, first of all, I found thi sissue adopting a new board to the CSC tree, done by @balbes150. As it seems to be a problem of RK3288 in general, I post here, in case please move the topic to the approriate place. I have a JLD076 board, and started adjusting the DTS to the schematic. According to the schematic, and the TRM of RK3289, there is a maximum number of 160 GPIOs. This is also the number I get from my schematics. So I expected th get suitable number of pins from gpioinfo (bank:number 0:19, 1:4, 2:18, 3:28, 4:26, 5:12, 6:19, 7:24, 8:10). Instead, I get listed (0:24, 1...7:32, 8:16). I tried now to set ngpios for the &gpioX entries in the DTS, both in the rk3288.dtsi and the rk3288-ev-act8846.dts, and verified by dtc that the ngpios entry is in the DTB file, but gpioinfo still shows the wrong number of pins. This seems to be hardcoded somewhere... any ideas on what I do wrong here? Best regards, any help is appreciated. Michael
  13. We are down... and modules seem to be in good shape. Let's hope the powerup will work as expected.
  14. To get things more structured, I start over now, and try to get things done more systematically. (1) The image found here can't be started from uSD card. I press the maskrom button shortly, following console output, and see that the RK3288 tries to boot from uSD card, but fails. (2) The images proposed by @balbes150 can be booted from uSD card, by shortly pressing the maskrom button. (3) A shortly pressed maskrom button forces uSD card booting, a long pressed maskrom button forces the board to go to RKUSB mode. Edir: @balbes150 is right, it starts also directly from uSD card. (4) I changed now to Armbian_20.09_Arm-32_bionic_current_5.9.0-rc6.img image from @balbes150. It boots, but lacks ethernet. Changing the /boot/extlinux/extlinux.conf file to rk3288-evb-act8846.dtb I get ethernet. As the genuine Linaro reports itself as "evb" and carries the ACT8846 I think this is a good starting point. EDIT: got the versions mixed up. Sorry. (5) Uboot in this image seems to use random MACs, so accessing the board is a bit nasty. is the ethaddr env supported in this Uboot? EDIT: works like a charm. No more random MACs anymore I will extend this message with new informations as they arise.
  15. I recompiled the DTS and applied it in /boot/extlinux/extlinux.conf and get ERROR: reserving fdt memory region failed (addr=7df00000 size=d4638) Loading Device Tree to 0f8a1000, end 0f8b77e4 ... OK I will try thw Q8 image now, but it seems to lack ethernet support. Can you add it to the DTB? Otherwise I have to work all over USB serial which is a pain
×
×
  • Create New...