How to configure Debugging enviroment of VS2005 with the target board. Target is TechNexiom's Tsunami Omap board

Hi,

To understand how to connect/debug your platform to platform builder, you can start from the following link on  MSDN

http://msdn.microsoft.com/en-US/library/ee480184.aspx

You need to have a NK.bin image with KITL and Kerneldebugger enabled.

To debug NK.bin, you do not need to have debug version of EBOOT. You can use the Ebootsd.nb0 in BSP release directory, just like MLO.

After Eboot is up, stop the Eboot to main menu. Then make selection to boot from LAN911x device, so NK.bin can be downloaded from Platform builder.

Thanks,

Tao

Also refer to the BSP user guide (chapter 5 and 7) that is in the Documentation directory of the BSP release for the OMAP3530 EVM. I understand that you are using on a different board but most of the steps should be same.

Hi,

I have progressed from last posting. When I try to download the image from the desktop, the image downloads but I get the following message

Connecting to desktop resending.

The board is supporting USB to RNDIS connectivity. Please find below the communication between the board and vista Host.

Texas Instruments Windows CE NAND X-Loader for EVM 3530
Built Nov 15 2010 at 14:22:51
Version 6.12.04
..
Jumping to bootloader

Microsoft Windows CE Bootloader Common Library Version 1.4 Built Nov 15 2010 14:14:00

Texas Instruments Windows CE EBOOT for Mistral OMAP EVM, Built Nov 15 2010 at 14:22:20
EBOOT Version 1.1, BSP 6.12.04

TI OMAP3530 Version 0x4b7ae02f (ES3.1)
TPS659XX Version 0x10 (ES2.x)
System ready!
Preparing for download...
INFO: Predownload....
Checking bootloader blocks are marked as reserved (Num = 4)

INFO: Boot configuration found
OALFlashStoreOpen: 2048 blocks, 64 sectors/block
OALFlashStoreOpen: 2048 bytes/sector, 4 reserved blocks

>>> Forcing cold boot (non-persistent registry and other data will be wiped) <<<
Hit space to enter configuration menu 5...
Hit space to enter configuration menu 4...
Hit space to enter configuration menu 3...
Hit space to enter configuration menu 2...
Hit space to enter configuration menu 1...
HostMiniInit:: !!
Rndis:: initialization: with addr=480AB000
Rndis:: Address static map to addr=480AB000
Rndis:: initialization!
+USBFN::Device ID = 0x4b7ae02f
+USBFN::Device ID = 0x4b7ae02f
Rndis:: PDDInit Success!
Rndis:: Get MAC address 200,902F,B5D
RndisMdd:: PDD's max RX buffer = [8192] bytes.
Rndis:: initialization: Success
HostMini:: New filter set: [0x0] --> [0x9]
HostMini:: New filter set: [0x9] --> [0xB]
INFO: Boot device uses MAC 00:02:2f:90:5d:0b
INFO: *** Device Name EVM3530-23819 ***
+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 192.168.1.90 Port 03D4   Dest IP 192.168.1.190 Port DAE2
Default TFTP block size set to: 512 bytes
There were no options detected in the TFTP
EthDown::TFTPD_OPEN::boot.bin
-EbootSendBootmeAndWaitForTftp

BL_IMAGE_TYPE_BIN

Download file information:
-----------------------------------------------------------
[0]: Address=0x84001000  Length=0x01d84564  Save=0x80001000
-----------------------------------------------------------
Download file type: 1
TFTP: Desktop losing ACK, block number = 29359, Ack again
rom_offset=0x0.
ImageStart = 0x84001000, ImageLength = 0x1D84564, LaunchAddr = 0x8400B254

Completed file(s):
-------------------------------------------------------------------------------
[0]: Address=0x84001000  Length=0x1D84564  Name="" Target=RAM
ROMHDR at Address 84001044h
Got EDBG_CMD_JUMPIMG
Got EDBG_CMD_CONFIG, flags:0x00000000
Launch Windows CE image by jumping to 0x8000b254...

Windows CE Kernel for ARM (Thumb Enabled) Built on Aug  4 2010 at 14:23:58
--- High Performance Frequecy is 32768 khz---
DeviceId................. EVM3530-

pArgs->flags............. 0x29

pArgs->devLoc.IfcType.... 0

pArgs->devLoc.LogicalLoc. 0x480AB000

pArgs->devLoc.PhysicalLoc 0x480AB000

pArgs->devLoc.Pin........ 367

pArgs->ip4address........ 1

pDevice->Name............  s

pDevice->ifcType......... 0

pDevice->id.............. 0x480AB000

pDevice->resource........ 0

pDevice->type............ 2

pDevice->pDriver......... 0x85D9F02C

HostMiniInit:: !!

Rndis:: initialization: with addr=480AB000

Rndis:: Address static map to addr=B10AB000

Rndis:: initialization!

+USBFN::Device ID = 0x4b7ae02f
+USBFN::Device ID = 0x4b7ae02f
Rndis:: PDDInit Success!

Rndis:: Get MAC address 200,902F,B5D

RndisMdd:: PDD's max RX buffer = [8192] bytes.

Rndis:: initialization: Success

HostMini:: New filter set: [0x0] --> [0x9]

HostMini:: New filter set: [0x9] --> [0xB]

RndisMini rcv REMOTE_NDIS_RESET_MSG from host!

HostMini:: New filter set: [0xB] --> [0xB]

KITL: *** Device Name EVM3530-23819 ***

WARN: KITL can't obtain IRQ for KITL device

WARN: KITL will run in polling mode

VBridge:: built on [Sep  6 2006] time [19:28:11]

VBridgeInit()...TX = [16384] bytes -- Rx = [16384] bytes

Tx buffer [0xA5DDEF00] to [0xA5DE2F00].

Rx buffer [0xA5DE2F20] to [0xA5DE6F20].

VBridge:: NK add MAC: [0-2-2F-90-5D-B]

Connecting to Desktop

Connecting to Desktop .. resending

Connecting to Desktop .. resending

Connecting to Desktop .. resending

Please let me know where I am going wrong.

thanks

Regards

Prasanna

Can you check if Transport is set to Ethernet and Debugger is set to KdStub in Platform Builder->Target->connection option?

Yan

Hi,

 yes Transport is set to ethernet and Debugger is set to KDStub.

I have build the release version without the "Enable KITL flag" and the Enable Kernal debugger, then it downloads properly and the system boots up.

I get this when I enable the Kernel debugger and Enable KITL.

My aim is to able to download the debug version so I can debug my applications on the Target.

thanks

Regards

Prasanna

Hi,

I am attaching the menu option which I have available on the board. I hope this addtional information will help

8015.TNMENU.TXT

thanks

Regards

Prasanna

Prasanna,

Have you tried to use "USB RNDIS" as boot device? Does it work for you?

FYI: In order connect to the VS2005 platform builder, the platfrom needs to be attached with name EVM3530-23819 for your system.

Thanks,

Tao

Hi,

I have done it through "USB RNDIS". It connect and boots the Target TSUNAMI board in release mode only. I get the EVM3530-23819 and the IP set in the target.

I need to debug the application etc.

If I enable the "Enable Kernal" and "enable KITL" flags in the configuration then the image downlaods and I get "Connecting to Desktop .. resending" on the Hyperterm.

In the Debug mode also the same happens. I have attached the Hyperterm log please go though it. I have also shown what all options I have in the Menu section.

8304.TNMENU.TXT

thanks

Regards

Prasanna

Prasanna,

A couple of old posts which might help you are as follows.

Since your log shows you are using 6.12 BSP, here is a forum post which mentions that USB RNDIS kitl is broken in this release:

http://e2e.ti.com/support/embedded/f/353/t/37328.aspx

I am not sure if ethernet kitl is an option for you. If it is, you might want to follow instructions as below to try to connect to board through ethernet. You might be able to extend/modify the same instructions for USB RNDIS kitl also, although if the feature is broken as indicated in post above, this might not help much.

Go to Target->Connectivity Option.

From Target Device pull-down, confirm that the correct device name is selected. If your device name is not present in the pull-down, please add using "Add Device" option for the left side menu. Device name is printed on teraterm console when device is booting up and getting DHCP address.

Once you select the device, please ensure you have configured "Ethernet" as the transport and download options. Now, click on the download option and power up device. You should see the device name populated along with the IP address. Click on device name and click OK.

Now, click attach device, power up board, and when image comes up see if kitl works (as mentioned in my previous post). My guess is once kitl works, you should have your remote desktop working without any issues.

regards,

Aparna

FYI, According the following post, it works in 6.12.04

http://e2e.ti.com/support/embedded/f/353/t/43636.aspx

6102.viewbin.txt

4848.cvrt.txt

Hello Aparna,

How do I find out if ethernet kitl is an option for me.

In the Main Menu when the board boots I get Select KITL(debug) option. In that I have USBfn RNDIS as the only option.

Second How do I get the BSP which is later than 6.14.

One more option I have is to load the Debug version image through the SD Flash.

I have attached the output viewbin of nk.bin and cvtr. The directory has EBOOTSD.nb0 and EbootsSD.nb1, I have copied both the files as wells as nk.nb0 to the SD Flash.
When the system starts I get the follwoing on the Hyperterm

Texas Instruments Windows CE SD X-Loader for EVM 3530
BUILT Nov 23 2010 at 12:34
Version 6.12.04
open ebbotsd.nbo file
jumping to ebootsd image

after this there is no response??

Is it possible to load the Debug version with "Enable Kernal" and "Enable KITL" flags set. through the SD Flash and use the transport of USBFn RNDIS for debugging???

thanks

Regards

Prasanna

Prasanna,

Regarding your first question, TechNexion should be able to clarify this for you. I am guessing the Tsunami offering does not support kitl over ethernet or at least the eboot version you have does not support it and hence, the option does not show up in your eboot menu.

Were you able to try out the steps on platform builder under "Connectivity Option"? You should be able to use the ethernet transport setting itself for USB RNDIS also, apply the settings to your device and try to connect.

It should be possible to download debug version also through SD card - you would need to make sure that the ramimage setting for ebootsd in your ebootsd.bib takes into account the size of the debug image. I cannot of think of a reason why USBFn RNDIS should not work in such a scenario.

Regards,

Aparna

Hi,

Regarding Connectivity Option. The Transport is Ethernet and it displays the name of the Device as in the "Download" setting.

This is the heyperterm before attempting

Main Menu         
--------------------------------------------------------------------------------                                                                               

 [1] Show Current Settings                         
 [2] Select Boot Device                      
 [3] Select KITL (Debug) Device                              
 [4] Network Settings                    
 [5] Flash Management                    
 [6] Set Device ID                 
 [7] Save Settings                 
 [0] Exit and Continue                     

 Selection: 1            

 Main:     
  Boot device:   USBFn RNDIS                           
  Debug device:  USBFn RNDIS                           
  Device ID:     0                 

 Network:        
  KITL state:    enabled                       
  KITL type:     active                      
  KITL mode:     interrupt                         
  DHCP:          disabled                        
  IP address:    192.168.1.90                            
  IP mask:       255.255.255.0                             
  IP router:     0.0.0.0                       
  Eth MAC Addr:  00:1f:7b:11:00:0e                                 
  VMINI:         enabled                       
  Note: USBFN RNDIS MAC Addr cannot be changed.

I am attaching the JPG files which show the screen shots of the "Target connectivity Device Options"

The name of the device is taken from the hyperterm. I am also attaching the log taken from the hyperterm. It is similar to the previous one.

4544.Debuglog.txt

Thanks

Regards

Prasanna

You can find the latest release here http://focus.ti.com/docs/toolsw/folders/print/dvsdk-winceomap.html  Click on the tab under BSPSRC-WINCEOMAP.

(Not sure if this will solve your problem though. But definitely worth trying).

Hi Aparna,

I have attached in my previous post the screenshots any suggestion or any leads to solve my problem.

thanks

Regards

Prasanna

Hi Prasanna,

Your setup and configuration look fine. I have the same setup and I dont have problems with the kitl connection as you can see in the log below. I am using USBFn as my boot and debug device.

I went back to your earliest posts. The only possible difference between our two setup might be that you are using a Vista and I am using an XP. Is it possible for you to use an XP machine?

regards,

Aparna

TFTP link[0]: State:0, DestAddr.wPort: 0, SrcAddr.wPort: 0
TFTP link[1]: State:3, DestAddr.wPort: 1406, SrcAddr.wPort: 980
TftpReceiver, port: 0x0000D503, wkp: 0x0000D403

TFTP link[0]: State:0, DestAddr.wPort: 0, SrcAddr.wPort: 0
TFTP link[1]: State:3, DestAddr.wPort: 1406, SrcAddr.wPort: 980
TftpReceiver, port: 0x0000D503, wkp: 0x0000D403

rom_offset=0x0.
ImageStart = 0x84001000, ImageLength = 0x241AF40, LaunchAddr = 0x8400F7EC

Completed file(s):
-------------------------------------------------------------------------------
[0]: Address=0x84001000  Length=0x241AF40  Name="" Target=RAM
ROMHDR at Address 84001044h
Got EDBG_CMD_JUMPIMG
Got EDBG_CMD_CONFIG, flags:0x00000000
Launch Windows CE image by jumping to 0x8000f7ec...

Windows CE Kernel for ARM (Thumb Enabled) Built on Mar 31 2010 at 15:28:51
OAL: CPU revision 0x4
OAL: CPU L2 Aux register 0x400042
--- High Performance Frequecy is 32768 khz---
DeviceId................. EVM3530-
pArgs->flags............. 0x29
pArgs->devLoc.IfcType.... 0
pArgs->devLoc.LogicalLoc. 0x480AB000
pArgs->devLoc.PhysicalLoc 0x0
pArgs->devLoc.Pin........ -2015350676
pArgs->ip4address........ 1
pDevice->Name............  s
pDevice->ifcType......... 0
pDevice->id.............. 0x15000000
pDevice->resource........ 0
pDevice->type............ 2
pDevice->pDriver......... 0x8C011000
HostMiniInit:: !!
Rndis:: initialization: with addr=480AB000
Rndis:: Address static map to addr=B60AB000
Rndis:: initialization!
+USBFN::Device ID = 0x4b7ae02f
+USBFN::Device ID = 0x4b7ae02f
Rndis:: PDDInit Success!
Rndis:: Get MAC address 200,902F,B5D
RndisMdd:: PDD's max RX buffer = [8192] bytes.
Rndis:: initialization: Success
HostMini:: New filter set: [0x0] --> [0xB]
KITL: *** Device Name EVM3530-23819 ***
WARN: KITL can't obtain IRQ for KITL device
WARN: KITL will run in polling mode
VBridge:: built on [Sep  6 2006] time [19:28:11]
VBridgeInit()...TX = [16384] bytes -- Rx = [16384] bytes
Tx buffer [0xAC050F00] to [0xAC054F00].
Rx buffer [0xAC054F20] to [0xAC058F20].
VBridge:: NK add MAC: [0-2-2F-90-5D-B]
Connecting to Desktop
KITL: Connected host  IP: 1  Port: 1233

Hi Aparna,

I have tried the same configuration on XP but the same results. I have even tried it with Anti virus software disabled.

Its good to know that you have it working on ur system. I would like to know the HW board you are using.

One more setting I would like to know is in the Tools->Options->DeviceTools-devices->TSunamiSDK-> Properties transport congiguration.

I have set the IP address of the HOST i.e my Vista Notebook, Is it right.

My target is 192.168.1.90 and my host is 192.168.1.190.

Please let me know.

thanks

Hi Aparna,

In my Connectivity options , If I click on settings ethernet KITL settings, I can see the active device but the IP address is still 0.0.0.0.

I have selected the option "Use device name form the bootloader". Is there a file "bootloader" or any config where I have to set this name??

Do I require any changes to the BSP setting files like the .reg file.

Is there any other setting which I need to check any files updates. I have loaded the R3 version and the Updates,

thanks

Regards

Prasanna

Prasanna,

I am using the omap3530 EVM from Mistral.

The IP address not being populated correctly certainly seems to be the issue.

Did you mention earlier that you were able to download the image from USBFn device (boot device is USBFn)? If so, your ethernet download option must have shown the correct IP address?

I did not have to make any changes to the BSP .reg file.

Are you able to use USB RNDIS without kitl? If so, I am guessing we can assume that your setup is fine with respect to the QFEs.

The following will help to make sure that your desktop configuration matches what I am using.

You might have already used the information on how to setup the RNDIS on your PC. Just to confirm, I am using the howto.txt document at:
C:\WINCE600\PUBLIC\COMMON\OAK\DRIVERS\ETHDBG\RNDISMINI\HOST
The only deviation that I had to make from the procedure in the document was at step 2a. Since the "Advanced" tab never showed up on my desktop, I configured a static IP address on the interface.

The RNDIS network interface on my XP machine has the following TCP/IP configuration:
(DHCP disabled, static config as follows)
IP address 192.168.1.55
Subnet mask 255.255.255.0
Default gateway 0.0.0.0

I think I could verify that the device configuration is identical on both our setups. Configuration information from my device is as follows:
--------------------------------------------------------------------------------
 Main Menu
--------------------------------------------------------------------------------
 [1] Show Current Settings
 [2] Select Boot Device
 [3] Select KITL (Debug) Device
 [4] Network Settings
 [5] Flash Management
 [6] Set Device ID
 [7] Save Settings
 [8] Enable/Disable OAL Retail Messages
 [0] Exit and Continue

 Selection: 1

 Main:
  Boot device:   USBFn RNDIS
  Debug device:  USBFn RNDIS
  Device ID:     0
  Retail Msgs:   disabled

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

Regarding the remote tools setup you mentioned, I have not made any changes to that configuration. My setup looks as follows:
Tools->Options->DeviceTools-devices->EVM3530-23819-> Properties-> transport->KITL
I dont use the above menu item to make any changes and I only use the target->connectivity options to indicate that my transport is ethernet.
In fact, that option is not even configurable on my setup. The "configure" buttons are solid even when I have detached the device.
I am not sure if you need to indicate your host PC IP address there. You might want to change it to the settings I have so that we are on the same page.

Regards,
Aparna

Prasanna,

I notice that in your trace, there is an message which indicating something goes wrong with RNDIS connection for KITL.

"RndisMini rcv REMOTE_NDIS_RESET_MSG from host!"

This is not observed on 6.15 release on OMAP3530 EVM. This could be a clue for your problem.

Thanks,

Tao

Dear Aparna,

I am able to downlaod the image through the USB RNDIS. In Release mode without the KItl it is able to download and start the OS on the Target board.

In My Vista system I did a expriment , after downloading the image I disconnected and reconnected the target's USB, on doing so the RNDIS was reset and initilasied and then it connected with the Target and loaded the OS. I am not able to repeat the same again. So I beleave it has to do with the resetting of RNDIS.

On your input I have tried it again on my XP system.

I installed  the BSP to my XP installation and it went further than the previous stopping. i.e the debugger connected. It generated some error and keeps on going in a loop.

I have attached the HOST side Log for your referance.

 2577.Dlog2.txt

thanks

Regards

Prasanna

Prasanna,

Have you been able to try with the 6.15 BSP version as Tao indicated? I cannot make out the version of the BSP from the attached log.

Also, do you see the same behaviour with retail build?

Thanks,

Aparna

Hi Aparna,

As per Tao's suggestion I have downloaded the Source BSP but I am yet to receive the Lic file from TI. I have got the TI software Activiation ID.

It would be great if you could send me the Lic file.

In Retail Build if "enable KITL" flag is not set then I dont have any problems the BSP boots on the target.

I need KITL as I need to port a USB driver from Windows platform to CE platform.

thanks

Regards

Prasanna