Release notes for the M52277EVB BSP Released: 12 Dec 2008 This is a release of the Freescale Semiconductor M52277EVB Linux BSP. The default configurations of this BSP have been tested and all features are believed to be functioning correctly except as noted in this document. If you find an issue, please report it to www.freescale.com. The following hardware is supported: MCF52277 processor on the M52277EVB development board. For configuration information, please see /Help/software/User_Manual.pdf on the BSP CD image. ========================================================= SUPPORTED FEATURES IN THIS RELEASE ========================================================= Processor Features: * ColdFire® V2 Core at 160MHz * Enhanced MAC module * 16 KB I/D-Cache * 128 KB SRAM * Integrated peripherals o Three UARTs (Only 2 are supported) o DMA Serial Peripheral Interface o I2C Bus Interface o 16-channel eDMA controller o Real Time Clock o CANbus support o USB o 4 Timers o LCD o SSI o Audio o Touch Screen o 16M on-board flash o 2M onboard Serial Flash o ADC interface o eDMA o SD/MMC Kernel Features: - Linux-2.6.26-uc0 kernel u-boot 2008.10 GNU gcc 4.3.2, uclibc 0.9.45, binutils-2.18.50.20080215, and elf2flt. GDB 6.8.50.20080821 Userspace packages highlights: * busybox * gdbserver * i2c-tools * mp3player * mtd-utils * nano-X * play * strace * touchscreen demos ============================================================= CFFlasher Information ============================================================= This CFFlasher setup procedure will help users reinstall the u-boot bootloader. Included in this BSP is a u-boot binary needed to restore the bootloader firmware. You have to use **Windows** to run the CFFlasher software. 1) Install the CFFlasher software. That code is not included in this BSP and should be downloaded from the Freescale website. http://www.freescale.com/coldfire 2) Click on the CFflasher icon and follow the instructions to start the software. 3) With target power off, connect a host USB port to the USB P&E micro interface - the J25 connector. 4) Select the appropriate "Target Config" settings. 5) Select the "Program" option and navigate to the /images/u-boot.52277.bin file or to a user built bootloader in /rootfs/boot/u-boot.bin. After selecting the "Program" button, a progess bar should be displayed on the screen. 6) Power down and remove the cable. When you power on the board again the u-boot headers and prompt should be displayed on a terminal set to 115200 8N1. 7) Follow the u-boot setup procedures in the User's Manual. ============================================================= DEVICE DRIVER UPDATES SINCE LAST RELEASE ============================================================= 1) Added support for RTC device. 2) Improved support for SocketCAN. ============================================================= BUG FIXES SINCE LAST RELEASE ============================================================= 1) Bug 1412 - Ping command does not work properly on second instance 2) Bug 1415 - Pinging with packet sizes greater than 1000 bytes results in packet loss. 3) Bug 1441 - USB ethernet perfermance is slow. 4) Bugs 1489, 1490, and 1491 - SD/MMC device driver is not fully functional. It detects most SD cards, but it is slow and does not work with the eDMA driver. This driver cannot be used with the audio kernel. SD cards are not "hot pluggable" and must be inserted during kernel boot to be detected. 5) Bug 1492 - Audio files (both mp3 and wav) sampled at 44.1KHz play very poorly. 6) Documentation bugs: Bug 1530 - Wrong node name mentioned in the SD/MMC device driver document Bug 1531 - EDMA option not enabled default in the audio kernel config file Bug 1534 - No information regarding the BDI pin on the board Bug 2125 - BDM setup missing steps Bug 2142 - gdb/bdm download instructions Bug 2389 - RTC document problem Bug 2393 - MMC_SD_SDIO_MCF5227x.htm documentation error 7) Bug 1549 - Tx bytes is not updated when CAN packet is transmitted Bug 1550 - Rx bytes counter in the can interface is spurious 8) Bug 1611 - mcf5227x_slides demo bug 9) Bug 1640 - compiler flag needs be a v2 core 10) Bug 2173 - uClinux kernel, is not creating the /proc//exe soft link to the absolute path of the running executable. 11) Bug 2175 - MCF52277 BSP does not consistently boot. 12) Bug 2386 - Enabled AppTRK in default configuration. 13) Bugs 2397, 2422, 2461 - Can bug fixes. CAN ID is always 0, CAN fail to receive continuous message frame, and CAN fail to send and receive frame after ifconfig can down ============================================================= KNOWN ISSUES ============================================================= Audio-Video ----------- 1) Audio and video device drivers cannot operate at the same time. Two kernels have been installed in flash. The video kernel is at location 0x40000 and the audio kernel is at location 0x340000. J5 and J6 must be reconfigured to switch between audio and video systems. 2) In the non eDMA mode the processor is not powerful enough to decode MP3/WAV files in real time with sample rates higher than 11 KHz. The eDMA option should remain enabled. RTC --- 3) With the initial release of the MCF5227x silicon the RTC registers HOURMIN, SECONDS, and DAYS are reset during power up; therefore the time and date information is lost after a reset. System limitations: ------------------- 4) There is a limited amount of RAM (64M) available on this system. Running memory intensive programs repeatedly will likely fragment the memory resources available. Care must be exersized when writing programs or scripts for this platform. Allocating large chunks of memory (>1M) should be avoided. If you do allocate large amounts of memory try to avoid repeated allocations/de-allocations. 5) Processes involving large files may fail and cause a kernel core dump. This has to do with the memory fragmentation issue. If you see a kernel core dump message that includes something similar to the following line: ... Allocation of length 559231 from process 357 failed DMA per-cpu: ... The memory is fragmented and cannot be recovered. Review the existing system and try to limit processes and reduce the system size by disabling unused device drivers and packages. UART ---- 6) UART0 is the default console. UART1 can be setup to use as a termianl after booting, but it cannot be used as a boot console to display kernel boot messages.