Hi all,
*I connected, sent and made call successful with osmocombb (with real IMSI
and IMEI).
But, now, I get error, always be rejected:*
OsmocomBB# show ms
MS '1' is up, service is limited
IMEI: 357337016773249
IMEISV: 3573370167732490
IMEI generation: fixed
automatic network selection state: A0 null
cell selection state: PLMN search
radio ressource layer state: idle
mobility management layer state: MM idle, PLMN search
OsmocomBB#
% (MS 1)
% Trying to registering with network...
*in my config file (/root/.osmocom/bb/mobile.cfg)**:*
!
! OsmocomBB () configuration saved from vty
!!
!
line vty
no login
!
gps device /dev/ttyACM0
gps baudrate default
no gps enable
!
no hide-default
!
ms 1
layer2-socket /tmp/osmocom_l2
sap-socket /tmp/osmocom_sap
sim reader
network-selection-mode auto
imei 357337016773249 0
imei-fixed
emergency-imsi 452040399998391
sms-service-center +84980200030
no call-waiting
no auto-answer
no force-rekey
no clip
no clir
tx-power auto
no simulated-delay
no stick
location-updating
neighbour-measurement
codec full-speed prefer
codec half-speed
no abbrev
support
sms
a5/1
a5/2
p-gsm
e-gsm
r-gsm
gsm-850
dcs
pcs
class-900 4
class-850 4
class-dcs 1
class-pcs 1
channel-capability sdcch+tchf+tchh
full-speech-v1
full-speech-v2
half-speech-v1
min-rxlev -106
dsc-max 90
no skip-max-per-band
exit
test-sim
imsi 001010000000000
ki xor 00 00 00 00 00 00 00 00 00 00 00 00
no barred-access
no rplmn
hplmn-search foreign-country
exit
no shutdown
exit
!
Anyone help me???, thanks a lot!
--
Thanks and Best Regards
--
From: Hoàng Mạnh Hùng
Hi,
I'm working on bringing up nuttx on the c139. I am running this as I described previously by jumping from 0x2000 to 0x10000 with a small firmware image there and then nuttx is configured to run from flash at 0x10000. I configured nuttx RAM to live at 0x800100 to skip the exception vectors area that the compal loader sets up.
NuttX is coming up somewhat but getting stuck on an unregistered interrupt #21 which seems strange since there are 21 interrupts and I thought they might be 0-based so not sure what's going on here. Was wondering if there was some state that the compal loader setup that is giving me problems or if there is some other issue going on. If anyone has an idea off-hand let me know.
If I take a DEBUGASSERT() out is when I get the info about irq 21. With the DEBUGASSERT() in it seems I'm trying to do initialization during interrupt handling somehow? "This API should not be called from interrupt handlers" is the comment near the assert in sem_wait().
Attached is a serial log from the phone booting up. I've added a lot of debug logging beyond what is normally in NuttX. I included first a log with DEBUGASSERT() included and then one without.
Thanks,Craig
Here is a patch for a simple "jumper" app which loads at 0x2000 and which disables the irqs (thought it might help with the nuttx startup error I have) and jumps to 0x10000 (where I have flashed nuttx).
I'm submitting a patch to nuttx as well for building nuttx.bin for running in compal_e86 flash.
I may have fouled up the patch due to being on jolly/menu. Wasn't sure if you wanted to pull in those changes as well? I've certainly used the menu app with the flashing_new instructions and it seems to work great on my c139.
-Craig
Hi,
I'm trying to get nuttx running on my C139 compal_e86(88?) phone. I have been reading some emails and loader scripts but am a bit unexperienced with this area of software. I've managed to use the "menu" app with flashing successfully but so far am unable to get nuttx to run either due to the compal loader not letting me load more than 128k into highram or the flash setup not being quite right in terms of loader scripts.
I think what I would like is this (based loosely on LINKAGE.txt in osmocom-bb/.../compal_e88)
- keep compal loader at 0x0- put something custom at 0x2000, either the menu app or a simple 2nd stage loader- put nuttx at 0x10000
The "menu" app option (http://bb.osmocom.org/trac/wiki/flashing_new) would require me to modify that code a bit so that I wasn't copying nuttx into highram but instead just running it "in-place" in flash. So maybe two header options: "highram:APPNAME" and "flash:APPNAME"? I suppose I could try running nuttx in highram as menu currently intends, by copying it from flash to ram but that seems sort of "wrong" if nuttx is my main goal.
The "other" option would be to write some simple loader for 0x2000 which did whatever setup might be required (none?) and simply jump to 0x10000. That way the ideas in LINKAGE.txt about safety and what-not are preserved. If I need to flash a new nuttx image I don't have to worry about ruining page 0 and compal loader and bricking the phone.
Another option would be to replace the compal loader but I'd rather get to nuttx sooner than later and don't see much immediate advantage to an entirely custom bootloader.
If I preserve the compal loader then all the normal osmocom-bb functionality is preserved in terms of being able to load layer1, rssi if you want to in highram while nuttx could be living in flash for booting into "normally" to use as a consumer-style device.
I think I prefer the "other" option I mention above to keep things fairly simple. Do you think I can just use the flash.lds from compal_e88, modify slightly for e86 (bigger IRAM I think is the only change) and simply put a jump at 0x2000 to 0x10000? Would that take care of exception vectors, setup and all the other stuff I don't currently understand about bringing things "up"?
Just FYI, I am working off the latest nuttx code and not nuttx-bb since nuttx-bb seems pretty out of date. Not sure what folks want to do with that.
Thanks,Craig
Hi everyone,
I am working on modification the osmocom-bb project. I try modified the
osmocom-bb which could communicate with BTS via UDP sockets.
Here you can find the project:
https://github.com/clovnrian/osmocom-bb-gprs-no-hw
I have problem with cell syncing. This is output from mobile:
<0003> gsm322.c:2947 Channel synched. (ARFCN=17, snr=0, BSIC=0)
<0003> gsm322.c:698 Starting CS timer with 4 seconds.
<0001> gsm322.c:2968 using DSC of 90
The CS timer always timeout. On github you can see what messages BTS sends
to mobile.
Does anybody know what I have to do to or what message I have to send to
mobile?
I will be grateful for any help
With regards
Miroslav Babják
Hi everyone,
I'm following up on this conversation:
http://comments.gmane.org/gmane.comp.mobile.osmocom.baseband.devel/1796
It seems like there was no movement in this topic in the last couple of years, so I decided to go ahead and integrate Nico's SAP client into the current master branch and created a patch from it.
I tested it (with Kevin's softSIM and a pcsc reader), it worked for me, however it is currently quite ugly: it kind of hand crafts the msgb structure (in l1ctl.c, patch line 121), sorry for that, but I kept getting extra bytes stuffed into the msg that was passed to the sap_interface so I decided to manually go around the problem.
I'm of course open to any suggestions to get it cleaner, and then if you think and decide so it could be merged into the master (as far as I see.
One thing however that I think is strange, and worth mentioning: I'm not sure why Nico decided to implement the switch between phone and SAP-client inside of l1ctl.c, for me it would feel better to do it in sim.c (since sim.c deals with SIM activities, l1ctl should deal only with L1 stuff...also the current SAP client calls back to sim.c, but receives data from l1ctl - little bit confusing), but I left it as is because of not knowing exactly the thoughts behind it.
Regards,
Domi
Hi all,
Was starting to work on making a usable phone again and wondered about the status of nuttx-bb git on osmocom.org versus nuttx source. It seems nuttx source is more up-to-date and has configs for my device: compal_e86/c139. Wondering if there is something in nuttx-bb that is unique that I should pay attention to? Should nuttx-bb be rebased from nuttx upstream?
I was able to cobble together a nuttx.bin but on loading it always stops at 88% with the chainloader. The nuttx.bin is 148K which would seem plenty of room since the C139 has 4000K flash (32MBit) (am I doing that calculation correctly)?
I had to fiddle with the MEMORY section of the ld.script in order to make space for nuttx, I'm not too familiar with this sort of thing so may have done something wrong...
/* E86 stacked flash 32mbit flash, 4mbit sram, DBB internal 256kb SRAM */
/* 0x800000-0x87ffff */ /* bump up because we have 32mbit instead of 16mbit */
/* compal-loaded binary: our text, initialized data */
LRAM (rw) : ORIGIN = 0x00800000, LENGTH = 0x00020000
TRAM (rw) : ORIGIN = 0x00820000, LENGTH = 0x00040000
/* compal-loaded binary: our unitialized data, stacks, heap */
IRAM (rw) : ORIGIN = 0x00860000, LENGTH = 0x00020000
Originally TRAM was 20000 long and gave me an error on building. Not sure if I can fiddle with these values or not.
Thanks,Craig
