Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 329837 - Platform wizard throws an exception while using the TMS320DM365 device
Summary: Platform wizard throws an exception while using the TMS320DM365 device
Status: CLOSED FIXED
Alias: None
Product: RTSC
Classification: Technology
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Amit Mookerjee CLA
QA Contact:
URL:
Whiteboard: target:3.20.05,3.16.06,3.21
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-09 13:01 EST by Amit Mookerjee CLA
Modified: 2011-06-20 14:05 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Amit Mookerjee CLA 2010-11-09 13:01:18 EST 
The platform wizard throws an exception when a platform is created with the TMS320DM365 device. 

Steps to reproduce problem
--------------------------
1. Start platform wizard in CCS4.20 (XDCtools 3.20.03) by navigating to Tools -> RTSC Tools -> Memory -> New 
2. Select the "arm" device family and the TMS320DM365 device.
3. Click Next. The platform wizard doesn't do anything and the following message is shown in the Error Log

java.lang.IllegalArgumentException: Argument of type xdc.services.spec.Expr$Term passed
at org.eclipse.rtsc.xdctools.ui.reflect.Reflect.getArrayLength( Reflect.java:24)
at org.eclipse.rtsc.xdctools.ui.wizards.DevicePage.getDeviceMem oryMap(DevicePage.java:660)
at org.eclipse.rtsc.xdctools.ui.wizards.DevicePage.createContro l(DevicePage.java:245)

This problem can be replicated with CCS4.1.3 and XDCtools 3.16.02 as well.

Short term workaround is to use the TMS320DM355 device in the platform wizard shipping with XDCtools 3.20.x and the base platform 'ti.platforms.evmDM355' in XDCtools 3.16.x and earlier releases.
Comment 1 Amit Mookerjee CLA 2010-11-09 15:34:47 EST 
Fixed in xdceclipse-h11,g38,f33.
Comment 2 Jon Rowlands CLA 2010-11-18 19:32:16 EST 
Verified using XDCtools 3.20.5.76 and CCS 4.2.0.10017

Followed steps given, memory map was populated correctly and
no errors in Error Log.
Comment 3 Dave Russo CLA 2011-06-20 14:05:08 EDT 
Shipped in XDCtools 3.21