StarterWare 02.00.01.01 issues fixed

This page lists the issues fixed in StarterWare 02.00.01.01 Am335x release.

Fixed in this release

Issue Identifier	Issue Description
SDOCM00102382	During NAND Page Write operation the FIFO status of the GPMC is not checked before writing to it, this potentially leads to corrupting the data already present in the FIFO.
SDOCM00102272	The functionality of "UARTGets" API is not compliant with the standard I/O function "gets". So this API has to be updated to make the functionality similar to "gets" with buffer overrun check.
SDOCM00102219	Game application prints the score continuosly on the UART console. This process of continuosly printing of scores is creating issue when semihosting is enabled. When semihosting is enabled, applicaiton tries to print continuosly the score on the debug console. Because of this application is not working properly. Console prints are blocking the actual touch event isr handling. Continusoly printing the score is also not a valid use case. Since it is affecting actual application performance in some scenarios, the printing of score on the console has to be removed.
SDOCM00102143	In AM335x TRM, the EEVAL register was not documented. While debugging customer issue this is identified. So uart_edma examples have to be updated to configure EEVAL register after clearing the interrupts.
SDOCM00102049	The platform API "PWMSSTBClkEnable" is used to enable the time base module clock for the required PWM instance. This API will not function properly when multiple PWM instances are used. This API enables the clock for required PWM instance and it is also disabling the clocks for the other PWM instances which causes issue when more than one PWM instaces are used. This API has to be updated correctly to enable the clocks for the required PWM instance without disturbing the clocks corresponding to the other PWM instances.
SDOCM00101720	UARTCharGetTimeout API returns 0xFF on a timeout, which makes it difficult to distinguish between an actual timeout and reception of a valid character of 0xFF.
SDOCM00101640	DS2 is removed from TRM. Hence support for DS2 to be removed from StarterWare.
SDOCM00101337	DCANIntMuxConfig() API does not handle configuration of interrupt line for last message object. The API was designed by referring to the description given in AM335x TRM. However the description given in DCAN functional spec contradicts the information in TRM and hence the API needs to be updated with information given in DCAN functional spec.
SDOCM00101334	The McSPI examples do not display an error message to the user if the board is in incorrect profile. Due to this the example hangs and user is not notified what is the root cause for the hang.
SDOCM00101333	The McSPICSTimeControlSet() API expects user to shift the values and pass it as parameters and parameter shifting is not handled within the API. This is not a bug because in the API description it is mentioned which macros can be passed to this API and these macros are having the shifted values. However if the user passes the values which are not shifted then the API will not hold good.
SDOCM00101192	The DCANIntMuxConfig() API takes 3 parameters - baseAdd, IntLine,msgNum. However inside the API intLine is not being used and instead of this msgNum is being written to the field of IntLine.
SDOCM00101045	After execution of RTC Only wake through external pin, GPIO wake for DS0, DS1, DS2 and Standby fails.
SDOCM00100831	With memory configured as standard memory (in mmu page table), memory barrier instructions need to be added for enabling and disabling interrupts.
SDOCM00100330	USB phy to be turned off while entering Deep sleep state. This will aid in additional power saving.
SDOCM00100323	The ECAP Interrupt Status Clear API (ECAPIntStatusClear) should read the Interrupt Flag (ECFLG)register and write to the Interrupt clear (ECCLR)register to clear the Interrupts. But current implementation reads from the clear register and writes to the same. This register gives back zeros when read from it. Hence the Interrupt status is not cleared.
SDOCM00100212	MMCSDCardInit() has to return the status but in current implementation it is hard coded to return 1 always.
SDOCM00100026	In EDMA3RequestChannel() the transfer complete code is configured based on channel number (chNum) instead of transfer complete code number (tccNum).
SDOCM00100013	The API's in board.h returns pointer to char array. So the user has to use the strcmp() where ever they are used. Instead if it is mapped to numerical integer, the CPU cycles would be saved as string comparison will be avoided.
SDOCM00099839	bss section is linker command file is not compatible with all gcc versions.
SDOCM00099737	The memory footprint captured at http://processors.wiki.ti.com/index.phpStarterWare_02.00.00.07_User_Guide#Memory_Usage_Statistics doesnt capture the size of middleware stack libraries like USB, Lwip, mmscd etc... this need to be captured in forthcoming releases.
SDOCM00099736	The function EMIFPinMuxSetup() is defined and not used in bootloader. this need to be removed to avoid confusion.
SDOCM00099655	Support for NEON/VFP Application in StarterWare.
SDOCM00099653	Ethernet application fails with 10 Mpbs
SDOCM00099651	All sources (UART, GPIO, Touchscreen, Timer-optional) are configured for resume from stanndby and the source selection provided on GUI is not valid for standby. Source selection to be implemented for resume from standby.
SDOCM00099650	Peripheral PLL are put to bypass in standby which effects the configurations of the module. Hence to be configured as GPIO for resume from standby. Incase of UART module resume from standby happens only with few keys like space, 'p', up-arrow. Resume from standby happens with all keys configuring RXD pin for GPIO inerrupt.
SDOCM00098947	The NAND Application does not use Instruction and Data Cache. Cache is used to increase programming bandwidth/to improve the performance of the CPU.
SDOCM00098556	In the IAR Project of Cache MMU example of Beaglebone, a macro 'CACHE_FLUSH' is defined for 'Debug' build configuration mode. This is not expected. The 'Debug' build mode should build the project without cleaning the Cache. However defining this macro would enable cleaning of the Cache. Due to this macro definition, this build mode generates executable which cleans the Cache before the data are output.
SDOCM00098536	In the Bootloader file 'bl_platform.c', in a function SelectI2CInstance(), the bit mask used to clear bit 4 of a variable is used incorrectly.
SDOCM00098464	The build configuration modes in the CCS Projects of Cache MMU application for the three platforms have errors.
SDOCM00098444	The HSI2C EEPROM Interrupt and EDMA applications read the contents of EEPROM onto a data buffer. Then a loop sequentially outputs every data byte in the buffer to the serial console. The displaying is done in an inverted manner. As in, the display happens in LS Nibble:MS Nibble format rather than in MS Nibble:LS Nibble format. Here LS means Least Significant and MS means Most Significant.
SDOCM00098250	UART EDMA example application not working when UART FIFO is enabled. Subsequent EDMA transmissions are not happening.
SDOCM00098132	1. StarterWare USB stack treats all devices connected on its ports as HS devices. Code needs to parse the device speed as well as the maxpacket size to provide dynamic fullspeed support. 2. In PIO mode buffer pointer is incremented by 64 bytes instead of incrementing by maxpacket size - function USBHCDPipeRead()
SDOCM00097961	I-Cache Flush in I-Cache Disable function is present in cache.c file instead of cp1.S. In case of D-Cache Disable, it is present in assembly file. So moving the I Cache flush to asembly file will avoid confusion.
SDOCM00097845	In function USBHCDPipeRead () in usbhostenum.c, After copying data that arrived with the first IN packet , code mistakenly moves the data pointer by a constant 64 bytes. In case the user asks for more than one maxpacket size of data , user buffer would get corrupted . This is applicable only in PIO mode.
SDOCM00097519	In a Bootloader function named UARTCharGetTimeout() present in the file 'bootloader/src/bl_uart.c', a loop is present which waits to receive characters from user. Though this loop and the subsequent condition checking is functionally correct, it is done in a complex manner. This can be replaced with a more gracious and simple implementation. Additionally the comments preceding the loop which explains its purpose is incorrect. It says, "Waits indefinitely until a byte arrives in the RX FIFO(or RHR).". The waiting happens for a limited number of iterations as decided by a count value and not for an indefinite period. This has to corrected.
SDOCM00097516	In a Bootloader function named UARTCharGetTimeout() present in file 'bootloader/src/bl_uart.c', the base address of UART instance to be used is taken as an input argument. However the base address variable is tampered within the function by assigning it with the base address of UART0 instance. This tampering is done before this variable is used. This is erroneous.
SDOCM00097393	During SCSI init , if a device reports unit Attention condition/ blank check condition , present code does not force the device to clear this condition. As a result the device starts NAKing/STALLing SCSI primary commands.
SDOCM00097342	In a call to the function UARTCharGetTimeout() in "third_party/xmodem/xmodem.c" file, the instance number of UART0 instance is passed as an argument instead of its base address. This is erroneous.
SDOCM00097256	In PM sleep/wake sequence the context of MPU is saved and restored for DS2. This is not needed and will increase the latency.
SDOCM00097137	On StarterWare USB webpage connector information table wrongly indicates that USB host mode examples use micro AB receptacle instead of the USB A type host port.
SDOCM00097064	In the IAR Project of Bootloader for Beaglebone, two build configuration modes namely 'Debug' and 'Release' are present. They are not required. The necessary modes are already present namely 'MMCSD_Debug', 'MMCSD_Release', 'UART_Debug' and 'UART_Release'.
SDOCM00096784	USBHCDPipeRead () wrongly checks the endpoint status for USB_HOST_OUT_ERROR instead of USB_HOST_IN_ERROR flag. Timer value needs to be cleared when it is stopped.
SDOCM00096696	TXMAXP register is being accessed using the wrong macro (HWREGB ) and HWREGH should be used. This is because TXMAXP register is a 2 byte register.
SDOCM00096610	DMTimer POSTED mode support is not present in StarterWare 02.00.00.07 release. By default(hard-wired) POSTED mode is enabled in DMTimer and because of this ceratin registers need to be polled before writing to them.
SDOCM00096608	There is no call to file or directory close after opening file or directory in bootloder and application code of mmcsd
SDOCM00096607	HSMMCSDControllerSetup is called twice in main function. Need to cleanup the same.
SDOCM00096577	The issue is with the M2 divider. This register (CM_WKUP_CM_DIV_M2_DPLL_*) does not allow the writing of a 0 to the DPLL_CLKOUT_DIV field. Therefore, the clearing of the existing value actually results in a 1 being left in the field. Then the OR’d in value may be incorrect.
SDOCM00096361	The HSI2C Header file "hsi2c.h" is missing a conditional check for the case when the macro '__cplusplus' is defined. If this macro is defined, a closing curly brace is inserted which corresponds to an opened one earlier in the file.
SDOCM00096332	While initialising SCSI Inquiry data in the structure g_pucCommand (USBDSCSIInquiry () )is being initialised with 16 bytes of data from tUSBDMSCDevice pucVersion field . pucVersion field is only 4 bytes long.
SDOCM00096165	In the AM335x Bootloader file - "bootloader/src/armv7a/am335x/bl_platform.c", the macro values for DDR timing paramters are not correct.
SDOCM00096121	The UART can generate error interrupts in two forms: 1. A single Receiver Line Status Error interrupt that caters to Overrun Error, Framing Error, Parity Error and Break Indication. 2. A Character Timeout Interrupt. These two interrupts are enabled but the UART Interrupt Service Routine (ISR) does not handle them as expected.
SDOCM00096039	In AM335x UART, a write to the FIFO Control Register (FCR) should be preceded by the setting of the 4th bit of Enhanced Feature Register (EFR) i.e. EFR[4]. The specific reason is that FCR[5:4] can be written to only when EFR[4] = 1. The API UARTFIFORegisterWrite() wrote to the FCR without ensuring this pre-condition
SDOCM00096033	The DDR3 which is used in EVM-SK AM335x board runs at a minimum memory clock frequency of 303MHz. This frequency can be attained by configuring the PLL with appropriate multiplier and divider settings. To configure PLL for DDR3, the Bootloader used the multiplier and divider parameters applicable for DDR2.
SDOCM00095982	The Transmit FIFO size of UART is 64 bytes. If FIFO is enabled, multiple bytes can be written at once to the TX FIFO on the occurrence of an interrupt in the Interrupt Service Routine (ISR). However, the ISR uses a UART API named UARTCharPut() which waits for the TX FIFO to become empty before writing one byte only into the TX FIFO. Thus we are not utilizing the remaining 63-byte capacity of the TX FIFO.
SDOCM00095894	The access of the Trigger Level Register (TLR) in UART, the 4th bit in Enhanced Feature register (EFR) has to be set to 1. This was not done in the API UARTFIFOConfig() which accessed TLR.
SDOCM00095771	Jlink debugger is not supported in StarterWare02.00.00.07 release and is mentioned in StarterWare02.00.00.07_Release_Notes. However, this information is not updated in AM335X_StarterWare_Environment_Setup page of user guide.
SDOCM00095660	Almost all the subsequent directories containing “.CCSProject files” have some random “linker CommandFile value” in these files. These should have corresponding correct value as per the correct cmd script.
SDOCM00095562	A macro 'CM_PER_GPIO1_CLKCTRL_MODULEMODE_ENABLE' has been used within the GPIO Clock Configuration function for GPIO3. This is incorrect. A similar macro for GPIO3 should have been used.
SDOCM00095072	ECAPIntDisable() API enables interrupt instead of disabling. This API reads ECAP Interrupt Enable Register and does bitwise OR with the bitmask of interrupts required to be enabled. Then the result written back to ECAP Interrupt Enable Register. This operation will enable interrupts instead of disabling it.
SDOCM00094820	PM demo not stable in 02.00.00.07 release.
SDOCM00094144	In TI AM335x EVM, stability issues are observed with Power Management in Demo Application when D-Cache is enabled. The EVM sometimes fail to wakeup. Currently, after some sequence changes, the issue is not observed, but root cause is not identified.
SDOCM00102277	usb_device_host_msc.c has windows style line endings . Use dos2unix utility to convert to unix file.
SDOCM00101137	Create a small sized image of usb_host_msc. Customer builds usb_host_msc example in PIO mode . Build crashes due to data abort. The exception is encountered just before branching to a function .
SDOCM00099724	Teardown hang: Frequent teardowns cause controller to hang. Solution/workaround: 250 micro seconds delay to be added to RXDMA teardown path.
SDOCM00099723	Babble condition is seen randomly when usb device (mouse) is inserted into the USB ports Solution :Restarting or re-initialization of the MUSB controller in SW helps in re-enumeration.
SDOCM00099717	RX DMA delayed buffer updation issue - When the system load is high, CPPI DMA RX buffer writes take longer time to reach DDR and hence the CPU gets interrupted (indicating transfer completion) long before DDR update. Solution :Initialise “data length” field in PD to zero. Check the “data length” field in PD for amount of data obtained (non zero value).
SDOCM00098752	CppiDmaGetINTD0Status () function is wrongly defined. The RX_SOP starvation status and clearing mechanism is wrong and does not work for AM335x. IRQSTAT and IRQENABLER registers need to be used instead.
SDOCM00097808	In - USB0ModuleClkConfig( ) defined in usb.c CM_CLKDCOLDO_DPLL_PER register is being wrongly initialized. Read only bit ST_DPLL_CLKDCOLDO is being set.
SDOCM00096470	when USBEndpointStatus () returns USB_HOST_OUT_ERROR and the timer has not run out the code will keep looping in the while(ulRemainingBytes != 0) loop.
SDOCM00096355	In StarterWare USB documentation under heading "DMA support" it is claimed that StarterWare supports GRNDIS mode. Currently only transparent DMA mode is supported and this has to be updated in the webpage.
SDOCM00095670	StarterWare USB stack supports forcing the PHY to operate in FULL SPEED mode. This needs to be tried in all example demos currently supported on SA platform and then documentation needs to be updated.