To keep updated all those who are interested in details:
Seems we finally found enough of the working mechanism of GSM-interference, to
promise we will be able to stop it.
More details: JK4401 hs-receptacle isn't shielded and obviously the contact
springs catch RF and feed it to the audio-path.
Sebastien,
which exact Wavecom wireless CPU are you thinking about?
Can you add it to the Chip Scouting section at
http://wiki.openmoko.org/wiki/MokoForesight
?
Maybe we can have a closer look at the chip...
Thanks and Best Regards,
Wolfgang
On Aug 11, 2008, at 5:06 PM, Sébastien Lorquet
getting cell information is far from firmware hacking :)
Many modems have (maybe undocumented) AT commands to get that info.
For me, GSM hacking is putting hands in the low level code itself.
2008/8/11 Florian Echtler [EMAIL PROTECTED]
But, there are other valid uses.
This reminds me that on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| The chance to get caught is even higher.
| Operating on the GSM bands automatically means the basestations receive
| what you send.
| This also means they can (and do) easily recognize if there's something
On Mon, Aug 11, 2008 at 08:06:55PM +0800, Joerg Reisenweber wrote:
To keep updated all those who are interested in details:
Seems we finally found enough of the working mechanism of GSM-interference,
to
promise we will be able to stop it.
This is good news indeed. Thanks for keeping us
Hello Werner,
Werner Almesberger wrote:
Hmm, this map is a bottom (K5AxB) configuration, not a top
(K5AxT) configuration.
You are right, the correct line in devices.txt should be:
device K5A3240CT 0xEC 0x22A0 amd map_63x64_8x8 /* GTA02 */
In particular, you can also wipe
Werner Almesberger wrote:
snip
Of small CPUs
The nicest one I found is the ST STM32F103 series, but they still eat
about 9mA at 8MHz (top speed is 72MHz, but then you need a crystal and
50mA), and 14uA in Stop. (The low-power modes are similar to the big
ARMs, just the overhead is greatly
Ian Stirling wrote:
Werner Almesberger wrote:
snip
Of small CPUs
The nicest one I found is the ST STM32F103 series, but they still eat
snip
(4% battery used in a week assuming a 3.6V 1200mAh battery)
Oops - just noticed this is rather stale - clicked the wrong 'sort by' box.
Freerunner_User wrote:
You are right, the correct line in devices.txt should be:
device K5A3240CT 0xEC 0x22A0 amd map_63x64_8x8 /* GTA02 */
This looks better, yes.
It seems that there is 8 KByte of ROM in the Calypso, however it looks
as if nIBOOT is not connected so the ROM part
Ian Stirling wrote:
Interestingly, some of these devices also offer USB. Exactly why this is
interesting, I'm unsure :)
USB would allow us to use such an MPU to implement most of the key
functionality of the debug board, i.e., JTAG and the serial console.
Granted, it would be a bit of work,
Hi,
Our current project is to control a small helicopter with the GTA02 on it.
So my question is, if there is a easy way to remove the display of the
phone without destroying it.
Because it is quite heavy and we don't really need it.
Thanks for your help.
Kind regards
Matthias
Matthias Katzengruber wrote:
Hi,
Our current project is to control a small helicopter with the GTA02 on it.
So my question is, if there is a easy way to remove the display of the
phone without destroying it.
should be no problem.
i dunno about the drivers (if they are happy when there is
12 matches
Mail list logo
