Mity CPU Platforms » MitySOM-335x (ARM Cortex-A8 Based Products)

Hi Raja,

Were you successful when you tried connecting the JTAG to the TI eval board?

I am assuming you are connecting to a MityARM-3359?

-Mike

Hi Mike,

Yes, I am connecting to MityARM-3359 and not on TI eval board.

So i want to know what .gel file i need to select while configuring?

Is my sysboot options are correct as configuring XIP or any other configuration required.

I do not succeed in connecting the same.

Hi,

Do we have some inputs on this topic please?

Thanks,
Raja.

Hi Raja -

Sorry for the delay in getting back to you on this. We are working this now and will have an answer for you as soon as we can.

Thanks,
Tom

Hello Raja,

Attached are both a gel file and a ccxml file that hopefully will get you going. The gel file has been used previously and should work for you with the MityARM-3359 SoM.

The ccxml file is setup for use with the XDS510 USB emulator. You may want to try and use this file and change the Emulator specific settings to the one you are using. As well one must have setting in this ccxml file is this line:

<property Type="filepathfield" Value="..\..\..\..\projects\internal\mityarm335x\sw\gel\AM335x.gel" id="GEL File"/>

In the GUI that value is set from the Advanced tab for the debugger configuration.

I am planning on trying to locate the same emulator (XDS100V2) that you are using and giving this process a try myself.

Thanks,

Alex

Hi Alex,

Thanks for your reply.

I will try with these files.

What are the sys-boot options i have to set while connecting to JTAG?

Thanks,
Raja.

Raja,

Sorry about the delay but I did want to update the fact that I was able to have the debugger connect to my MityARM-3359 SoM through the 335x Development Kit from CCS5 using the XDS100v2 emulator.

Offhand I'm not sure which XIP setting you want to be using but I used our "default" setting of 000100000000 (J106). At the UBoot prompt (did not allow it continue booting) I was then able to get CCS to connect over the emulator.

Attached is a new ccxml file that is using the XDS100V2.

Please let me know how its going for you and if you've been successful or had any issues.

Alex

Hi Alex,

I am working on to connect the JTAG to the mityarm board.

But having trouble how to proceed with project creation and connecting to target.

Do you have any procedure or example how to connect and flash the kernel to the target?

Regards,
Raja.

Hi Alex,

Do we have any inputs on connecting JTAG to Mityarm board and can be used for flashing?

Alternatively i tried 'Linux Debug in CCSv5" from TI site and created project in CCSV5 for linux. But during connecting to target it gave me error as "make: no rule to make target 'include/config/auto.conf' needed by 'include/config/kernel_release'. stop.

My kernel compiled properly and generated uImage when i built from command prompt.

Do you have any information, What could be wrong here?

Thanks,
Raja.

Raja,

Typically we load the kernel over either tftp/nfs and write it onto the MityARM-3359 flash memory or boot from nfs (http://support.criticallink.com/redmine/projects/arm9-platforms/wiki/Linux_Kernel). Previously we have loaded the kernel, booted the module and then ran our application on the module with GDB server and connected via GDB to CCS to do debugging (http://processors.wiki.ti.com/index.php/Linux_Debug_in_CCSv5).

Can you please try and explain exactly it is that you're end goal is with this debugging and some further details on how you are trying to do it?

Also please provide a Link to the "Linux Debug in CCSv5" web page you are referencing, that may help me understand what you're trying to accomplish as well.

Thank you and hopefully we'll get this sorted out,

Alex

Hi Alex,

I have also referred the same link provided by you (http://processors.wiki.ti.com/index.php/Linux_Debug_in_CCSv5). But I am trying for procedure mentioned under stop mode debug. As our final board is not having ethernet, trying for the JTAG connectivity for kernel debug and NAND flash programming.

Do you got any procedure how to program NAND flash using XDS100V2 JTAG?
Do you got any other best way to program the NAND with out ethernet?

Thanks,
Raja.

Raja
This TI page talks about various ways to flash the NAND (from CCS, etc)
http://processors.wiki.ti.com/index.php/AM335x_U-Boot_User%27s_Guide#Flashing_U-Boot_with_CCS

You can load u-boot over serial using the xmodem/ymodem protocols
The following TeraTerm macro is what I have used to load u-boot over serial port COM1 (assuming boot config is set)

; open Tera Term
;   command line = 'TERATERM /C=1' (COM1 port)
connect '/C=1'

sendln 'reset'

wait 'C'

xmodemsend 'path to u-boot-spl.bin' 2

if result=0 goto error

wait 'Starting XYZmodem'

wait 'C'

ymodemsend 'path to u-boot.img'

if result=0 goto error

wait 'Hit any key to'
send #13
end

; error. stop macro
:error
messagebox 'Download error!' 'Tera Term'
end

There is currently an issue (as you revealed in your other forum post) with u-boot loading from NAND.
That should be fixed very soon.
cheers
/Tim

Another note:

Do you have any other I/O connections for storage such as MMC or USB Host (sticks)? If so you could load the data using those interfaces via u-Boot instead of serial (which is a little slow for large images).

-Mike

Hi Michael,

Thanks for your reply.

I will try with the tera term script file.

We have just SD card available. I have tried to program and could program boot loader.
But the procedure is vast and in future if need to be programmed in bulk quantity, it will be difficult.

what will you suggest for such programming.

Regards,
Raja.

Raja,

A couple of thoughts come to mind:

1) If your volume is high enough, Critical Link may be able to pre-program the NAND for you.

2) You could set up a switch on your board (or use a custom "programming board" or even our DevKit board) to alter the boot mode to support MMC (or select a boot mode that will use MMC in the event a valid NAND image is not yet programmed) and create a "flash programming" SD card that will (via bootscripts in the stored environment on the SD card) program the NAND automatically on startup.

E.G. on the SD card you would have:

- SD based MLO to boot u-Boot from SD
- SD u-Boot image
- Env.txt environment file
- MLO to be programmed into NAND
- u-Boot Image to be programmed into NAND
- You application data (filesystem/app image/kernel/etc) to be programmed into NAND

The Env.txt file would include (as environment strings) command scripts to erase and program the NAND using the files on the MMC card.

You could even set up the environment "bootcmd" string to autorun the programming scripts.

This would make your programming process fairly straightforward. Just plug the MityARM-3359 into a board with the MMC card in it and turn it on....

Does this make sense?

-Mike