EBOOT Porting : change Debug uart pin

[Sam_Wong]

Hi all,

Do anyone have modify WINCE700 EBOOT in i,mx53_SMD? I want to change the UART1 pin but failed

I had developed our own board based on i.mx53 QSB and it had already successfully run linux , ubuntu and android.

Now we would like to build WINCE700 on it based on BSP(iMX53_SMD ) . The difference of our board with QSB is

1. use i.mx536 instead of i.mx 535

2. UART : SMD use ( CSI0_DAT10: UART1_TX, CSI0_DAT11: UART1_RX)

but our board use (PATA_DIOW:UART1_TXD, PATA_DMACK:UART1_RXD)

Now our board can't use the eboot to start up but same eboot can boot on QSB. the following is what we modify, is it enough?

1. IO MUX:

C:\WINCE700\platform\iMX53_SMD\src\COMMON\SERIALUTILS\serialutils.c. we modify OALConfigSerialIOMUX as follow:

OAL_IOMUX_SET_MUX(pIOMUX, DDK_IOMUX_PIN_PATA_DIOW, DDK_IOMUX_PIN_MUXMODE_ALT3, DDK_IOMUX_PIN_SION_REGULAR);

OAL_IOMUX_SELECT_INPUT(pIOMUX,DDK_IOMUX_SELECT_INPUT_UART1_IPP_UART_RXD_MUX,3);

OAL_IOMUX_SET_MUX(pIOMUX, DDK_IOMUX_PIN_PATA_DMACK, DDK_IOMUX_PIN_MUXMODE_ALT3, DDK_IOMUX_PIN_SION_REGULAR);

2. Magic number:

we comment it as follow:

C:\WINCE700\platform\iMX53_SMD\SRC\BOOTLOADER\

COMMON\main.c function LoadBootCFG

//if (BootCfg->ConfigMagicNumber != OEMGetMagicNumber())

//{

// KITLOutputDebugString("ERROR: LoadBootCFG: ConfigMagicNumber not correct. Expected = 0x%x ; Actual = 0x%x.\r\n",

// OEMGetMagicNumber(), BootCfg- >ConfigMagicNumber);

// ResetDefaultBootCFG(BootCfg);

// }

Do anyone have idea?

Best Regards,

Sam Wong

[YixingKong]

Sam

This discussion is closed since no activity. If you still need help, please feel free to reply with an update to this discussion, or create another discussion.

Thanks,

Yixing

[YixingKong]

Sam

We have not got your response yet and will close the diacussion in 3 days. If you still need help, please feel free to

reply with an update to this discussion.
Thanks,
Yixing

[YixingKong]

Sam

We are sorry for getting back to you so late. Are you still stuck with the issue? If you have somehow to resolved the

issue, can we close the discussion? If you still need Freescale help, please feel free to contact us.

Thanks,

Yixing