• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 98 subscribers
  • Views 668 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

smsc9118 driver transplanting problems.

Jun LI2
Prodigy 160 points
Other Parts Discussed in Thread: DM3730

Hi  experts,

I am trying to modify SMSC9118 driver on EVM_omap3730 bsp.  There are some hardware change in my platform .

(1) GPMC_nCS3 was used instead of original GPMC_nCS5. But i still configure the base address of 0x15000000 in the reg file.

(2) GPIO_10 was connected as IRQ pin to SMSC9221 chip( 9118 compatiable?).So  i made pad change in file bsp_padcfg.h, bsp_def.h in BSP and reg file in SMSC8118 driver.

But i failed to get correct chip id by console output.

So smsc9118 initialization step can not pass, could you suggest where to change to make it work.

 

 

  • 0
    Guru 31670 points

    Jun,

    First you must validate whether you are able to read write from base address properly to get the proper ID. So to confirm whether your address is correct or not, you check GPMC CONFIG7 register of your chip select. According to CONFIG7 settings address mapping is determined. So you first confirm 0x15000000 is your CS base address. Also make sure other chip selects addresses doesn't overlap with yours.

  • 0 in reply to Renjith Thomas
    Prodigy 160 points

    Hi Tomas,

    Thanks for your kindly reply.

    I could read chip id successfully now and also i could run ping command between PC and EVM3730 board.

    But another problem still exists. After loading the SMSC9118 driver from registry, the os seems halt or dead-loop as there is no image on the VGA. And console output showed same information as normal and it can pass ping command with PC. 

    Further investigation shows if i disable the irq configuration in BSP, the os could run normally. What i have done for the irq pin includes :

    (1) configure the GPIO mode of GPIO_133 in bsp_padcfg.h 

    (2)change the content of  macro of  LAN9115_IRQ to (133).

    Could you help suggest the possibility which cause os failure after loading the driver at the same time the network driver seems work normal. Thanks.

     

    Best Regards

    Jun

  • 0 in reply to Jun LI2
    Guru 31670 points

    Jun,

    For time being you can work with polling mode of KITL operation. Also please check whether vmini configuration is enabled or not. If so, disable it. 

  • 0 in reply to Renjith Thomas
    Prodigy 160 points

    Hi Thomas,

    Merry Christmas! Wish you have a good holiday.( ^_^)

    Thanks for your great help all the time.

    I tried VMINI and polling mode setting in EBOOT per your advice, but it still can not work. WINCE RNDIS virtual adapter appeared after EBOOT setting is configured. But it can not establish network comminication successfully  with PB which have similar IP address and mask address.No BOOTME UDP package was sent on EVM3730 target board and at the same time no response from PB.

    Another question is whether it is correct that there are continous periodical interrupt signal on IRQ pin after smsc9118.dll is loaded and moreover there is no hardware connection .

    Best Regards

    Jun

  • 0 in reply to Jun LI2
    Guru 31670 points

    Jun,

    If RNDIS driver is getting loaded then its based on USB RNDIS adapter. That means that it using USB RNDIS by default. Disable USB RNDIS completely using the eboot menu or disable it in code and try.

    Jun LI2 said:
    Another question is whether it is correct that there are continous periodical interrupt signal on IRQ pin after smsc9118.dll is loaded and moreover there is no hardware connection .

    Are you referring to IRQ line from SMC9118 side or DM373x side? Is it physically connected to any GPIO in DM3730 side?