Pirelli DP-L10

The Pirelli DP-L10 is a tripleband GSM/Wifi VoIP dualmode phone, which was developed by Pirelli Broadband Solutions and manufactured by Foxconn.


It was branded and sold by quite a few operators:

  • Pirelli DP-L10
  • Arcor Twintel DP-L10
  • Telekom TC-300
  • sipgate Pirelli Discus DualPhone DP-L10
  • Black
  • Cubic Mobile DP-L10
  • Tovo t450g
  • Eurotef-M

The phones are still available as new at various places like eBay, Pollin or
For more information on the original firmware see the ip-phone-forum wiki (german).


  • CPU/DBB: TI Calypso (D751992AZHH)
  • ABB: TI Iota (TWL3014)
  • GSM Transceiver: TI Rita (TRF6151)
  • PA: SKY77328-13
  • Flash/SRAM: Spansion S71PL129NC0 128MBit/64MBit
  • Wifi: Marvell 88W8385 802.11 MAC
    • Marvell 88W8015 802.11b/g transceiver
  • Winbond W56940 ringtone chip
  • Sunplus SPCA552E multimedia controller
  • LSI-65194A1 ASIC (seems to be a DSP for VoIP en-/decoding)
  • Silabs CP2102 USB UART (connected to UART_IRDA of the Calypso)


The pcb is labelled with "T60N925", and the Foxconn internal project name seems to be "T60N925.00".

There are no schematics of this phone, however, steve-m has grinded down one of those boards, see the pictures of all layers here or locally at PirelliDPL10PCB.

Pirelli DP-L10 pcb front

large version

Pirelli DP-L10 pcb back

large version

large version of RF part

RF path

Since this phone is a tripleband design, it uses 3 rx filters, connected to the respective Rita inputs:

  • Epcos B7820 for GSM900
  • Epcos B7821 for DCS1800
  • Epcos B7851 for DCS1900

Those are connected to an unknown "T 636 / 5475" antenna switch. The pinout of this switch however is identical with the Panasonic EZFL897TB11C.
The control voltage inputs of the switch are connected to the TSPACT outputs of the Calypso DBB through a Fairchild NC7NZ34 triple-buffer.

The NC7NZ34 buffer

Phone as clock generator

The idea to use an OsmocomBB-driven phone as an accurate clock source, e.g. for the USRP, by synchronizing the clock to a cell of a commercial operator was discussed on the mailing list a while back. Since the USRP needs an input clock of 52MHz, but the Compal-phones only expose 13 and 26MHz, an external PLL would be required. The DP-L10 however exposes the MCLK/TSPACT11 pin of the Calypso, which is connected through the triple-buffer to the GSM900 TX/Vc3 input of the antenna switch, and thus easily accessible. When the corresponding bit in the MCU_SW_TRACE register is set, this pin outputs the 52MHz clock being fed to the ARM-core, which is phase-locked to the VCTCXO. See the blue circuit path in the picture above.

This is the output captured with a 100MHz scope (and thus limited):

MCLK output after the buffer

After synchronizing to a cell with the phone, the frequency error measured by the DSP is in the 0-10Hz range.

USB/Serial converter

A nice feature of this phone is that it already has an integrated Silabs CP210x USB-UART, which is supported by Linux. Even faster, odd baudrates of the Calypso DBB are supported by this chip, including the maximum 812.500 baud.
Most of the phones seem to use USB vid:pid 0489:e003, which is mainline since Linux 2.6.36 (thus, older kernels need to be patched, the cp210x driver doesn't seem to take the vid/pid via modprobe parameters).

As someone pointed out on the mailing list, you can do the following for Kernels < 2.6.36:

# modprobe -v cp210x
# echo "0489 e003" > /sys/bus/usb-serial/drivers/cp210x/new_id

The DP-L10 has the CalypsoRomloader enabled.


All JTAG lines, as well as the second uart (UART_MODEM), go to the unpopulated connector next to the display connector.

DP-L10 debug connector

pin signal
1 Vcc
3 TESTRSTz (Iota)
9 nc
10 GND
11 nc
12 nc

State of support

The code which adds support for the Pirelli DP-L10 can be found in master.

What works:
  • RX/TX in GSM900 and DCS1800, PCS1900
  • audio path
  • SIM-reader
  • keypad, keypad backlight
  • Display with backlight
  • pretty much everything else, except Wifi, ringtone generator, camera and the VoIP accelerator ASIC

Note: As the power button is not connected to the keyboard scan matrix and can only be read through a Iota status register, which is quite impractical, we use the camera button on the top left side of the phone as a substitute.

Loading procedure

Due to the fact that the phone has a USB charging mode, loading osmocomBB is a bit more complicated:

  1. remove the battery
  2. plug in USB cable
  3. start osmocon, for example:
    ./osmocon -p /dev/ttyUSB0 -m romload ../../target/firmware/board/pirelli_dpl10/layer1.highram.bin
  4. put in battery and the code is being loaded. If it should abort, remove the battery, kill osmocon and resume from step 3.

Without removing the battery the following procedure is possible (without SIM, but it takes longer):

  1. plug in USB cable, the USB charging mode will start
  2. press and hold the power button, the phone will boot and show "Insert SIM"
  3. start osmocon
  4. press and hold the power button, the phone will power off
  5. the code is being loaded (because after the poweroff Iota triggers a poweron due to the "Charger inserted"-condition, which executes the bootloader)

When osmocom is alreday running on the phone and you want to reboot/load an updated version/different application, do the following:

  1. kill osmocon and start it again
  2. press the camera button on the side to power off the phone
  3. the code is being loaded (due to the fact mentioned above)

Updated by laforge almost 2 years ago · 24 revisions

Add picture from clipboard (Maximum size: 48.8 MB)