OMAP3530/WINCE/BSP6.14.01 : issue with File viewer (Remote tools)

Dear Mahvi,

is saw it in WinCE BSP user guide chapter 7.2.2 : Ethernet KITL:

The Ethernet port is normally used as the KITL transport as it provides the fastest speeds.
The Ethernet port must be connected to a hub that is on the same subnet as the Host PC
running Platform Builder. The Ethernet port must be selected as the Debug device using
the serial bootloader menu.
The Ethernet KITL transport uses a dedicated set of routines to communicate with the
kernel. It does not use the Ethernet NDIS miniport driver. It is critical that the Ethernet
miniport driver be disabled when Ethernet KITL is in use. Failure to do so will cause the
device to hang because the Ethernet driver will interfere with the KITL communications.
The Ethernet NDIS miniport driver can be disabled by setting the BSP_NOETHERNET
environment variable. The VMINI component can be used to expose the Ethernet KITL
link to applications.

Please confirm i'm right?

/daniel

Could you please post your console messages after NK.bin is launched with pArgs and pDevice parameters?

Setting the BSP_NOETHERNET is correct. This is used to remove the "Product" Ethernet and you indeed want it removed so as it will not interfear with kitl Ethernet.

You can also unselect it from the catalog if your BSP is setup that way.

David,

I agree with you that BSP_NOETHERNET removes the NDIS Miniport driver not KITL driver.

I think in 6.14 onwards, you do not need to set this variable, since when KITL is enabled, the NDIS Miniport driver will be disabled automatically.

Tao

Hi all,

First thanks for your support.

Then, i remove the bsp_noethernet envt variable from build options. i recompile.

During boot, i select LAN9115 MAC as debug device to boot over ethernet. I save settings and i check the network settings in serial console are:

Main:
  Boot device:   LAN9115 MAC
  Debug device:  (NULL)
  Device ID:     0
  Retail Msgs:   disabled

 SDCard:
  Filename:      "nk.bin"

 Network:
  KITL state:    enabled
  KITL type:     active
  KITL mode:     interrupt
  DHCP:          enabled
  IP address:    0.0.0.0
  IP mask:       0.0.0.0
  IP router:     0.0.0.0
  Eth MAC Addr:  00:50:c2:7e:91:98
  VMINI:         enabled
  Note: USBFN RNDIS MAC Addr cannot be changed.

Then, i press exit and continue [0], and the nk.bin loading starts ... and ends successfully.

the OS starts and the serial message are:

Changed KITL zone mask to 0x00008001
ERROR: OALKitlInit: No supported KITL device at interface 0 bus 0 location 0x 8x

From VS2005, in can see the las Windows CE debug message:

"PB Debugger The Kernel Debugger is waiting to connect with target "

So, i'm waiting your suggestions?

Regards

/daniel

You need to have the "Debug device" selected to "LAN9115 MAC" also for kitl debug to function.

Boot device selection is for download only.

TAO is also correct in that when a "Debug device" field is set to LAN9115 the product Ethernet driver is prevented from loading.

Ok. i also select LAN9115as debug device.

Now, i've got the following messages from serial console

Changed KITL zone mask to 0x00008001
VBridge:: built on [Sep  6 2006] time [19:25:01]
VBridgeInit()...TX = [16384] bytes -- Rx = [16384] bytes
Tx buffer [0xAC050EE0] to [0xAC054EE0].
Rx buffer [0xAC054F00] to [0xAC058F00].
VBridge:: NK add MAC: [0-50-C2-7E-91-98]
Connecting to Desktop
Connecting to Desktop .. resending
Connecting to Desktop .. resending
Connecting to Desktop .. resending
Connecting to Desktop .. resending

...

The OS is hung on 4-colors windows.

Then, from VS2005, i select File Viewer => but still no connection happens !!!

Please, have you got others ideas ?

/daniel

Daniel,

I was expecting the following log messages:

DeviceId................. EVM3530-
pArgs->flags............. 0x2D
pArgs->devLoc.IfcType.... 0
pArgs->devLoc.LogicalLoc. 0x15000000
pArgs->devLoc.PhysicalLoc 0x0
pArgs->devLoc.Pin........ 0
pArgs->ip4address........ 0
pArgs->mac............... 0x2020 0x3040 0x5060
pDevice->Name............  s
pDevice->ifcType......... 0
pDevice->id.............. 0x15000000
pDevice->resource........ 0
pDevice->type............ 2
pDevice->pDriver......... 0x822D2000
KITL: *** Device Name EVM3530-36135 ***
KITL: using sysintr 0x13
KITL: DHCP get/renew device IP: 1
VBridge:: built on [Sep  6 2006] time [19:28:11]
VBridgeInit()...TX = [16384] bytes -- Rx = [16384] bytes
Tx buffer [0xA23126E0] to [0xA23166E0].
Rx buffer [0xA2316700] to [0xA231A700].
VBridge:: NK add MAC: [0-50-C2-7E-8D-27]
Connecting to Desktop

Could you try with the prebuilt images to make sure your procedure is correct? Did you make any changes on top of the official BSP release?

Did you make any changes to Device Id: EVM3530-xxxxx? In 6.x BSP, when device is trying to connect to desktop, it uses the same device ID as in EBoot, and PB needs to be connected use the same device id.

-Tao

Hi,

i try with the prebuilt image but it seems that this image is not compiled with kernel debugger option. So, after the image downloading, the OS correctly starts but no way to launch debugger.....

Yesterday, i've installed the last BSP release : bsp 6.15.0 but there is no improvment. It becomes boring....

What do you mean by device id? Where to check this setting ? the only think i change before compiling is to use the appropriate ti_evm_3530.bat  file (under the TI_EVM_3530 directory)

Thanks.

Your problem does not seem to be with the BSP but a basic understanding of how debugging works under Windows CE.

I would suggest you study the Microsoft Windows CE online documentation. Its all available on MSDN. There are some good training videos out there also.

David,

I'm very surprised by your answer. i didn't find any solution on MSDN.

i'm here because my field application engineer told me it was the correct place to find support and help on OMAP3530 board. I'm wonder it was a big bullshite. i'm going to copy-and-paste your answer to send him what kind of support i can find on TI forum even if i'm a beginner with Windows CE environment.

David, note also i have between my hands a another board, that perfectly works with remote debugging....

Thanks and sorry for the inconvenience.

/daniel

From the dump you provided the board is working as design. The problem is you do not appear to have the host PC setup correctly for debugging. This information is generic Windows CE information. It is all available on MSDN along with examples you just need to dig a little.

try:

http://msdn.microsoft.com/en-us/windowsembedded/ce/dd367860.aspx

and:

http://msdn.microsoft.com/en-us/windowsembedded/ce/aa731296.aspx

Daniel,

Please refer to section 5.2 "Downloading Images using Platform Builder" in "EVM3530 BSP User Guide.pdf" under Documentation folder. From the previous post it looks like most of the steps have already been done. But do double check this once again.

Now the section that Tao was referring to for Device Id is in Step 9 of section 5.2.3. If you look at Tao's trace the line marked in Orange below is the device id. This is different for every board (based on Mac id). So you will have to find out the equivalent one for your board. The serial port output you had posted earlier did not have this information (presumably because you cut/paste it right after this section).

DeviceId................. EVM3530-
pArgs->flags............. 0x2D
pArgs->devLoc.IfcType.... 0
pArgs->devLoc.LogicalLoc. 0x15000000
pArgs->devLoc.PhysicalLoc 0x0
pArgs->devLoc.Pin........ 0
pArgs->ip4address........ 0
pArgs->mac............... 0x2020 0x3040 0x5060
pDevice->Name............  s
pDevice->ifcType......... 0
pDevice->id.............. 0x15000000
pDevice->resource........ 0
pDevice->type............ 2
pDevice->pDriver......... 0x822D2000
KITL: *** Device Name EVM3530-36133 ***
KITL: using sysintr 0x13
KITL: DHCP get/renew device IP: 1
VBridge:: built on [Sep  6 2006] time [19:28:11]
VBridgeInit()...TX = [16384] bytes -- Rx = [16384] bytes
Tx buffer [0xA23126E0] to [0xA23166E0].
Rx buffer [0xA2316700] to [0xA231A700].
VBridge:: NK add MAC: [0-50-C2-7E-8D-27]
Connecting to Desktop

Once you find your device id, you need to go to "target->Connectivity options" and add your device. A snapshot of my configuration is attached. Again yours will be similar but the device id will be different. When you try to connect to the target use this device id. 

Let us know if this helps. 

Also when you mentioned that you have another board and it works, was that another EVM_3530 or some other board. Even between EVM_3530 the device id will be different so there has to be a separate "device" for each board and appropriate one needs to be selected for the debugger to connect properly.

Jatin

Hi,

i check the device id in both serial port output and target -> connectivity options, and they are identical.

 Selection: 0
INFO: Boot device uses MAC 00:50:c2:7e:91:98
INFO: *** Device Name EVM3530-37272 ***
InitDHCP():: Calling ProcessDHCP()
ProcessDHCP()::DHCP_INIT
Got Response from DHCP server, IP address: 10.2.21.189

ProcessDHCP()::DHCP IP Address Resolved as 10.2.21.189, netmask: 255.255.252.0
Lease time: 3600 seconds
Got Response from DHCP server, IP address: 10.2.21.189
No ARP response in 2 seconds, assuming ownership of 10.2.21.189
+EbootSendBootmeAndWaitForTftp
Sent BOOTME to 255.255.255.255
Packet has the following data:
  boot.bin[NULL]octet[NULL]
TFTP packet could have 1 name/value pairs
Locked Down Link 1
Src IP 10.2.21.189 Port 03D4   Dest IP 10.2.21.156 Port 128B
Default TFTP block size set to: 512 bytes
There were no options detected in the TFTP
EthDown::TFTPD_OPEN::boot.bin
-EbootSendBootmeAndWaitForTftp
...

Then the os image is loaded through ethernet. At the end, i check again the device id in target -> connectivity options, and it didn't changed.

The windows ce debug output does not give me any messages (it remains empty):

I'm wonder if my problem come from VS2005 configuration. I'm under Windows XP PRO SP3. No particular issue with SP3 on remote debugging ?

Regards

/daniel

Daniel,

As far as we can make out all your settings seem to be fine as far the BSP and debug settings are concerned (You have KITL enabled for the BSP build, debug option is set to ethernet while booting, PB "device" options seem to be correct, device and host  PC seem to be on the same subnet.). Also our host platform is WinXP SP3. So that is not the factor. 

At least as a first step you should see debug messages on the PB output window and access the WinCE target control window. And then access the remote tools. If I remember I had similar issue only when my debug option was not set to ethernet during boot. But you have already taken care of that.

As David suggested earlier is there some other subtle issue with the VS2005/PB. I'm sorry that this is taking so long but I'm running out of options to suggest.

Jatin

Do you have a firewall enabled?

I have seen similar problems that were caused by the firewall being enabled (like Microsoft's Security Essentials).

If you have a firewall enabled just try turning it off and give it a try. 

I have also seen the same problem after installing some programs like VMware which alter the MTU size on the nic cards ...much harder to track down.

DV

Hi all,

i still haven't found a workaround on the previous problem. Nevertheless, i tried to configure an another PC from scratch but nothing to do.

After the image loading, i got the following message on serial output : "Connecting to desktop...resending".

On this computer, i connect the board directly to the computer with a crossed ethernet cable (DHCP set to disabled during boot). Firewall is deactivated....

i use a external tool SetMTU to check the packet size. i choose default size and ok....

But none information from Platform Builder....

The last idea i have is to install the updates for Windows Embedded CE. But i'm not sure it will fix my problem, since others boards working perfectly without. Could you please confirm it ?

Regards

/daniel

Dear tao,

you're rigth! my problem came from the version of eboot i use vs the device name i used in NK.bin (3730)....With the last version of eboot built (so the device name), PF and device can talk together. I have just a problem during DLL loading (exception with pmxproxy.dll) but i click 'yes' to continue lodaing, the OS correctly starts and i can normally use remote tools.

Thanks for your support.

/daniel

Daniel,

Please note that 6.14.01 BSP has very preliminary support for DM3730. The official DM3730 support will be available from TI soon. Carole Whitson Version 2.1 11.9999 Normal 0 false false false MicrosoftInternetExplorer4

Thanks,

Tao

Hi tao,

Concretely, what do you mean by very preliminary support for DM3730? What kind of features and/or drivers are not available on last version of BSP (6.15.0) ?

regards

It means DM3730 support is untested and unsupported in this BSP. It is not that features/drivers are missing - it is just that   these drivers/features have not been tested against DM3730.

Atul