![[IPv4/6]](/images/ip_proto.php "This beacon shows the currently used ip protocol (ipv4 or ipv6) for this connection"){kind=small}
Information about the hardware
Main processor is an ARM9 based Samsung S3C2440 running at 400 MHz. All other information about this hardware can be found on the FriendlyARM website.What the Board Support Package provides
- complete automated buildsystem for cross development (PTXdist based)
- Toolchain
- all required configurations (compile and runtime)
- support for the most common hardware on Mini2440 platform
- serial console
- network
- sound
- LED
- AD converter
- I2C
- SPI
- EEPROM
- Watchdog
- Keypad
- GPIO
- USB host and device
- various LC displays (N35/A70/VGA shield/T35/X35/W35i/N43)
- touchscreen
- SD card
- NAND for root filesystem
- buzzer
- documentation how to use the BSP on the Mini2440
Documentation
A quickstart how to build the BSP and deploy the Mini2440 can be found here:
Where to get the Board Support Package
All releases can be downloaded as TAR archives from here:
The archives names are OSELAS.BSP-Pengutronix-Mini2440-*.tgz
Current release is OSELAS.BSP-Pengutronix-Mini2440-2012.12.0.tgz
Other resources to build this Board Support Package can be downloaded here:
Where to get the latest and greatest
Development on this BSP happens in a GIT repository. To be able to test new features or to contribute, always the current GIT status must be used.
The repository can be accessed:
- via your browser / git client:
http://git-public.pengutronix.de/
Support
Questions about this BSP can be sent to the oselas@community.pengutronix.de mailing list. In order to do so, you must be subscribed to the list. A subscription can be requested on our Mailings Lists page.
Note: This is a community mailing list and offered for free. Please be aware: This support is done in our all spare time.
Known issues
| OSELAS.BSP-Pengutronix-Mini2440-2012.12.0 | |
| Known issues can be found in the BSP's archive in protocol/known_issues.txt | |
| OSELAS.BSP-Pengutronix-Mini2440-2012.06.0 | |
| Issue: The LCD is always off, independent of the used type | |
| Description: The LCD controller gets not enabled due to a broken patch to enable it. So, the attached display never gets valid signals. | |
| Solution: Apply this hot fix patch to the OSELAS.BSP-Pengutronix-Mini2440-2012.06.0 board support package after extracting it from the archive. Follow the steps listed in its header to apply the patch. | |
| Other known issues can be found in the BSP's archive in protocol/known_issues.txt | |
| OSELAS.BSP-Pengutronix-Mini2440-2012.02.0 | |
| Known issues can be found in the BSP's archive in protocol/known_issues.txt | |
| OSELAS.BSP-Pengutronix-Mini2440-2011.12.0 | |
| Issue: all tools depending on the ALSA library are crashing at run-time. | |
| Description: The ALSA lib has some issues with the glibc-2.14.x and ends with a segmentation fault. | |
| Solution: Use the OSELAS.Toolchain-2011.11.1 instead. Or you can use the older OSELAS.Toolchain-2011.03.1 instead. It comes with glibc-2.13 and everything ALSA-lib related works. | |
| Issue: Building the Qt4/QWT and Qt4/QML demo fails. | |
| Description: Due to a wrong version string in the local rule files PTXdist does not find the sources. | |
| Solution: Change the QML_DEMO_VERSION value form 'master' to '2011.12.0' in file rules/qml-demo.make and also the QT4_DEMO_VERSION value from 'master' to '2011.12.0' in file rules/qt4-demo.make. | |
| Other known issues can be found in the BSP's archive in protocol/known_issues.txt | |
| OSELAS.BSP-Pengutronix-Mini2440-2011.11.0 | |
| Known issues can be found in the BSP's archive in protocol/known_issues.txt | |
| OSELAS.BSP-Pengutronix-Mini2440-2011.10.0 | |
| Issue: Compiling the Qt4-demo application can fail. | |
| Description: Due to a wrong path in the qt4-demo.pro file some QWT related files from the host can leak in. It fails if the host uses an older QWT version than 6.0.1. | |
| Solution: Remove the INCLUDEPATH += /usr/include/qwt-qt4 line from the file local_src/qt4-demo-2011.08.0/qt4-demo.pro. | |
| Other known issues can be found in the BSP's archive in protocol/known_issues.txt | |
| OSELAS.BSP-Pengutronix-Mini2440-2011.09.1 | |
| Known issues can be found in the BSP's archive in protocol/known_issues.txt | |
| OSELAS.BSP-Pengutronix-Mini2440-2011.08.0 | |
| Known issues can be found in the BSP's archive in protocol/known_issues.txt | |
| OSELAS.BSP-Pengutronix-Mini2440-2011.07.0 | |
| Known issues can be found in the BSP's archive in protocol/known_issues.txt | |
| OSELAS.BSP-Pengutronix-Mini2440-2011.06.0 | |
| Issue: The mentioned toolchain fails to build. | |
| Description: The defined PTXdist release fails to extract the required source archives (gcc/binutils) due to missing MD5 sums. Previous PTXdist releases didn't check MD5 sums. This behaviour was changed with the ptxdist-2011.06.0 release. | |
| Solution: Install also the ptxdist-2011.03.0 release. All ptxdist releases can co-exist. Use this older ptxdist release to build the toolchain and the recent ptxdist-2011.06.0 release for the board support package itself. | |
| Other known issues can be found in the BSP's archive in protocol/known_issues.txt | |
| OSELAS.BSP-Pengutronix-Mini2440-2011.05.0 | |
| Issue: Extracting and patching the host-libusb-compat package fails. | |
| Description: The package host-libusb-compat fails in the extraction stage on multi core machines (not on single core machines). | |
| Solution: A patch is required to fix an expression in the rule
file configs/platform-friendlyarm-mini2440/rules/host-libusb-compat.make. Refer issue below for a patch. |
|
| Issue: Compiling the host-libusb and host-libusb-compat package fails. | |
| Description: Both mentioned packages need different configuration settings on 64 bit host machines to compile them successfully. | |
| Solution: Apply this hot fix patch to the OSELAS.BSP-Pengutronix-Mini2440-2011.05.0 board support package. This patch also fixes the issue mentioned above. Follow the steps listed in its header to apply the patch. | |
| Other known issues can be found in the BSP's archive in protocol/known_issues.txt | |