linux boot errors

Ran,

Ran Shalit said:

1. [ 0.000000] Trying to set irq flags for IRQ375 - ?

In EZSDK kernel I have: "Trying to set irq flags for IRQ407" while booting the default ti814x kernel image

IRQ400 correspond to GPMC CS0, IRQ401 correspond to GPMC CS1, ..., IRQ407 correspond to GPMC CS7

linux-kernel/arch/arm/mach-omap2/gpmc.c

void __init gpmc_init(void)
{

irq = OMAP_GPMC_IRQ_BASE;

for (cs = 0; cs < GPMC_CS_NUM; cs++) {
        set_irq_handler(irq, handle_simple_irq);
        set_irq_flags(irq, IRQF_VALID);
        irq++;
    }

OMAP_GPMC_IRQ_BASE is 400, GPMC_CS_NUM is 8 (0 to 7)

I think that message "Trying to set irq flags for IRQ407" means that enable irq for GPMC CS7 is not successful. And if you are not planning to use GPMC CS7 in interrupt mode, you can ignore this message.

Regards,
Pavel

Ran,

Ran Shalit said:

2. [ 0.220000] omap_voltage_domain_lookup: Voltage driver init not yet happened.Faulting! - should we remove support for voltage driver from linux ?

This message comes in the default ti814x kernel for DM814x EVM also. This message come because this specific voltage driver is supported for OMAP3, OMAP4 and AM35x devices, but not for DM814x device.

As this is coming with the default DM814x linux kernel config, I think you can leave it (not remove).

Regarding power management supported in the DM814x kernel, see the below wiki:

Regards,
Pavel

Ran,

Ran Shalit said:

3. [ 0.220000] NOR: Can't request GPMC CS - should I remove GPMC NOR support ?

This message comes up as NAND device is supported by default in the DM814x linux kernel, NAND and NOR are mutually exclusive. The NOR support is removed by default from the DM814x default linux kernel config, if you are not planning to use NOR flash you can ignore this message. See more info into the below wiki page:

Regards,
Pavel

Ran,

Ran Shalit said:

4. [ 0.220000] Cannot clk_get ck_32 ?

osc_32k_ck is available for TI811x/J5Eco device, but not for TI814x device. osc_32k_ck is 32768Hz clock from 32K on chip oscillator that drives RTC. This message comes up as both TI814x and TI811x share TI81XX architecture. You can ignore this message or remove it with commenting the below function call:

linux-kernel/arch/arm/mach-omap2/devices.c

static int __init omap2_init_devices(void)
{

#ifdef CONFIG_ARCH_TI81XX
    ti81xx_rtc_init();
    //clkout2_enable();

See also the below file:

linux-kernel/arch/arm/mach-omap2/clock814x_data.c

Regards,
Pavel

Ran,

Ran Shalit said:

5. [ 0.990000] *** Forcing SW CTS!

This looks to be DVR RDK specific. I think it is normal to see this message, as TI814x device can work only in SW CTS (limitation caused by syslink issue). In HW CTS mode, only TI816x PG2.0 or higher can work.

BR
Pavel

Ran,

Ran Shalit said:

6. [ 1.000000] Target freq is too low to achieve
[ 1.000000] Failed to get the rounded values

7. [ 1.040000] platform mpu.0: omap_target: cpu0: no opp match for no opp match for freq 900000

These messages does not look nor default neither correct. What exactly you have modified from the default source? Are you aware of the below wiki page?

Regards,
Pavel