Tag: OSD335x-SM

In our lab, we have used both the XDS110 and XDS200 emulators.  Depending on your emulation / debug needs, you can also use higher end emulators like the XDS560v2.

If you plan to use debug features like trace that are available on higher end emulators, please make sure that you bring the EMU2/EMU3/EMU4 pins to the JTAG header. If you do not plan to use those higher end debug features, then those particular EMU signals do not need to be routed to the JTAG header.

Texas Instruments also provides a number of different websites detailing information about the emulators that can be use with the AM335x processor, and thus the OSD335x SiP, as well as general inofrmaton about JTAG connectors and adapters:

• Debug Probe Performance Comparison
• XDS Target Connection Guide
• JTAG Connectors
• JTAG Adapters

Linux images from Bealgeboard.org require EEPROM to be programmed with a board ID. The following solutions can be used to overcome this issue:

1. Bypass the checks in the bootloader (u-boot)

2. Use Robert Nelson’s patch to create u-boot that will boot and allow you to program the EEPROM: In u-boot apply the patch:

https://github.com/RobertCNelson/Bootloader-Builder/blob/master/patches/v2018.03-rc1/0002-NFM-Production-eeprom-assume-device-is-BeagleBone-Bl.patch#L157-L164

u-boot also uses a device tree that you might need to modify. You should find the u-boot device tress in ./arch/arm/dts It is useful to look through the 0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch patch from Robert Nelson (see https://eewiki.net/display/linuxonarm/BeagleBone+Black) since this patch modifies device trees and can point you to important directories in u-boot.

A more detailed explanation of the above options can be found in this forum post.

Generally, XDS200 connectivity issues can be resolved by updating its firmware.

To update a XDS200-class JTAG debugger connected via USB, using a Windows host is highly recommended. Close any instances of CCS that are running in your system. Open a Windows Command Prompt and issue the following commands:

1. Go to the directory where the utility is installed:

C:\>cd C:\ti\ccsv6\ccs_base\common\uscif\xds2xx

2. Run the configuration just to make sure a XDS200-class debugger is connected and to confirm the firmware revision installed on it:

C:\ti\ccsv6\ccs_base\common\uscif\xds2xx>xds2xx_conf get xds2xxu 0

3. If you have a single XDS200 connected via USB:

Run the following commands in the exact order shown below (the batch file update_xds2xx does this in reverse order, increasing the chances of failure):

C:\ti\ccsv6\ccs_base\common\uscif\xds2xx>xds2xx_conf update xds2xxu 0 xds200_firmware_v1008.bin

C:\ti\ccsv6\ccs_base\common\uscif\xds2xx>xds2xx_conf program xds2xxu 0 xds200_cpld_v1008.xsvf

C:\ti\ccsv6\ccs_base\common\uscif\xds2xx>xds2xx_conf boot xds2xxu 0

4. After that, run the command in step 2 again to check if the correct firmware was loaded.

C:\ti\ccsv6\ccs_base\common\uscif\xds2xx>xds2xx_conf get xds2xxu 0

If connectivity issues persist, please go through the XDS200 Wiki to find out more information.

Power consumption of OSD335x-SM depends highly on usage scenarios. The OSD335x-SM Power Application Note and the OSD335x Power Management Software Control Application Note will give you detailed information about OSD335x-SM power consumption in various operating states.

Other helpful resources are:

1. AM335x Power Consumption Summary: This wiki page provides current and power measurements for common system application usage scenarios. However, these measurements were made for a presently unsupported version of SDK. Updated power consumption data can be found here.
2. Power Estimation Tool: This entails modifying and submitting a spreadsheet specifying processor mode and peripheral usage of AM335x. Login to TI website is required and the results will be emailed to the email address used to login.

All the peripherals supported by the AM335x are also supported by the OSD335x-SM. Please refer to the Ball Map section of the OSD335x-SM datasheet to understand naming conventions of various balls of OSD335x-SM. Also, the OSD335x Family Pin Assignments page gives you detailed information about pin mapping differences between OSD335x-SM and AM335x.

No, you don’t. The AM335x die in the OSD335x-SM is the same as the Die in the discrete TI device.  This means that the Pin MUX will work the same on the OSD335x-SM as it would on the discrete version. There are differences in the location and position of the signals, however. Please refer to OSD335x Family Pin Assignments page for ball map differences between OSD335x-SM and AM335x.

The ORCAD files for both OSD335x and OSD335x-SM devices can be found here.

Yes, OSD335x family runs all Linux distributions supported by TI for AM335x. It is also officially BeagleBoard Compatible so it will run the same Linux distributions found on Beaglebone Family of products.

Here are some good resources:

Texas Instruments Linux Kernel Users Guide

elinux – Building BeagleBone Black Linux kernel

Beyond Logic – Compiling the BeagleBone Black kernel

elinux – BeagleBone Black Debain

These power pins are driven by the TPS65217C PMIC and are used internally to power the AM335x, DDR and other components.  These pins are all connected within the SiP and should not be connected externally.  Optionally, these pins can be brought out as test points for debugging purposes only.  They should NEVER be used to power external components.