6
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
1 This repository contains a couple of hack-utilities that have been developed as
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
2 attempts at displaying TI's 176x220 pixel demo/prototype phone UI on an external
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
3 development host in the absence of a suitable Calypso target device with an LCD
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
4 of the needed large size. Two approaches have been tried, separated in time by
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
5 about 2.5 y:
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
6
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
7 2015-09 approach
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
8 ================
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
9
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
10 A year before FreeCalypso Magnetite, when all we had was the TCS211 semi-src
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
11 from Sotovik with its original all-Windows build system, with all of the blobs
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
12 intact and no apparent hope of deblobbing, plus our first attempt at bottom-up
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
13 GSM fw with completely broken L1, we had built two hacked-up versions of TI's
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
14 TCS211 fw with TI's 176x220 pixel UI enabled: one running on the GTA02 modem,
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
15 the other running on the Pirelli DP-L10. Both were hacked up to emit raster
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
16 blits of the big 176x220 pix, 16 bits per pixel color UI on the RVTMUX serial
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
17 channel, running at Calypso's maximum baud rate of 812500 bps. These hacks
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
18 have not been touched since 2015-09, but they can still be found in the
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
19 historical leo2moko-debug and tcs211-pirelli Hg repositories on Bitbucket.
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
20
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
21 A host utility named fc-lcdemu had been written to display these LCD blits
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
22 emitted by those hacked-up firmwares. It receives these blits via a pipe from
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
23 rvinterf and displays them in an X11 window; it thus naturally requires libX11
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
24 to compile and an X11 display to run. X11 programming is a black art which
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
25 this author (Mychaela Falconia) once knew but now largely forgot, hence
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
26 fc-lcdemu was based on the HECterm project (an xterm-like terminal application
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
27 for X11) by the same author, but from a much earlier life phase.
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
28
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
29 If you wish to resurrect and play with one of these external LCD output hacks
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
30 from 2015-09, you will need to invoke rvinterf with special arguments to tell
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
31 it to launch fc-lcdemu and to pass the LCD blits to it; the synopsis is as
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
32 follows:
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
33
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
34 rvinterf -B812500 -X fc-lcdemu /dev/ttyXXX
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
35
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
36 The -B812500 argument is needed to tell rvinterf to use this high baud rate,
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
37 and the -X option tells rvinterf to invoke the following named program (can be
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
38 a more complex shell command) with popen(3) and then feed it LCD blits received
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
39 from the target. If you use the new version of rvinterf that is about to be
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
40 released with fc-host-tools-r8, the old -v option is no longer needed and no
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
41 longer accepted.
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
42
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
43 This 2015-09 approach was putting a huge load on the RiViera Trace mechanism,
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
44 hacks were required in the firmware to massively super-size the memory space
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
45 allotted to RVT and to run the RVTMUX serial channel at 812500 baud, and even
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
46 with the supersized memory allocation and the maximum serial baud rate there
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
47 were still some 'Lost Message' traces. The hacks on the firmware side which
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
48 implement this 2015-09 approach have NOT been included in our current Magnetite
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
49 firmware.
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
50
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
51 2018-03 approach
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
52 ================
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
53
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
54 Rivisiting the phone UI subproject of FreeCalypso in 2018, I got another idea
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
55 for how to get the LCD framebuffer bits out of a Calypso device: instead of
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
56 having the firmware push them out to the trace buffer every time r2d_refresh()
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
57 is called, have the fw do nothing, and have the external host read the
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
58 framebuffer memory out at its own pace via ETM memory read commands. The new
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
59 fc-lcdpoll utility implements this approach; in order to avoid having to reopen
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
60 the X11 can of worms, I made fc-lcdpoll output the blits in the form which the
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
61 already-existing fc-lcdemu code from 2015 takes as input, so you run a pipeline
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
62 like this:
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
63
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
64 fc-lcdpoll framebuffer_base_addr | fc-lcdemu
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
65
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
66 fc-lcdpoll connects to rvinterf as a regular client, thus you would typically
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
67 have rvinterf running already when you run the above pipeline in another window.
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
68 fc-lcdpoll needs to know the address of the in-RAM framebuffer maintained by
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
69 the R2D firmware component, and this address needs to be given on the command
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
70 line. You can find it by grepping the linker-generated map file (fwimage.map
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
71 or ramimage.map as appropriate) for the _r2d_lcd_memory_words symbol.
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
72
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
73 This new approach works with current FC Magnetite firmware, and has been tested
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
74 in a few different ways:
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
75
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
76 * We have a real TI-made D-Sample board and we can run our Magnetite firmware
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
77 on it, but lacking the tpudrv10 driver code for Clara RF, we are running with
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
78 a non-functional placeholder stub for the TPU driver. The D-Sample board thus
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
79 has no GSM radio functionality when running our fw, and the firmware can only
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
80 do what any regular phone would do in an area with zero coverage: limited to
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
81 stepping through menus and examining SIM phonebook entries and stored
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
82 messages. The physical LCD output works, but is often garbled due to what
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
83 appears to be a hardware problem. Running fc-lcdpoll|fc-lcdemu against this
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
84 setup results in the virtual LCD mirroring the physical one, albeit with some
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
85 lag, and the virtual LCD shows what the physical one *should* display if it
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
86 weren't garbled.
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
87
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
88 * One can run a UI-enabled Magnetite build on our FCDEV3B modem board and use
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
89 the fc-lcdpoll|fc-lcdemu pipe to display what the fw puts in the framebuffer.
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
90 Unlike the D-Sample, our FCDEV3B has perfectly working GSM radio, thus this
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
91 setup allows us to see the behaviour of the UI firmware with a working radio
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
92 and thus a working GSM network connection underneath. By calling the number
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
93 of the SIM inserted into this setup, one can see the incoming call screen
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
94 followed by the missed call indication. Because there is no physical keypad
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
95 on the FCDEV3B, it appears at first that the show stops here with no way to
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
96 feed keypresses to the firmware, but TI's firmware does have a mechanism for
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
97 sending simulated keystrokes via RVTMUX encoded in GPF system primitives, and
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
98 we have recently figured out how to use it. Our fc-shell utility now offers
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
99 the new key command for sending such simulated keypresses to the target, and
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
100 by combining this key entry mechanism with the present fc-lcdpoll|fc-lcdemu
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
101 display viewing mechanism, we've been able to exercise the UI a little
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
102 further. This approach definitely shows some promise.
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
103
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
104 * The Pirelli DP-L10 target has also been tried. I was hoping that it would
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
105 make a good platform by virtue of having a working GSM radio (unlike the
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
106 D-Sample sans tpudrv10 code) and a physical keypad that is just like the
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
107 one on the D-Sample, but no joy. When running FreeCalypso on Pirelli's alien
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
108 hardware, among many other issues that kill any possibility of turning this
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
109 alien hw into a libre phone, we get this one highly bizarre misbehaviour for
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
110 which we have absolutely no explanation: the radio works OK *only if* the
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
111 firmware is built with deep sleep enabled in CST (i.e., enabled by default on
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
112 boot), and the Calypso gets to do some deep sleeps prior to the operator
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
113 manually bringing it up with AT commands. If deep sleep is disabled, as soon
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
114 as you try to bring the radio up, the Calypso DSP falls over with errors
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
115 which we naturally have no way of debugging. The most recent experiment has
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
116 revealed that this same DSP death behaviour (resulting in no working GSM
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
117 radio) occurs even when deep sleep is enabled if the firmware is built in the
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
118 MFW configuration (UI layers included) - as the UI layers command the radio
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
119 bring-up immediately on boot, the DSP falls over. Thus we are rudely reminded
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
120 once more than the Pirelli target is a dead end.
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
121
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
122 Baud rate considerations
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
123 ========================
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
124
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
125 The ETM memory read approach implemented in fc-lcdpoll is a lock-step, one read
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
126 transaction at a time mechanism, not a continuous unstoppable stream of data
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
127 like the original 2015-09 approach - therefore, it does not impose any load on
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
128 the firmware's trace buffers, and it can work with RVTMUX running at any baud
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
129 rate, even plain 115200. However, the slower the RVTMUX serial channel runs,
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
130 the slower will the virtual LCD update, hence running the serial line at 812500
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
131 baud is still preferable. To change the RVTMUX serial baud rate from 115200 bps
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
132 to 812500 bps in your Magnetite firmware build, follow these steps:
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
133
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
134 * Run ./configure.sh like you normally would, selecting the UI-enabled config
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
135 of interest for your target.
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
136
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
137 * Go into the build directory, and before running 'make', edit
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
138 config/swconfig.cfg - it is one of the config headers generated by the
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
139 configure.sh process. In that configuration header file, change the
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
140 TR_BAUD_CONFIG setting from TR_BAUD_115200 to TR_BAUD_812500.
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
141
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
142 * Run 'make' or 'make ram' as desired after editing the swconfig.cfg header.
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
143
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
144 And of course remember to pass the -B812500 option to rvinterf when talking to
|
Mychaela Falconia <falcon@freecalypso.org>
parents:
diff
changeset
|
145 such trace-speed-increased firmware.
|
