| Summary: | RTSC platform wizard difficulties entering 'Base' and 'Length' for memory segment | ||
|---|---|---|---|
| Product: | [Technology] RTSC | Reporter: | Shreyas Prasad <shreyasp> |
| Component: | Tools | Assignee: | Sasha Slijepcevic <sascha> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | d-russo, dfriedland, vikram.adiga |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | target:3.25.04 | ||
|
Description
Shreyas Prasad
This was done on purpose to force hex inputs from the user. Support for other input formats can be added but I do not know how useful it will be since most people think about memory maps in hexadecimal. Adding a "0x" to the input is the most common way of representing memory locations in hexadecimal. Could we instead prefix the '0x' in the GUI itself so that there's no ambiguity? There are several improvements we could do to the UI and we can add this to the list. However, we would like to move away from the platform wizard and have a nicer/cleaner way of handling memory in XGCONF itself. I would prefer to focus on that and only make critical fixes to the platform wizard. - fixed in xdceclipse-i06 Verified pass. CCS version: 5.4 XDCtools version: 3.25.04.83 Verify steps: I verified the "0x" is prefixed by GUI to the memory map addresses. delivered in xdctools 3.25.04 |