• Intro
• Downloads
• Community
• Development
• News
• TALK

Eclipse integration/Known issues prefinal

Revision as of 11:35, 10 September 2009

Known Issues for Maemo Eclipse Integration Edition 2 PreFinal release

More detailed known issues lists can be found from Garage projects for each product https://garage.maemo.org/.

Product baselines

• Fremantle devices are not officially supported as devices do not exist (publicly) yet but most unofficial Fremantle packages are already available from Fremantle extras-devel repository

Product configuration

• Maemo SDK ARMEL rootstrap is meant to be used only for cross-compiling and it does not support running or debugging applications
• Diablo 4.1.2 device requires kernel patch from here http://tablets-dev.nokia.com/maemo-dev-env-downloads.php to be flashed to the Tablet for USB Networking to work with Windows host PC
• Diablo 4.1.2 device requires hildon-desktop patch to be installed to the Tablet from pc-connectivity Garage repository (see instructions from here http://pc-connectivity.garage.maemo.org/beta1/installation.html) for VNC client to work on host PC

Maemo Mica plugin framework for Eclipse

• While debugging Python application automatic termination of debugged program does not work when debugging session ends
• Automatic installation of OProfiling support to the Maemo device may cause Eclipse to crash if Eclipse cannot find OProfile packages from configured repositories. Add following repository to the Maemo device and run "sudo apt-get update" manually as workaround.

   deb http://repository.maemo.org/ diablo/tools free

or

   deb http://repository.maemo.org/ fremantle/tools free

Maemo ESBox plugin for Eclipse

• Some of the templates and examples provided by ESBox are not yet ported to Fremantle
• Installation wizard for SDK Virtual Image on Mac OS X may run into deadlock in situations when more than one dialog is open at the same time
  • workaround is to use manual installation of SDK Virtual Image on Mac OS X
• Remote ltrace tool launching for Maemo device fails if SBRSH is used
  • workaround is to use SSH and RSE instead of SBRSH
• Python interpreter is not switched when switching targets
• Configuring C/C++ indexing in Mac OS X does not always work properly

Maemo Pluthon plugin for Eclipse

• <none>

Maemo PC Connectivity

• Maemo PC Connectivity functionality with N900 device and Fremantle is more limited than with N800/N810 device with Diablo
  • N900 will not support USB host mode
    • no workaround (N900 HW issue)
  • N900 will not support IP Forwarding (iptable NAT kernel modules)
    • workaround is to rebuild Fremantle kernel with NAT enabled and hack kernel symbols for NAT kernel modules
  • N900 will not support BlueTooth connections simultaneously with WLAN connections
    • no known workaround
  • N900 will not support USB connectivity switching between "PC Suite" and "Mass Storage" modes with platform default applet (applet provided by PC Connectivity works fine)
    • workaround is to use ONLY configuration applet provided by PC Connectivity instead of default applet
    • another workaround is to plug-out and plug-in USB cable between mode changes with default applet
  • Fremantle platform does not have libicd-dummy package available until final release and thus user cannot navigate to Internet through the browser using USB and BlueTooth. He/she will be able to navigate only using WLAN (standard behavior)
    • final PC Connectivity release will have libicd-dummy package
  • Samba does not work with Fremantle platform and N900 causing disk mounts between N900 and Windows host PC to fail
    • will be (hopefully) fixed for final release
  • Fremantle platform and SDK support ONLY 16-bit color depth
    • workaround is to configure host PC (Linux, Windows or Mac OS X) to use 16-bit depth instead by default (if default does not happen to be 16-bit)
• Configuring connectivity to work between Maemo device and host PC after installation is still partly manual work on host PC side for all supported operating systems
• When creating a project and setting SBRSH as download method quite often errors like "sbrsh server: fuse: bad mount point" and "sbrsh server: Can't mount to point:" happens. As a workaround you need to restart SBRSHD (on Maemo device side) and restart ESBox (on host PC side)

Maemo SDK Virtual Image

• NetworkManager is being started after Scratchbox, so the resolv.conf file used by Scratchbox may be invalid which causes network problems

Maemo Flasher-3.5 Tool

• Flasher-3.5 beta for Windows tool may have problems in some Windows host PC configurations to flash eMMC images properly
  • workaround is to use Linux or Mac Flasher-3.5 tool for eMMC flashing
• Flasher-3.5 beta for Windows tool fails to unpack FIASCO image with '-u' option
  • workaround is to use Linux or Mac Flasher-3.5 tool for unpacking FIASCO images

Integration testing

• Some publically available test suites (for Eclipse components and NFS mounts, for example) are run on Linux, Windows and Mac OS X during integration testing but frameworks and test sets are not yet ready to be published

• Test results (for unit tests and integration tests) for official releases are not yet ready to be published together with products

Feedback can be sent to eclipse-integration@maemo.org