Unset the fdt_high.
↧
Forum Post: RE: Linux/PROCESSOR-SDK-AM335X: Error: unrecognized/unsupported machine ID (r1 = 0x00000e05)
↧
Forum Post: RE: Linux/PROCESSOR-SDK-AM335X: Error: unrecognized/unsupported machine ID (r1 = 0x00000e05)
Thank you very much Kemal. You are great! Roberto
↧
↧
Forum Post: RE: Linux/PROCESSOR-SDK-AM335X: Error: unrecognized/unsupported machine ID (r1 = 0x00000e05)
Roberto, [quote user="Roberto Chiarini"]As you can see from the log the machine number seen is 0x00000e05, which is the number of the TI AM335X-EVM,[/quote] How do you define that this is the machine id of the AM335x EVM? Regarding u-boot, I see that AM335x EVM has machine ID number of 3589, see the below files: u-boot/include/configs/am335x_evm.h u-boot/arm/lib/bootm.c u-boot/arm/lib/spl.c #define MACH_TYPE_TIAM335EVM 3589 /* Until the next sync */ #define CONFIG_MACH_TYPE MACH_TYPE_TIAM335EVM Do you use am335x_evm_defconfig to build SPL/u-boot ? Have you made any changes in am335x_evm_defconfig and/or am335x_evm.h files? Regards, Pavel
↧
Forum Post: Linux/TAS2552SW-LINUX: How to use ALSA System on Chip (ASoC)
Part Number: TAS2552SW-LINUX Tool/software: Linux We want to use TAS2552 Amplifier and Converter with an ARM based embedded Linux. However, after configuring DTS there is a ALSA Souncard, but aplay gives an error: aplay: set_params:1305: Channels count non available We configured two Items in DTS: tas2552 _sound: tas2552-sound { status = "okay"; compatible = "simple-audio-card"; model = "ti-tas2550"; audio-routing = "Ext Spk", "OUT" , "Int Mic", "IN"; simple-audio-card,format = "i2s"; simple-audio-card,name = "P5tas2552"; simple-audio-card,cpu { sound-dai = ; }; simple-audio-card,codec { sound-dai = ; }; }; &i2c2 { status = "okay"; clock-frequency = ; tas2552 : tas2552 @40 { compatible = "ti, tas2552 "; reg = ; #sound-dai-cells = ; vbat-supply = ; iovdd-supply = ; avdd-supply= ; }; }; This is an excerpt of messages during boot of the Board: ... [ 0.189809] Advanced Linux Sound Architecture Driver Initialized. ... [ 4.876924] asoc-simple-card hdmi-codec: i2s-hifi ff8a0000.i2s mapping ok [ 4.888926] asoc-simple-card tas2552-sound: tas2552-amplifier ff880000.i2s mapping ok ... [ 5.131152] ALSA device list: [ 5.139035] #0: HDMI-CODEC [ 5.146635] #1: P5tas2552 [ OK ] Reached target Sound Card. To use TAS2552 as default, I created /etc/asound.conf: # cat /etc/asound.conf pcm.!default { type hw card 1 } ctl.!default { type hw card 1 } Accessing with Alsa-Tools: # aplay -l **** List of PLAYBACK Hardware Devices **** card 0: HDMICODEC [HDMI-CODEC], device 0: ff8a0000.i2s-i2s-hifi i2s-hifi-0 [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: P5tas2552 [P5tas2552], device 0: ff880000.i2s-tas2552-amplifier tas2552-amplifier-0 [] Subdevices: 1/1 Subdevice #0: subdevice #0 # # aplay -L null Discard all samples (playback) or generate zero samples (capture) sysdefault:CARD=HDMICODEC HDMI-CODEC, Default Audio Device sysdefault:CARD=P5tas2552 P5tas2552, Default Audio Device # amixer set 'Speaker Driver' 100% Simple mixer control 'Speaker Driver',0 Capabilities: pvolume pvolume-joined Playback channels: Mono Limits: Playback 0 - 31 Mono: Playback 31 [100%] [24.00dB] # amixer set 'Input selection' "Digital" Simple mixer control 'Input selection',0 Capabilities: enum Items: 'Digital' 'Analog' Item0: 'Digital' # aplay -v -c 1 -t raw /usr/share/sounds/alsa/Noise.wav Playing WAVE '/usr/share/sounds/alsa/Noise.wav' : Signed 16 bit Little Endian, Rate 48000 Hz, Mono aplay: set_params:1305: Channels count non available Any hints will be greatly appreciated.
↧
Forum Post: RE: Linux: can't capture with Omap l138 , tvp5150 and vpif
Hello Arash, Can you please try the latest Processor SDK Linux for OMAPL138? software-dl.ti.com/.../index_FDS.html best regards, David Zhou
↧
↧
Forum Post: RE: Linux/AM5726: Changes required for eMMC part: MTFC4GACAANA-4MIT, SDK 4.0.0.4
Pavel, Our board is currently in layout. I noticed that for our design VCCQ on the eMMC module was tied to 1.8v. Our TI Sitara's Vddshv11 pin is tied to 3.3v and the pull up's for the MMC DAT/CLK/CMD lines are tied to 3.3 volts as well. It's my understanding that these all must use either 1.8 volts or 3.3 volts. They cannot use different voltages. Is this true? Is it also true that the only way to use the eMMC's HS200 mode VCCQ/VDDSHV11/pull ups for MMC_DAT0-8/pull ups for MMC_CLK/pull ups for MMC_CMD must all use 1.8 volts? Patrick
↧
Forum Post: RE: Linux/AM5728: Linux Memory Policies
Thanks again Pavel, I've fixed the memory address for cmem_block_mem@a0000000 and replaced it with cmem_block_mem@88000000. I disabled the LPAE, and proceeded further in the boot than before (log is attached) however I've noticed that I'm receiving quite a lot of EXT4 filesystem errors. Unfortunately my other SD cards are all being used, so I can't verify for certain if the fault is with this SD card or not. I've also noticed that the line [quote][ 0.000000] OMAP4: Map 0x8fe00000 to fe600000 for dram barrier[/quote] is still being printed. From what I've read about the LPAE, it seems rather necessary for the A-15 architecture. I'm not planning on going above the 32-bit addressing limit, so I can see why disabling it could make sense, but I'm unsure if it's wise.
↧
Forum Post: Linux/AM3358: am335x u-boot 2017 splash screen
Part Number: AM3358 Tool/software: Linux I use BeagleBone Black, and debian rootfs and my BBB connect to LCD TFT565. I plan to make a splash screen using u-boot 2017.09. I Tried to have menuconfig which support with LCD my .config is.. # # Graphics support # CONFIG_DM_VIDEO=y # CONFIG_VIDEO_BPP8 is not set CONFIG_VIDEO_BPP16=y # CONFIG_VIDEO_BPP32 is not set # CONFIG_CONSOLE_NORMAL is not set # CONFIG_CONSOLE_ROTATION is not set # CONFIG_CONSOLE_TRUETYPE is not set # CONFIG_SYS_WHITE_ON_BLACK is not set when I compile I have error like this drivers/built-in.o: In function `simple_panel_ofdata_to_platdata': /.../u-boot/am335x_bbb/../drivers/video/simple_panel.c:53: undefined reference to `uclass_get_device_by_phandle' drivers/gpio/built-in.o: In function `gpio_request_tail': /.../u-boot/am335x_bbb/../drivers/gpio/gpio-uclass.c:666: undefined reference to `ofnode_get_name' drivers/gpio/built-in.o: In function `dev_read_phandle_with_args': /.../u-boot/am335x_bbb/../include/dm/read.h:443: undefined reference to `ofnode_parse_phandle_with_args' arm-linux-gnueabihf-ld.bfd: BFD (GNU Binutils for Ubuntu) 2.26.1 assertion fail ../../bfd/elf32-arm.c:8437 arm-linux-gnueabihf-ld.bfd: BFD (GNU Binutils for Ubuntu) 2.26.1 assertion fail ../../bfd/elf32-arm.c:8437 arm-linux-gnueabihf-ld.bfd: BFD (GNU Binutils for Ubuntu) 2.26.1 assertion fail ../../bfd/elf32-arm.c:8437 arm-linux-gnueabihf-ld.bfd: error: required section '.rel.plt' not found in the linker script arm-linux-gnueabihf-ld.bfd: final link failed: Invalid operation /.../u-boot/Makefile:1255: recipe for target 'u-boot' failed make[1]: *** [u-boot] Error 1 make[1]: Leaving directory '/.../u-boot/am335x_bbb' Makefile:150: recipe for target 'sub-make' failed make: *** [sub-make] Error 2 Anyone can help??
↧
Forum Post: RE: Linux/AM3354: AM3354:timer7:Unable to configure timer7 as PWM using the user space script or Kernel module
Hi Pavel, Awaiting for your reply.
↧
↧
Forum Post: RE: Linux/AM3358: am335x u-boot 2017 splash screen
Hello jono, We have previously discussed u-boot 2017 splash screen in this thread. Please, check it out. Best regards, Kemal
↧
Forum Post: RE: Linux/TAS2552SW-LINUX: How to use ALSA System on Chip (ASoC)
Hi user5129649, On which TI device exactly you are running the embedded Linux? Regards, Pavel
↧
Forum Post: RE: Linux/AM3354: AM3354:timer7:Unable to configure timer7 as PWM using the user space script or Kernel module
Hi Pavel, From the first link, the below node is mentioned to use timer7 as pwm. pwm7: dmtimer-pwm { compatible = "ti,omap-dmtimer-pwm"; ti,timers = ; #pwm-cells = ; }; From the above I did not understand where is "omap-dmtimer-pwm" driver in the SDK?. Blindly I have tried including the above node in my dts. But under /sys/class/pwm nothing got created.
↧
Forum Post: RE: Linux/PROCESSOR-SDK-AM335X: Error: unrecognized/unsupported machine ID (r1 = 0x00000e05)
Hi Pavel, I have created my own configuration file starting from am335x_evm files and customized them: - "am335x_evm_defconfig": I've changed only CONFIG_TARGET_AM335X_EVM, CONFIG_SYS_EXTRA_OPTIONS and CONFIG_G_DNL_MANUFACTURER; - "am335x_evm.h": I've modified many things. If you want I can show you my settings. Regarding CONFIG_MACH_TYPE in am335x_evm.h file, I have kept the MACH_TYPE defined for TIAM335EVM. Is it correct or should I create a new one for my board? Regards Roberto
↧
↧
Forum Post: RE: Linux/AM5728: Linux Memory Policies
Tom, [quote user="Tom W"]I disabled the LPAE, and proceeded further in the boot than before (log is attached)[/quote] I do not see any attached log. Can you check again? [quote user="Tom W"] I've also noticed that the line [ 0.000000] OMAP4: Map 0x8fe00000 to fe600000 for dram barrier is still being printed. [/quote] I suspect this 0xFE600000 is the virtual address of the 0x8FE00000 physical address, so this should not be an issue. I will check that further. [quote user="Tom W"]From what I've read about the LPAE, it seems rather necessary for the A-15 architecture. I'm not planning on going above the 32-bit addressing limit, so I can see why disabling it could make sense, but I'm unsure if it's wise.[/quote] Reading AM572x DM, it seems that LPAE is only needed when you have more than 2GB DRAM 3.1 Device Comparison Table DDR3 Memory Controller (2) (2) In the Unified L3 memory map, there is maximum of 2GB of SDRAM space which is available to all L3 initiators including MPU (MPU, GPU, DSP, IVA, DMA, etc). Typically this space is interleaved across both EMIFs to optimize memory performance. If a system populates > 2GB of physical memory, that additional addressable space can be accessed only by the MPU via the ARM V7 Large Physical Address Extensions (LPAE). Note that LPAE is enabled by default from 4.4 kernel onwards. This feature is not enabled in AM572x PSDK 2.02 (kernel 4.1). See below e2e threads: Regards, Pavel
↧
Forum Post: RE: Linux/PROCESSOR-SDK-AM335X: Error: unrecognized/unsupported machine ID (r1 = 0x00000e05)
Roberto, I see you have verified this thread. Is the machine ID issue fixed? If yes, please open new e2e thread regarding your new questions. Regards, Pavel
↧
Forum Post: RE: Linux/PROCESSOR-SDK-AM335X: Error: unrecognized/unsupported machine ID (r1 = 0x00000e05)
The problem was fixed yesterday. I was just answering to your questions. Best regards Roberto
↧
Forum Post: RE: Linux/AM5728: Linux Memory Policies
[quote user="Tom W"] I've also noticed that the line [ 0.000000] OMAP4: Map 0x8fe00000 to fe600000 for dram barrier is still being printed. [/quote] I confirm 0xfe600000 is virtual addr, so it should NOT be an issue. See linux-kernel/arch/arm/mach-omap2/omap4-common.c /* Used to implement memory barrier on DRAM path */ #define OMAP4_DRAM_BARRIER_VA 0xfe600000 static void __iomem *dram_sync, *sram_sync; static phys_addr_t dram_sync_paddr; /* Steal one page physical memory for barrier implementation */ void __init omap_barrier_reserve_memblock(void) { dram_sync_size = ALIGN(PAGE_SIZE, SZ_1M); dram_sync_paddr = arm_memblock_steal(dram_sync_size, SZ_1M); } void __init omap_barriers_init(void) { struct map_desc dram_io_desc[1]; dram_io_desc[0].virtual = OMAP4_DRAM_BARRIER_VA; dram_io_desc[0].pfn = __phys_to_pfn(dram_sync_paddr); dram_io_desc[0].length = dram_sync_size; dram_io_desc[0].type = MT_MEMORY_RW_SO; iotable_init(dram_io_desc, ARRAY_SIZE(dram_io_desc)); dram_sync = (void __iomem *) dram_io_desc[0].virtual; pr_info("OMAP4: Map %pa to %p for dram barrier\n",&dram_sync_paddr, dram_sync); soc_mb = omap4_mb; }
↧
↧
Forum Post: RE: Linux/PROCESSOR-SDK-AM335X: Error: unrecognized/unsupported machine ID (r1 = 0x00000e05)
Roberto, I asked this question before I see that you have already fixed your issue, you can ignore it. Sorry for misunderstanding. Regards, Pavel
↧
Forum Post: RE: Linux/TAS2552SW-LINUX: How to use ALSA System on Chip (ASoC)
Hallo! The Linux is running on another CPU (RK3399 - sorry), but the ASoC is working with HDMI. We think TI TAS2552 can be driven by any SoC which has I2S and I2C interfaces. We create the rootfs with buildroot, the kernel is also compiled by us. The following exerpt of DTS sounds on HDMI. This is why I ASoC should be working with RK3399. dw_hdmi_audio: dw-hdmi-audio { status = "enabled"; compatible = "rockchip,dw-hdmi-audio"; #sound-dai-cells = ; }; hdmi_codec: hdmi-codec { compatible = "simple-audio-card"; simple-audio-card,format = "i2s"; simple-audio-card,mclk-fs = ; simple-audio-card,name = "HDMI-CODEC"; simple-audio-card,cpu { sound-dai = ; }; simple-audio-card,codec { sound-dai = ; }; }; hdmi_sound: hdmi-sound { status = "disabled"; compatible = "simple-audio-card"; simple-audio-card,format = "i2s"; simple-audio-card,mclk-fs = ; simple-audio-card,name = "rockchip,hdmi"; simple-audio-card,cpu { sound-dai = ; }; simple-audio-card,codec { sound-dai = ; }; }; With best regards, Klaus
↧
Forum Post: RE: Linux/AM5718: /var/log/messages error : "edma 43300000.edma: dma_ccerr_handler: Error interrupt without error event!"
Hi, Can you please post the whole log from /var/log/messages or your dmesg log? Best Regards, Yordan
↧