Hello list,
I'm newbee so excuse me for my very basic question. I follow all the instructions on srlabs.de/gprs given by Karsten
I have a C123 and a USB / jack 2.5mm - pl2303 based :(
All steps are fine until I try to programm the compal ram ;)
./host/osmocon/osmocon -m c123xor -p /dev/ttyUSB0 ./target/firmware/board/compal_e88/layer1.compalram.bin
I get :
...
PROMPT1... ... PROMPT2... handle_write(): xxxx bytes (xxxx/yyyy) ... ... handle_write(): xxxx bytes (xxxx/yyyy) Received 1 byte : xx Received 1 bytes : yy ... ... Finally I received e.r.r.o.r (byte by byte) NOT ACK RECEIVED...
I can also get (not with the same firmware...) :
... PROMPT1... ... PROMPT2... handle_write(): xxxx bytes (xxxx/yyyy) ... ... handle_write(): finished
and then... nothing...
I'm going to test the cable, as Philipp has told to Pavel. I also bought a RS232 / Jack unlocking Motorola (C123) cable and I own a BlackBox FTDI based USB/RS232 cable... So I'll test it as soon as I receive the cable.
Do you think is a matter of cable, who is supposed to be osmocom compatible, or a phone issue or even the USB port... ?
Thank you very much for your help and excuse me again with this kind of 'stupid' question about cable. I read almost all the subjects, I did a lot of experimentations in a lot of git branch (master, testing, burst_ind - of course not working with PL2303 ... + d1cb8ea9b784c7acbafbb2fdcedbdf4655c2f6f5 not working too)
I think it must work at least in the master branch...
Smith
Hey,
If I'm not mistaken pl2303 based cables have/had problems handling baudrates above 115200, there was a recent update into the kernel tree, but I've never tested it.
If you have FTDI based cable try it out, i have one based on FT4232 and it works flawlessly, pl2303 cable gave me a lot of trouble before.
You can still run osmocom-bb on 115200 cable but I believe it's not going to be sufficient for sniffing and i think you'll need to patch the code a bit for 115200 to work (perhaps someone from osmocom can guide here?).
Cheers, Lukas
On Mon, Aug 29, 2011 at 1:09 AM, smithmr103@gmail.com smithmr103@gmail.comwrote:
Hello list,
I'm newbee so excuse me for my very basic question. I follow all the instructions on srlabs.de/gprs given by Karsten
I have a C123 and a USB / jack 2.5mm - pl2303 based :(
All steps are fine until I try to programm the compal ram ;)
./host/osmocon/osmocon -m c123xor -p /dev/ttyUSB0 ./target/firmware/board/compal_e88/layer1.compalram.bin
I get :
...
PROMPT1... ... PROMPT2... handle_write(): xxxx bytes (xxxx/yyyy) ... ... handle_write(): xxxx bytes (xxxx/yyyy) Received 1 byte : xx Received 1 bytes : yy ... ... Finally I received e.r.r.o.r (byte by byte) NOT ACK RECEIVED...
I can also get (not with the same firmware...) :
... PROMPT1... ... PROMPT2... handle_write(): xxxx bytes (xxxx/yyyy) ... ... handle_write(): finished
and then... nothing...
I'm going to test the cable, as Philipp has told to Pavel. I also bought a RS232 / Jack unlocking Motorola (C123) cable and I own a BlackBox FTDI based USB/RS232 cable... So I'll test it as soon as I receive the cable.
Do you think is a matter of cable, who is supposed to be osmocom compatible, or a phone issue or even the USB port... ?
Thank you very much for your help and excuse me again with this kind of 'stupid' question about cable. I read almost all the subjects, I did a lot of experimentations in a lot of git branch (master, testing, burst_ind - of course not working with PL2303 ... + d1cb8ea9b784c7acbafbb2fdcedbdf4655c2f6f5 not working too)
I think it must work at least in the master branch...
Smith
On Mon, Aug 29, 2011 at 01:55:59AM +0200, Lukas Kuzmiak wrote:
If I'm not mistaken pl2303 based cables have/had problems handling baudrates above 115200, there was a recent update into the kernel tree, but I've never tested it.
the problem is not "[standard] baud rates above 115200" but it is "non-standard baud-rates at all". Normal USARTs have baud-rate generators that can only generate baud-rates "input_clock / divider" where divider is either an integer, or even more: limited to a power of 2
The calypso cannot do any standard baud-rates above 115200. That's why you need a USART with more flexible baud rate generator. The most commonly known one to do this is the FTDI series of USB-serial converters.
Hello Harald and Lukas,
In my opinion regarding non-standard speed, PL2303 based cable should never succeed to load code into calypso ram... The wiki says that for some branch and/or firmwares it works, I don't understand how it can happen.
btw with my pl2303 cable what branch / firmware do i have to use for loading a GSM layer1 into my C123... with succeed?
Ps. I bought a RS232 / Jack adaptator. I wait for it... (I already have a FTDI RS232 / USB cable) - If i have a little time I can braze a jack on the RS232 as explained on the wiki
Sorry for my late answer and thank you both for your help. I didn't had time to work on my problem :( (right now I have trouble with my soft raid 10 in dual boot who drives me crazy!)
Le 29/08/2011 09:23, Harald Welte a écrit :
On Mon, Aug 29, 2011 at 01:55:59AM +0200, Lukas Kuzmiak wrote:
If I'm not mistaken pl2303 based cables have/had problems handling baudrates above 115200, there was a recent update into the kernel tree, but I've never tested it.
the problem is not "[standard] baud rates above 115200" but it is "non-standard baud-rates at all". Normal USARTs have baud-rate generators that can only generate baud-rates "input_clock / divider" where divider is either an integer, or even more: limited to a power of 2
The calypso cannot do any standard baud-rates above 115200. That's why you need a USART with more flexible baud rate generator. The most commonly known one to do this is the FTDI series of USB-serial converters.
On Tue, Aug 30, 2011 at 11:40:13PM +0200, smithmr103@gmail.com wrote:
Hello Harald and Lukas,
In my opinion regarding non-standard speed, PL2303 based cable should never succeed to load code into calypso ram... The wiki says that for some branch and/or firmwares it works, I don't understand how it can happen.
because the firmware download happens at a much lower baudrate than some of the applications later use.
btw with my pl2303 cable what branch / firmware do i have to use for loading a GSM layer1 into my C123... with succeed?
YOU CANNOT DO GPRS DECODE (which uses burst_ind) WITH A PL2303 BASED CABLE!
I guess it has been written dozens of times to the wiki and this mailinglist (check the archive).
Hello Harald,
Of course, I read this... sorry my question was 'what is the branch I can use (I guess 'master') and which firmware can I load into calypso ram with my pl2303 cable'? - I can load 'Hello world' without trouble... but after the code is not bootstrapped (it doesn't run)... This is my major issue. I can, in mostly cases, load firmwares but they dont't execute! I guess somebody else in here has the same problem...
Le 31/08/2011 10:35, Harald Welte a écrit :
On Tue, Aug 30, 2011 at 11:40:13PM +0200, smithmr103@gmail.com wrote:
Hello Harald and Lukas,
In my opinion regarding non-standard speed, PL2303 based cable should never succeed to load code into calypso ram... The wiki says that for some branch and/or firmwares it works, I don't understand how it can happen.
because the firmware download happens at a much lower baudrate than some of the applications later use.
btw with my pl2303 cable what branch / firmware do i have to use for loading a GSM layer1 into my C123... with succeed?
YOU CANNOT DO GPRS DECODE (which uses burst_ind) WITH A PL2303 BASED CABLE!
I guess it has been written dozens of times to the wiki and this mailinglist (check the archive).
baseband-devel@lists.osmocom.org
-
Harald Welte -
Lukas Kuzmiak -
smithmr103＠gmail.com