Project

General

Profile

SciphoneDreamG2 » History » Version 14

marcin, 02/19/2016 10:49 PM

1 1 laforge
= Sciphone Dream G2 =
2
3
The Sciphone Dream G2 is a [wiki:MT6235] based phone running UI software to mimic the look+feel of Android.
4
5
There is currently an u-boot and Linux port for the MT6235 underway, the primary development platform is the Sciphone G2.
6
7
OsmocomBB does not yet support any Mediatek chipsets, so this phone is not supported by OsmocomBB.  Nonetheless, we
8
expect to have support for it at some point in the future.
9
10 3 laforge
More information on the hardware of the device can be found at [http://en.qi-hardware.com/wiki/Sciphone_Dream_G2]
11 2 steve-m
== Serial Cable ==
12
13
You can make a serial cable by sacrificing the headset that comes with the phone, by swapping the pins inside the connector.
14
15
Serial pinout:
16
17 9 sylvain
||Pin||signal||comment||
18 2 steve-m
||1||GND||
19
||2||GND||
20 9 sylvain
||5||Rx||(From PC to Phone)||
21
||7||Tx||(From Phone to PC)||
22 2 steve-m
23
[[Image(sciphone_serial.jpg,20%)]]
24
25 1 laforge
== JTAG ==
26
27
The JTAG port of the MT6235 is accessible on the phone PCB, see the attached picture.
28 5 steve-m
You can use [http://openocd.berlios.de/web/ OpenOCD] along with the attached configuration file ([raw-attachment:openocd_mt6235.cfg]) for debugging.
29 4 steve-m
30 6 marcin
[[Image(scig2_front.JPG,20%)]]
31
[[Image(scig2_jtag.jpg,20%)]]
32
33 4 steve-m
== Serial Bootloader == 
34
35 5 steve-m
Like all Mediatek MT62xx !SoCs, the phone uses the [wiki:MTKRomloader].
36 6 marcin
37 10 steve-m
For executing U-Boot and Linux using the MTK romloader, proceed as follows:
38
39 11 steve-m
 * clone osmocom-bb.git and checkout the branch 'steve-m/loader_sciphone'
40 10 steve-m
 * compile the code, connect the phone and run osmocon:
41
   {{{
42 12 steve-m
$ ./osmocon -p /dev/ttyUSB0 -m mtk ../../target/firmware/board/mt62xx/loader.mtkram.bin
43 10 steve-m
   }}}
44
 * press and '''hold''' the powerbutton of the phone, until the loading has finished and you see the following:
45
   {{{
46
[...]
47
Received branch address ack, code should run now
48
49
Running on mt62xx in environment mtkram
50
HW_CODE = 0x6235
51
   }}}
52
53
'''Uploading U-Boot'''
54
 * '''don't''' terminate osmocon and execute:
55
 {{{
56
$ ./osmoload memload 0x500000 u-boot.bin
57
$ ./osmoload jump 0x500000
58
 }}}
59
60
 * now terminate osmocon and open a serial terminal of your choice (115200-8N1)
61
 * see below for loading Linux with U-Boot
62
63 13 marcin
== MTK boot process ==
64
65 14 marcin
MT62xx chips have IPL (Initial Program Loader) saved in ROM.[[BR]]
66 13 marcin
67
This is first code executed after power up.[[BR]]
68
69
It configures basic functionality of CPU (serial port 19200n8) and waits on 0xA beacon.[[BR]]
70
71
If beacon won't be received, it jumps to NAND memory read procedure.[[BR]]
72
73
At 0x0 address there is Boot Header placed which holds informations about NAND memory and parameters of image which is going to be loaded.[[BR]]
74
75
NAND memory read procedure tries to read NAND memory from 0x0 address with following NFI controller settings:
76
77
||Bus width||Address bytes||Page size||Column shift||Used in Sciphone G2||
78
||1||3||512||8||||
79
||0||3||512||8||||
80
||1||4||512||8||||
81
||0||4||512||8||yes||
82
||1||4||2048||16||||
83
||0||4||2048||16||yes||
84
||1||5||2048||16||||
85
||0||4||2048||16||||
86
87
If Boot Header read from NAND memory will match to currently used NFI configuration, bootloader will start to read data from NAND to internal SRAM. Internal SRAM size is 64kB, which means that code loaded by IPL can't be bigger than that.[[BR]]
88
89 14 marcin
'''Note:''' IPL doesn't configure PLL and SDRAM controller, so there is no possibility to load code to external RAM. Here is where SPL (Secondary Program Loader) comes into the game.
90 13 marcin
91
== SPL - Runing U-Boot from NAND ==
92
93
SPL (Second Program Loader) is just small U-Boot loader which includes low level CPU initialization (PLL, SDRAM) and NAND driver.[[BR]]
94
95
With default build it occupies less than 4kB, but it lacks NAND memory detection. All the NAND memory types can be specified using preprocessor which is not comfortable. We already identified three different NAND memories and that would be bad to create seperate builds for them.[[BR]]
96
97
Fortunatelly there is no need to strip down SPL size to 4kB, so SPL code has been reworked and new functionalities are added. It detects NAND memory at startup and configures NFI controller automatically. New implementation can be found at "nand_spl/nand_boot_detect.c".[[BR]]
98
99
SPL also automatically configures SDRAM controler according to RAM you have on your device (currently it tries two configurations).[[BR]]
100
101
SPL is generated on every U-Boot build and binary can be found at "nand_spl/u-boot-spl.bin".[[BR]]
102
103
SPL will be loaded and executed by IPL, only if Boot Header will contain valid data (in this case checksum and length is most important).[[BR]]
104
105
There is already tool created which automatically generates Boot Header and places it at the begining of given binary. MTK Boot Header generator can be found at "tools/mtk_image.c".
106
107
{{{
108
Usage ./mtk_image [ -s size ] [ -o file ] mtk_dump.bin image.bin
109
	[ -s size ]	- size of image, if not specified file size will be taken
110
	[ -o file ]	- name of output file
111 1 laforge
	mtk_dump.bin	- dump of NAND memory from address 0 (at least 64 bytes)
112 13 marcin
	image.bin	- image to be loaded by MTK bootloader
113 1 laforge
}}}
114
115 14 marcin
mtk_image tool needs dump file from your device (at least 64 bytes read from NAND 0x0 address) as there are different NAND memory configurations. Thanks to that Boot Header will be properly generated for your device.[[BR]]
116 13 marcin
117 14 marcin
'''Note! Before flashing U-Boot to NAND, create full dump of your NAND, otherwise you'll be not able to restore phone's original software.'''
118
119 6 marcin
== U-Boot ==
120
121
Port of U-Boot for Sciphone G2 can be found at [http://git.osmocom.org/gitweb?p=uboot-mt623x.git;a=summary U-Boot]
122
123
Building U-Boot:
124
125
{{{
126
export CROSS_COMPILE=arm-linux-gnueabi-
127
make sciphone_g2_config
128
make
129
}}}
130
131
== Linux kernel ==
132
133
Port of Linux kernel for Sciphone G2 can be found at [http://git.osmocom.org/gitweb?p=linux-mt623x.git;a=summary Linux kernel]
134
135
Building Linux:
136
137
{{{
138
export CROSS_COMPILE=arm-linux-gnueabi-
139 7 marcin
make ARCH=arm sciphone_g2_defconfig
140 6 marcin
make ARCH=arm uImage
141
}}}
142
143 8 marcin
== Building initramfs file system ==
144
145
The easiest way to have file system in Linux kernel is to build [http://www.kernel.org/doc/Documentation/filesystems/ramfs-rootfs-initramfs.txt Initramfs image].[[BR]]
146
147
You need to download [http://www.busybox.net/ Busybox], configure it and build it.
148
149
{{{
150
export CROSS_COMPILE=arm-linux-gnueabi-
151
make menuconfig
152
make
153 13 marcin
make install
154 8 marcin
}}}
155
156 13 marcin
Generated file system by default installs in _install directory.[[BR]]
157
158 8 marcin
Additional to that you'll need to create console device in already built filesystem.
159
160
{{{
161
sudo mknod dev/console c 5 1
162
}}}
163
164
Now you can create CPIO archive:
165
166
{{{
167
find . | cpio -o -H newc > rootfs.cpio
168
}}}
169
170
Next step is to point to Linux kernel where initramfs image is located.[[BR]]
171
172
In menuconfig of Linux kernel you should modify following option:
173
174
{{{
175
CONFIG_INITRAMFS_SOURCE=<path_to_cpio>
176
General setup -> Initial RAM filesystem and RAM disk -> Initramfs source file(s)
177
}}}
178
179
After these steps Linux kernel image will have initramfs built in.[[BR]]
180
181
'''Important note:''' Initramfs ignores 'init=' variable given in kernel boot parameters list. It always executes /init command at startup and you can't change it. Check if you have /init in your file system (BusyBox has /linuxrc by default, so just change its name to init).
182
Every time you change initramfs file system you have to rebuild also Linux kernel.[[BR]]
183
184
To unpack CPIO archive you can use following command:
185
186
{{{
187
cpio -i -d -H newc -F <path_to_cpio_archive> --no-absolute-filenames
188
}}}
189
190 6 marcin
== Reading data files in U-Boot ==
191
192
'''NAND'''
193
194 7 marcin
Following command will read 256 bytes from NAND address 0 at address 0x800000.
195 6 marcin
196
{{{
197 7 marcin
nand read 0x800000 0 0x100
198 6 marcin
}}}
199
200
'''Serial'''
201
202 7 marcin
Following command will read data at address 0x800000 from serial at baudrate 115200 (using kermit protocol).
203 6 marcin
204
{{{
205 7 marcin
loadb 0x800000 115200
206 6 marcin
}}}
207
208
'''SD/MMC'''
209 1 laforge
210 6 marcin
Following command will read uImage file at address 0x800000 from MMC card.
211 7 marcin
212 6 marcin
{{{
213 14 marcin
mmcinfo
214 7 marcin
fatload mmc 0 0x800000 uImage
215 13 marcin
}}}
216
217
== NAND memory ==
218
219
So far three types of NAND memories has been identified:
220
221
||Chip||Size||
222
||HY27XS08121M||512Mb (64MB) NAND||
223
||HY27XA081G1M||1Gb (128MB) NAND||
224
||TC58NVG0S3AFT||1Gb (128MB) NAND||
225
226
All of them are supported by "mt62xx_nand.c" NAND driver in U-Boot.[[BR]]
227
228
This driver has also support for ECC hardware decoding and encoding.[[BR]]
229
230
ECC layout which is used by MTK looks as follows:
231
232
{{{
233
/*
234
 * For small and large page NAND devices ecc block size is the same:
235
 *
236
 *      ecc_block_size = 256
237
 *
238
 * Placement of ecc bytes in spare area is as follows:
239
 *
240
 * --------------------------------------------------------------
241
 * |                            SPARE                           |
242
 * --------------------------------------------------------------
243
 * |    | ECC0  |       | ECC1  |       | ECC2  |       | ECC3  |
244
 * --------------------------------------------------------------
245
 * 0    8       16      24      32      40      48      56      64
246
 *
247
 * ECC0 = 12 bits (from 1st ECC block) + 12 bits (from 2nd ECC block)
248
 * ECC1 = 12 bits (from 3rd ECC block) + 12 bits (from 4th ECC block)
249
 * ECC2 = 12 bits (from 5th ECC block) + 12 bits (from 6th ECC block)
250
 * ECC2 = 12 bits (from 7th ECC block) + 12 bits (from 8th ECC block)
251
 */
252
253
}}}
254
255
ECC layout information is pretty important as built-in bootloader in MT62xx chips
256
has hardware ECC enabled and it won't load code from NAND if ECC layout will
257
not match.[[BR]]
258
259
This layout is also important to properly dump or restore existing firmware.[[BR]]
260
261
NAND driver for Linux is under development.
262
263
== LCD ==
264
Sciphone G2 has LCD with 240x320 resolution.[[BR]]
265
266
Currently two different LCD controllers has been identified (on Sciphone G2):
267
 * ILI9331
268
 * ILI9325
269
These controllers are already supported in U-Boot.[[BR]]
270
271
To identify what kind of controller is in your device, just check U-Boot prints.
272
273
{{{
274
DRAM:  32 MiB
275
NAND:  64 MiB
276
MMC:   msdc_mmc: 0
277
mtk_lcd INFO: Read LCD device code: 9331.
278
}}}
279
280
U-Boot supports displaying bitmap on the screen, you just have to create bitmap in proper format.[[BR]]
281
282
By default U-Boot will build osmocomBB bitmap.[[BR]]
283
284
To convert your customized bitmap change type of bitmap to indexed.[[BR]]
285
286
Using GIMP, select "Image -> Mode -> Indexed...". Maximum number of colours is 240 (16 is used by internal U-Boot CMAP).[[BR]]
287
288
In existing U-Boot bmp logo converting tool (tools/bmp_logo.c) there are two issues:
289
 * width of bitmap has to be aligned to 4 (otherwise padding bytes will be added and bitmap will be not properly displayed)
290
 * size of bitmap can't be bigger than 65535 (LCD on Sciphone G2 is 240x320 = 76800)
291
Both issues are fixed on [http://git.osmocom.org/gitweb?p=uboot-mt623x.git;a=summary uboot-mt623x].[[BR]]
292 1 laforge
293 13 marcin
MT6235 LCD controller shares data lines with NFI (NAND) controller. Currently there is no possibility to use NAND when LCD is used.[[BR]]
294
295
Frame buffer driver for Linux is under development.
296
297 14 marcin
== BBT handling ==
298 13 marcin
299
Comment from "sciphone_g2.h" configuration file explains how BBT is handled.
300
301
{{{
302
/*
303
 * Below option allows U-Boot to save BBT table in NAND.
304
 * Without this option BBT table is created everytime when first nand
305
 * command is executed (except "nand dump"). Full scanning of NAND
306
 * takes long time and unnecessarily delays first command execution.
307
 *
308
 * NOTE! This option is disabled by defaut as at startup it deletes last
309
 * two blocks of NAND. Most of people run code from RAM and don't have
310
 * NAND memory dumped yet. If you don't like to wait on first nand
311
 * command, you should enable below option.
312
 */
313
#define MT62XX_NAND_BBT_IN_NAND
314
}}}
315
316
== MTD partitions ==
317
318
Layout of MTD partitions is following:
319
320
{{{
321
device nand0 <mt62xx_nand.0>, # parts = 5
322
 #: name                size            offset          mask_flags
323
 0: sbl                 0x00020000      0x00000000      0
324
 1: env                 0x00020000      0x00020000      0
325
 2: u-boot              0x00200000      0x00040000      0
326
 3: kernel              0x00200000      0x00240000      0
327
 4: root                0x03bc0000      0x00440000      0
328 6 marcin
}}}
Add picture from clipboard (Maximum size: 48.8 MB)