From keith at rhizomatica.org Sun Nov 1 02:17:34 2020 From: keith at rhizomatica.org (Keith) Date: Sat, 31 Oct 2020 20:17:34 -0600 Subject: Final death of the NITB, really this time. Message-ID: <77c3f68b-a315-9df2-2ccb-f22ac8ca99e6@rhizomatica.org> Hi all, I just noticed that osmo-bts commit 6d117891c93da969e0ff8b293bef97c699490f2b is the last version that can be brought up by the openBSC aka osmo-nitb. Which makes me wonder now, should the openbsc / osmocom-nitb package continue to be published to repositories? From keith at rhizomatica.org Sun Nov 1 02:27:34 2020 From: keith at rhizomatica.org (Keith) Date: Sat, 31 Oct 2020 20:27:34 -0600 Subject: GGSN operation / feature Message-ID: Hi All, I have scanned 3GPP documents for info on the GGSN IP network facing side, IIUC how the GGSN responds there is "out of scope" - I'm specifically wondering about sending ICMP host unreachable messages in response to packets for IPs that are not currently active in the pool. Sometimes it would happen where I was pinging an IP assigned to an MS while looking at other things in the SGSN and PCU but in the meantime the MS would cycle the PDP context and have a new IP. For this and maybe other reasons I wrote a proof of concept, probably not great code, but working, patch to have the GGSN send ICMP host unreachable. Do you think this is a desirable feature? If so I would try to clean it up and submit to code review. Also if in agreement, would it be worth making it switchable via a vty param? I am thinking of where one might not want the IP space to be probable, although I would assume that kind of thing is best left to the local firewall implementation. Patch here: http://git.osmocom.org/osmo-ggsn/?h=keith%2Ficmp Thanks. K. From dchardware at gmail.com Sun Nov 1 15:55:56 2020 From: dchardware at gmail.com (Sipos Csaba) Date: Sun, 1 Nov 2020 16:55:56 +0100 Subject: NMT-450 Message-ID: Hi Andreas, I pulled the new master, rebuilt my setup from source in a clean state and it works as it should. One more question though: is it possible to use the MNCC socket to connect the NMT-450 network to 2G (via Osmo-BSC), or to SIP via LCR? Thanks again! Regards, Csaba -------------- next part -------------- An HTML attachment was scrubbed... URL: From andreas at eversberg.eu Sun Nov 1 18:37:48 2020 From: andreas at eversberg.eu (Andreas Eversberg) Date: Sun, 1 Nov 2020 19:37:48 +0100 Subject: NMT-450 In-Reply-To: References: Message-ID: Sipos Csaba wrote: > Hi Andreas, > > I pulled the new master, rebuilt my setup from source in a clean state > and it works as it should. > > One more question though: is it possible to use the MNCC socket to > connect the NMT-450 network to 2G (via Osmo-BSC), or to SIP via LCR? > > Thanks again! > > Regards, > Csaba Hi Csaba, you can connect NMT to LCR via MNCC socket. LCR is capable of connecting to SIP. Currently I develop a replacement for MNCC: Osmoc-CC. There will be no need for LCR any more. A SIP connector application can be used to directly interface SIP with osmocom-analog. I might release it next year, if it appears to be stable enough. You mentioned that you got some docs about Hungarian frequency allocation. (The one that helped you to make your phone work.) Can you send me that document? Best regards, Andreas From laforge at osmocom.org Mon Nov 2 08:29:59 2020 From: laforge at osmocom.org (Harald Welte) Date: Mon, 2 Nov 2020 09:29:59 +0100 Subject: GGSN operation / feature In-Reply-To: References: Message-ID: <20201102082959.GJ693266@nataraja> Hi Keith, On Sat, Oct 31, 2020 at 08:27:34PM -0600, Keith wrote: > I have scanned 3GPP documents for info on the GGSN IP network facing > side, IIUC how the GGSN responds there is "out of scope" I'd agree to that. > - I'm specifically wondering about sending ICMP host unreachable messages in > response to packets for IPs that are not currently active in the pool. makes sense. > If so I would try to clean it up and submit to code review. please do, thanks! > Also if in agreement, would it be worth making it switchable via a vty > param? I am thinking of where one might not want the IP space to be > probable, although I would assume that kind of thing is best left to the > local firewall implementation. I think the GGSN "function" should not implement firewall policy. However, given that generating and discarding a potentially very large amount of ICMP host unreachable messages can consume a significant amount of resources, I guess a vty option might make sense. -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From laforge at osmocom.org Mon Nov 2 08:34:07 2020 From: laforge at osmocom.org (Harald Welte) Date: Mon, 2 Nov 2020 09:34:07 +0100 Subject: Final death of the NITB, really this time. In-Reply-To: <77c3f68b-a315-9df2-2ccb-f22ac8ca99e6@rhizomatica.org> References: <77c3f68b-a315-9df2-2ccb-f22ac8ca99e6@rhizomatica.org> Message-ID: <20201102083407.GK693266@nataraja> Hi Keith, On Sat, Oct 31, 2020 at 08:17:34PM -0600, Keith wrote: > I just noticed that osmo-bts commit > 6d117891c93da969e0ff8b293bef97c699490f2b is the last version that can be > brought up by the openBSC aka osmo-nitb. I don't like that, we should not break backwards compatibility without a very good reason. If it's too hard to fix: It would be worth documenting this in the wiki and, ideally, also in OsmoNITB (Readme? Manueal?) itself. > Which makes me wonder now, should the openbsc / osmocom-nitb package > continue to be published to repositories? I think the reasone for that was some "utility" programs (or was it osmo-bsc_nat?) only being built from there. So we are building the openbsc.git packages not for osmo-nitb itself. Maybe we should simply modify the debian control to no longer create osmo-nitb and osmoocom-bsc-sccplite? -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From mykola at kingmuffin.com Wed Nov 4 13:02:05 2020 From: mykola at kingmuffin.com (Mykola Shchetinin) Date: Wed, 4 Nov 2020 15:02:05 +0200 Subject: osmo-st-* projects Message-ID: Hello there! The question out of curiosity. Hard to not notice quite a few of projects written in Smalltalk. Why was cellular network implementation in Smalltalk abandoned? Or was everything in C initially and you just tried out Smalltalk as a possible alternative? What was your thinking back then? Interested to know some history. Thanks a lot! P.S. of course, I see some stuff in Erlang as well, but it has an awesome Diameter support which kind of answers a similar question but related to Erlang. From laforge at osmocom.org Wed Nov 4 19:55:22 2020 From: laforge at osmocom.org (Harald Welte) Date: Wed, 4 Nov 2020 20:55:22 +0100 Subject: osmo-st-* projects In-Reply-To: References: Message-ID: <20201104195522.GA1078888@nataraja> Hi Mykola, On Wed, Nov 04, 2020 at 03:02:05PM +0200, Mykola Shchetinin wrote: > The question out of curiosity. Hard to not notice quite a few of > projects written in Smalltalk. :) > Why was cellular network implementation in Smalltalk abandoned? Holger Freyther, a key co-developer of OpenBSC from the very beginning, and later many other Osmocom projects, had (has?) a particular interest in develping in Smalltalk. He was doing related developments on contract of a customer who also seemed to have an interest in Smalltalk. As Holger has unfortuantely (mostly) departed from Osmocom a few years ago. To the best of my knowledge, there never formed a larger developer community around them. > Or was everything in C initially and you just tried out Smalltalk as a > possible alternative? What was your thinking back then? You'd have to ask Holger specifically for that. > P.S. of course, I see some stuff in Erlang as well, but it has an > awesome Diameter support which kind of answers a similar question but > related to Erlang. The Osmocom Erlang projects also have had a similar fate than the smalltalk ones, at least as far as I can tell. I became intereted in Erlang at some point, and still think it is an awesome environment specifically for the telecom problem domain in which Osmocom works. For sure all of the control plane stuff could be done very well in Erlang. Unfortuantely, beyond the original company / use case, the Erlang code never really got more users, or contributions, and hence it sits there and bit-rots. Meanwhile, all of the paid contract development that sysmocom is doing is *always* around the existing C-based implementations. Particularly as we are already very late in terms of 2G technology, nobody will set aside resources to re-write something reasonably complex like OsmoBSC or OsmoMSC in Erlang or any other programming language. It would be spending man-years of work just to get to the functionality that already exists in the C implementation today. So the only real chance to use other programming languages is whenever we create something completely new, from scratch, where we don't need any of the existing C codebase. And that simply hasn't happened, with one very small exception: osmo-diameter2gsup. We might see another glimpse of Erlang in a MEGACO-enabled next-generation osmo-mgw, but that is too early to say at this point. Maybe it will also only be a MEGACO-to-MGCP translator in front of osmo-mgw as we know it today. So in retrospective, what do we learn from this? Once you created a significant code-base in one language/architecture, it is going to be hard to move away from it while working in the same problem space. There are tons of existing infrastructure that you'd have to re-build (msgb, tlv parser, protocol encoder/decoder libraries, VTY, ...), and as more time passes, that amount of code that would need to be reimplemented grows likewise. Regards, Harald -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From afranklin at mailfence.com Fri Nov 6 17:14:27 2020 From: afranklin at mailfence.com (Albert Franklin) Date: Fri, 6 Nov 2020 18:14:27 +0100 (CET) Subject: pySim incorrectly detecting as OpenCells-SIM? Message-ID: <71114296.779393.1604682867622@ichabod.co-bxl> Hello I tried to buy a sysmoISIM-SJA2 but it was not available to my region, so I acquired a Chinese writable sim card with adm keys (https://www.aliexpress.com/item/32813645415.html). With their software I can read PIN, PUK, ADM, ISMI, PLMN, EHPLMN, etc exactly as on the image on the link mentioned. pcsc_scan detected it (even with a weird name) from a Chinese brand manufacture using https://github.com/LudovicRousseau/pcsc-tools/blob/master/smartcard_list.txt. I tried pySim-read and it failed on the end saying that OpenCellsSim' object has no attribute 'read_ehplmn'. I'm sharing the full output if anyone is interested. It's weird because it fails to read ISMI and ICCID for example and other fields. I started recently studying this area, I took a look at pySim code and looks like that it's based on size of data to detect if it's OpenCells or not (which I believe is not my case). Is there a easy way to know if my Chinese card is OpenCells or whatever they are? $ ./pySim-read.py -p 0 Using PC/SC reader interface Reading ... Autodetected card type: OpenCells-SIM ICCID: IMSI: None GID1: ffffffff GID2: ffffffff SMSP: ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff SPN: CMCC Display HPLMN: False Display OPLMN: False PLMNsel: 32d00032d01034f06045f08032f32212f020ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff PLMNwAcT: ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused OPLMNwAcT: 32d0004000 # MCC: 460 MNC: 000 AcT: E-UTRAN 32d0008000 # MCC: 460 MNC: 000 AcT: UTRAN 32d0000080 # MCC: 460 MNC: 000 AcT: GSM ... ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused HPLMNAcT: 32d0004000 # MCC: 460 MNC: 000 AcT: E-UTRAN 32d0008000 # MCC: 460 MNC: 000 AcT: UTRAN 32d0000080 # MCC: 460 MNC: 000 AcT: GSM ACC: ffff MSISDN: Not available Administrative data: 00000002 MS operation mode: normal operation Ciphering Indicator: disabled SIM Service Table: ff33ffff00003f033000f0c3 Service 1 - CHV1 disable function Service 2 - Abbreviated Dialling Numbers (ADN) Service 3 - Fixed Dialling Numbers (FDN) Service 4 - Short Message Storage (SMS) Service 5 - Advice of Charge (AoC) Service 6 - Capability Configuration Parameters (CCP) Service 7 - PLMN selector Service 8 - RFU Service 9 - MSISDN Service 10 - Extension1 Service 13 - Last Number Dialled (LND) Service 14 - Cell Broadcast Message Identifier Service 17 - Service Provider Name Service 18 - Service Dialling Numbers (SDN) Service 19 - Extension3 Service 20 - RFU Service 21 - VGCS Group Identifier List (EFVGCS and EFVGCSS) Service 22 - VBS Group Identifier List (EFVBS and EFVBSS) Service 23 - enhanced Multi-Level Precedence and Pre-emption Service Service 24 - Automatic Answer for eMLPP Service 25 - Data download via SMS-CB Service 26 - Data download via SMS-PP Service 27 - Menu selection Service 28 - Call control Service 29 - Proactive SIM Service 30 - Cell Broadcast Message Identifier Ranges Service 31 - Barred Dialling Numbers (BDN) Service 32 - Extension4 Service 49 - MExE Service 50 - Reserved and shall be ignored Service 51 - PLMN Network Name Service 52 - Operator PLMN List Service 53 - Mailbox Dialling Numbers Service 54 - Message Waiting Indication Status Service 57 - Multimedia Messaging Service (MMS) Service 58 - Extension 8 Traceback (most recent call last): File "./pySim-read.py", line 255, in (res, sw) = card.read_ehplmn() AttributeError: 'OpenCellsSim' object has no attribute 'read_ehplmn' As I can't buy the sysmoISIM-SJA2 where I live, I searched for other sellers. I found this one (https://www.aliexpress.com/i/32272726951.html) where an user wrote "+ Devices work. + Use GRSIMWrite to program them initially. After you do this, you will know PIN-ADM so then pysim will work. - PsiWords could spend a little time pointing people at correct software to program cards. That would be, as they like to say, much more professional! (Especially if they want repeat business!) 21 Aug 2018 16:43". I'm curious if this card sold by other user just have a different encoding / format to read/write data from mine, because the PIN + ADM keys I also can obtain from their software, however, since my card is in another format I don't believe that I will have success to write it. Am I wrong? I saw the list of supported SIM cards and some of them are very limited. Someone already acquired a SIM card with great compatibility with pysim from China? I searched for supersim, fakemagicsim and some combinations and no success. fakemagicsim supersim magicsim grcardsim sysmosim-gr1 sysmoSIM-GR2 sysmoUSIM-GR1 sysmoUSIM-SJS1 Fairwaves-SIM OpenCells-SIM Wavemobile-SIM sysmoISIM-SJA2 Any help or advise is very welcome. --? Sent with https://mailfence.com Secure and private email From ivan.babanov at gmail.com Tue Nov 10 22:26:01 2020 From: ivan.babanov at gmail.com (Ivan Babanov) Date: Wed, 11 Nov 2020 01:26:01 +0300 Subject: Ericsson RBS-2206 startup with OSMO Message-ID: Hello all! I'm still trying to bring onAir any of BTS in lab. Today we were trying with Ericsson RBS-2206. We limited hardware to the minimal possible setup containing: DXU-21 dTRU-1800 CDU-G 1800 And we created IDB with 1 cell 1TX 2RX After it we tried to use default config from master branch initially created for RBS-2308. It worked pretty fine except RF Power which was configured as 41dBm and 41 - 12 = 29 dBm. Value 29 was not acceptable for our RBS. I checked with Ericsson BSC Doc and found that our RBS2206 has max RF output 47dBm for DCS1800. (btw, RBS2308 has only 34dBm max output according to the same document, maybe config needs to be corrected) After setting 47dBm to config, TX-0 was configured correctly and Operational led was on. The main problem we are faced now is unavailability to perform "Enable"action on TX and RX objects and all next steps are not successful too. After getting logs from RBS (all files are attached) I see that TX and RX enabling fails with line: [20-11-03 11:51:27.264] 0\RC_HWU_TX hwu_tx_state.c:223 TRACED:TX Enable FAILED!, RCFW_ATC_State NOT Synchronized Looks like internal oscillator is not ready. So, the question is how to make internal oscillator synchronized? Could it be an E1 Sync stability issue caused by Digium cards? I remember we discussed it on earlier steps of bringing up OSMO-BSC. Now I have just 2 ideas what to do: 1. Set Digium card to get Sync from RBS. Now Digium is configured for Internal clocking and acts as master. Maybe in case when both sides will be configured to get sync from E1 it will decrease difference between internal clock of RBS and E1 and RBS will get Synced state. 2. Theoretically I can try to use Nokia DX200 BSC as a clock master for Digium and deliver sync to RBS from Digium. I'm not sure if timing accuracy is the same for Nokia and Ericsson HW. One more question is where can I find some info about timing accuracy for BTS and any possible way to check it on the existing E1 line? Thank you Babanov Ivan -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- DXU 0 log ************** **** Detailed log **** [90-01-01 00:00:00.010] NONAME debug_handlers.c:810 TRACED:No sys_env_board_type [90-01-01 00:00:00.010] NONAME debug_main.c:2909 TRACEH:OS-info: OSE Delta PowerPC krn-4xx/P2.3.2.0 [90-01-01 00:00:00.010] NONAME debug_main.c:2941 TRACEH:No restart info [90-01-01 00:00:00.010] NONAME debug_main.c:2956 TRACEH:Reset time: Not set [90-01-01 00:00:00.010] NONAME debug_main.c:3066 TRACEH:Load file=DXPR41GZ Program version=VEP-PPU CXC1121730_19.R1L01, System start cause=POWER_ON(0), Appl type=LFINFO_UPDATED_APPL(1) [90-01-01 00:00:00.016] NONAME bios_device.c:318 TRACED:ata_block_data.Num_Blocks=125440, ata_block_data.Block_Size=512 [90-01-01 00:00:00.028] P_MPSF_MICROSM microsm.c:1107 TRACEH:OK: entering COLDSTART phase [90-01-01 00:00:00.028] P_MPSF_MICROSM microsm.c:404 TRACED:OK: RAM configured, start = 0x0, size = 0x1d00000, TLB usage = 27 (/64). [90-01-01 00:00:00.028] P_MPSF_MICROSM microsm.c:407 TRACED:OK: POOL configured, start = 0x400000, size = 0xb00000. [90-01-01 00:00:00.274] P_MPSF_MICROSM microsm.c:763 TRACED:OK: Loaded MPSC_SHLIB, PAD: f04000 [90-01-01 00:00:00.698] P_MPSF_MICROSM microsm.c:763 TRACED:OK: Loaded MPSO, PAD: f14000 [90-01-01 00:00:00.706] P_MPSS_LSM lsm_loader.c:4262 TRACEH:RBS Family: 0 [90-01-01 00:00:00.706] P_MPSS_LSM lsm_loader.c:4277 TRACEH:Board type (hex): 9 [90-01-01 00:00:00.708] P_MPSS_LSM lsm_file_info.c:2323 TRACED:init w.t. 0 [90-01-01 00:00:00.828] P_MPSF_MICROSM microsm.c:861 TRACED:OK: Started program: MPSO, PAD: f14000, IAD: f52000 [90-01-01 00:00:00.868] P_MPSS_LSM lsm_loader.c:4051 TRACED:zf_start = 0x10001000 [90-01-01 00:00:00.868] P_MPSS_LSM lsm_loader.c:4061 TRACED:Area NOT OK [90-01-01 00:00:00.868] P_MPSS_LSM lsm_loader.c:4062 TRACED:Initializing.... [90-01-01 00:00:00.870] P_MPSS_LSM lsm_loader.c:4070 TRACED:DONE [90-01-01 00:00:00.870] P_MPSS_LSM lsm_loader.c:4073 TRACED:ZF in NVRam Rev=-------- Size=0x0 (0) [90-01-01 00:00:00.870] P_MPSS_LSM lsm_file_info.c:1049 TRACED:LFIF LI=CXC1122176_1,R2 [90-01-01 00:00:00.870] P_MPSS_LSM lsm_file_info.c:1073 TRACED:Known LFIF CXC1122176_1, R2 [90-01-01 00:00:00.870] P_MPSS_LSM lsm_file_info.c:1049 TRACED:LFIF OLI=CXC1122176_1,R1A [90-01-01 00:00:00.876] P_MPSS_LSM lsm_loader.c:4648 TRACED:LFIF len=33192 npgm=3 res=1 [90-01-01 00:00:01.070] P_MPSS_LSM lsm_file_info.c:1591 TRACED:FEFC enabled at startup [90-01-01 00:00:01.070] P_MPSS_LSM lsm_file_info.c:1687 TRACEH:FilePckgName:CXP1040007_09R41G [90-01-01 00:00:08.842] P_MPSS_LSM lsm_file_info.c:3739 TRACED:Application DXPR39EZ [90-01-01 00:00:08.854] P_MPSS_LSM lsm_file_info.c:3739 TRACED:Application DXPR41GZ [90-01-01 00:00:09.080] P_MPSS_LSM lsm_file_info.c:3739 TRACED:Application TRBR09FB [90-01-01 00:00:09.556] P_MPSS_LSM lsm_file_info.c:3739 TRACED:Application [90-01-01 00:00:10.030] P_MPSK_DBG_MAIN debug_main.c:1209 TRACEH:System load: 99.6% [90-01-01 00:00:10.408] P_MPSS_LSM lsm_file_info.c:3739 TRACED:Application ECBR09FB [90-01-01 00:00:10.868] P_MPSS_LSM lsm_file_info.c:3739 TRACED:Application [90-01-01 00:00:18.052] P_MPSS_LSM lsm_file_info.c:3739 TRACED:Application TRPR41GZ [90-01-01 00:00:18.062] P_MPSS_LSM lsm_file_info.c:3739 TRACED:Application [90-01-01 00:00:18.072] P_MPSS_LSM lsm_file_info.c:3739 TRACED:Application [90-01-01 00:00:18.082] P_MPSS_LSM lsm_file_info.c:3739 TRACED:Application [90-01-01 00:00:18.092] P_MPSS_LSM lsm_file_info.c:3739 TRACED:Application [90-01-01 00:00:18.102] P_MPSS_LSM lsm_file_info.c:3739 TRACED:Application [90-01-01 00:00:18.112] P_MPSS_LSM lsm_file_info.c:3739 TRACED:Application [90-01-01 00:00:18.122] P_MPSS_LSM lsm_file_info.c:3739 TRACED:Application [90-01-01 00:00:18.122] P_MPSS_LSM lsm_loader.c:2546 TRACED:Selected FLBI_P_D from application SW loadfile. [90-01-01 00:00:18.440] P_MPSF_MICROSM microsm.c:763 TRACED:OK: Loaded FLASH_SHLIB, PAD: f65000 [90-01-01 00:00:18.464] P_MPSS_LSM lsm_loader.c:2546 TRACED:Selected BIOS_P_D from application SW loadfile. [90-01-01 00:00:18.958] P_MPSF_MICROSM microsm.c:763 TRACED:OK: Loaded BIOS_SHLIB, PAD: f72000 [90-01-01 00:00:19.436] P_MPSF_MICROSM microsm.c:763 TRACED:OK: Loaded MPSS, PAD: f92000 [90-01-01 00:00:19.510] P_MPSF_MICROSM bios_device.c:265 TRACED:ata_block_data.Num_Blocks=125440, ata_block_data.Block_Size=512 [90-01-01 00:00:19.520] P_MPSF_MICROSM microsm.c:861 TRACED:OK: Started program: MPSS, PAD: f92000, IAD: ff0000 [90-01-01 00:00:19.522] P_MPSS_HWDB_HNDL HardwareDB.c:802 TRACED:MPSS-PPU CXC1121731_21.R1G01 running [90-01-01 00:00:19.522] P_MPSS_HWDB_HNDL HardwareDB.c:838 TRACEH:RBS Family: 0 [90-01-01 00:00:19.526] P_MPSS_HWU_MAIN hwuadm_main.c:395 TRACEH:RBS Family: 0 [90-01-01 00:00:19.528] P_MPSS_HWU_MAIN hwuadm_main.c:321 TRACEH:RU Type = 6 [90-01-01 00:00:19.530] P_MPSS_HWDB_HNDL HardwareDB.c:738 TRACED:Parameter PD0011 not found [90-01-01 00:00:19.530] P_MPSS_HWDB_HNDL HardwareDB.c:738 TRACED:Parameter PD0010 not found [90-01-01 00:00:19.530] P_MPSS_HWDB_HNDL HardwareDB.c:738 TRACED:Parameter PT0008 not found [90-01-01 00:00:19.530] P_MPSS_HWDB_HNDL HardwareDB.c:738 TRACED:Parameter PD4002 not found [90-01-01 00:00:19.530] P_MPSS_HWDB_HNDL HardwareDB.c:1272 TRACED:Parameter PD4002 not found [90-01-01 00:00:19.534] P_MPSS_LSM lsm_loader.c:3081 TRACEH:InternalState = _hwu [90-01-01 00:00:19.552] P_MPSS_NVRM_HNDL NV_Ram.c:467 TRACED:max entry 32767, start 10005000 [90-01-01 00:00:19.552] P_MPSS_NVRM_HNDL NV_Ram.c:636 TRACED:Initializing NVRAM... [90-01-01 00:00:20.546] P_MPSS_MMI_HNDL LED.c:963 TRACEH:MMI indication for LED_Local state FLASH [90-01-01 00:00:20.796] P_TRNSC_CPA trnscpa.c:483 TRACED:TRNC-PPU CXC1121734_20.R10A01 running [90-01-01 00:00:20.810] P_ECBUS_UCC ecbus_ucc_main.c:928 TRACED:ECBUS_UCC Process stopped, on BoardType: 9 [90-01-01 00:00:20.812] P_ECBUS_SWITCH ecbus_switch.c:549 TRACED:ECBUS_UCC Process stopped, on BoardType: 9 [90-01-01 00:00:20.812] P_CPRI_ARM_M_MN cpri_arm_master_main.c:4380 TRACED:P_CPRI_ARM_MASTER_MOUNTER Process stopped, not valid for RBS2000 [90-01-01 00:00:20.812] P_ECBUS_NRM_M_MN ecbus_nrm_master_main.c:3270 TRACED:P_ECBUS_NRM_MASTER_MOUNTER Process stopped, on BoardType: 9 [90-01-01 00:00:20.814] xDCserver linx_lower_proxy.c:282 TRACED:xDCserver Process stopped, on BoardType: 9 [90-01-01 00:00:20.830] TRNS_PATSY_CONF patsy_conf.c:6447 TRACED:HWU pid 0x10030 [90-01-01 00:00:20.842] P_MPSS_LSM lsm_loader.c:2914 TRACED:Started TRNSC, errCode 0, iad 1129000 [90-01-01 00:00:20.944] P_MPSS_LSM lsm_file_info.c:1635 TRACED:Using LI main DEST=D21 [90-01-01 00:00:20.946] P_MPSS_LSM lsm_loader.c:2084 TRACED:Prefer $$$$_P_D [90-01-01 00:00:20.946] P_MPSS_LSM lsm_loader.c:2084 TRACED:Prefer $$_mac_p [90-01-01 00:00:20.946] P_MPSS_LSM lsm_loader.c:2084 TRACED:Prefer $recp [90-01-01 00:00:20.970] PLS_COM_L1 sio.c:835 TRACED:baud[1 -> 1] [90-01-01 00:00:20.970] SPI_CTRL_MAIN spi_controller_main.c:559 TRACED:SPI Physical IO addr 5001C000, Virtual IO addr 10000000 [90-01-01 00:00:20.972] PLS_COM_L1 sio.c:844 TRACED:UART initialized [90-01-01 00:00:20.976] PLS_SIO_GPS sio_gps.c:724 TRACED:UART initialized [90-01-01 00:00:21.256] P_NPSENSORS npsensors.c:1028 TRACED:DXU sensor set [90-01-01 00:00:21.256] P_NPSENSORS npsensors.c:3155 TRACED:Create a TEMP_IN_ sensor in ODB [90-01-01 00:00:21.256] P_NPSENSORS npsensors.c:3155 TRACED:Create a TEMP_IN_ sensor in ODB [90-01-01 00:00:21.292] P_HWU_CABINET hwucabinet.c:766 TRACED:EEPROM type = X24645 [90-01-01 00:00:21.396] P_MPSS_LSM lsm_loader.c:4117 TRACED:Load files in file package of executing application: ZFJR41GZ DXPR41GZ [90-01-01 00:00:21.396] P_MPSS_LSM lsm_loader.c:4117 TRACED:TRPR41GZ ECAR41GZ TRAR41GZ ECXR09FZ TRXR09FZ DXLR06ES ECLR06ES TRLR06ES [90-01-01 00:00:21.396] P_MPSS_LSM lsm_loader.c:4123 TRACED:DXBR09FB ECBR09FB TRBR09FB [90-01-01 00:00:21.410] TRNS_PATSY_SUP patsy_supp.c:5557 TRACED:Opened file:dn_patsy_bin Rev:R7A01 Size:208KBytes [90-01-01 00:00:21.420] TRNS_PATSY_SUP patsy_supp.c:5557 TRACED:Opened file:dn_self_test_bin Rev:7.4.0 Size:208KBytes [90-01-01 00:00:22.166] P_MPSS_LSM lsm_loader.c:3776 TRACED:SetInstList, inst 0, n_func 2 [90-01-01 00:00:22.180] P_MPSS_HWU_MAIN hwuadm_main.c:1475 TRACED:FuncType[0] = 0 FuncInst[0] = 0 [90-01-01 00:00:22.180] P_MPSS_HWU_MAIN hwuadm_main.c:1475 TRACED:FuncType[1] = 2 FuncInst[1] = 0 [90-01-01 00:00:22.200] P_TRNSC_NBS NBS_Bport_handler.c:621 TRACED:(local_bus) Connect the ISL channel on LB [90-01-01 00:00:22.200] TRNS_PATSY_CONF patsy_conf.c:1169 TRACED:Changing the IFF for hdlc_ch 0 new value 0xFF [90-01-01 00:00:22.222] P_MPSS_LSM lsm_loader.c:3500 TRACEH:OperationalReport from TRNSC [90-01-01 00:00:22.722] P_MPSS_LSM lsm_loader.c:3865 TRACEH:Waiting for internal report [90-01-01 00:00:22.722] P_MPSS_LSM lsm_loader.c:3081 TRACEH:InternalState = _inst [90-01-01 00:00:22.956] ISM_Y2_PROC1 ism_y2.c:1982 TRACED:New active channel 1025 [90-01-01 00:00:22.960] CENTRAL_ODB codb.c:207 TRACED:OK: Central ODB running: pid = 65636 (0x10064) [90-01-01 00:00:22.960] CENTRAL_ODB codb.c:355 TRACED:OK: Central Local ODB connected: pid=131108 (0x20024) lodb_ref=1 [90-01-01 00:00:22.960] LOCAL_ODB local_odb.c:2440 TRACED:OK: Connected to Central ODB [90-01-01 00:00:22.966] P_LOADER csm_loader.c:2730 TRACED:MPSR-PPU CXC1121732_19.R1F01 running [90-01-01 00:00:22.970] P_LINX_GW_MGR LinxGatewayManager.c:546 TRACED:P_LINX_GW_MGR Process stopped, on BoardType: 9 [90-01-01 00:00:22.970] P_MPSS_LSM lsm_loader.c:2914 TRACED:Started MPSR, errCode 0, iad 1196000 [90-01-01 00:00:22.970] P_MPSS_LSM lsm_loader.c:2546 TRACED:Selected ec_mac_p from application SW loadfile. [90-01-01 00:00:23.664] EC_Main ./TMP/C//EC_MainClass.cpp:90 TRACED:EC_SW CXC116102_20 R1E01 (2012-10-03) [90-01-01 00:00:23.674] P_MPSS_LSM lsm_loader.c:2914 TRACED:Started EC, errCode 0, iad 1238000 [90-01-01 00:00:24.276] O_LOMP_Main LOMP1.c:892 TRACED:Info: (LOMP_SW6 CXC1125822_19.R1AC01) [90-01-01 00:00:24.294] P_MPSS_LSM lsm_loader.c:2914 TRACED:Started LOMP, errCode 0, iad 12ca000 [90-01-01 00:00:25.014] O_IDB_Main IDBP.c:3615 TRACED:Info: (IDBP_SW6 CXC1125821_19.R1J01) [90-01-01 00:00:25.016] P_MPSS_LSM lsm_loader.c:2914 TRACED:Started IDBP, errCode 0, iad 1379000 [90-01-01 00:00:25.192] O_IDB_Main ../TMP/C/IDB_Storage.c:1053 TRACEH:CONFIG - IDB structure rev 50:0 (Init cont rev R60D) [90-01-01 00:00:25.192] O_IDB_Main ../TMP/C/IDB_Storage.c:1073 TRACEH:CONFIG - Config Name 2206 SCC 1X2 [90-01-01 00:00:25.192] O_IDB_Main ../TMP/C/IDB_Storage.c:1084 TRACEH:CONFIG - Cabinet 0 [90-01-01 00:00:25.192] O_IDB_Main ../TMP/C/IDB_Storage.c:1106 TRACEH:CONFIG - Type:9 Variant:0 Climate system: 6 Power system: 15 [90-01-01 00:00:25.192] O_IDB_Main ../TMP/C/IDB_Storage.c:1117 TRACEH:CONFIG - Basic Configuration Sectors A: 5616, B: 0, C: 0 [90-01-01 00:00:25.670] P_MPSM_ENTRY remp_entry.c:205 TRACED:REMP process stopped due to rbs family [90-01-01 00:00:25.670] P_MPSS_LSM lsm_loader.c:2914 TRACED:Started MPSM, errCode 0, iad 13d0000 [90-01-01 00:00:25.670] P_MPSS_LSM lsm_loader.c:3500 TRACEH:OperationalReport from EC [90-01-01 00:00:25.672] P_MPSS_LSM lsm_loader.c:3500 TRACEH:OperationalReport from LOMP [90-01-01 00:00:25.672] P_MPSS_LSM lsm_loader.c:3500 TRACEH:OperationalReport from IDBP [90-01-01 00:00:25.672] P_MPSS_LSM lsm_loader.c:3500 TRACEH:OperationalReport from MPSM [90-01-01 00:00:25.674] P_MPSS_LSM lsm_loader.c:3500 TRACEH:OperationalReport from MPSR [90-01-01 00:00:25.676] P_MPSS_LSM lsm_loader.c:3055 TRACEH:TraceH_Checkpoint: NodeStartState = SWConsistency [90-01-01 00:00:25.676] P_MPSS_LSM lsm_loader.c:3081 TRACEH:InternalState = _test [90-01-01 00:00:26.208] TSC_CO_Timing co_timing.c:342 TRACED:Product CXC1121724_18 TSC_SW version R5E01 [90-01-01 00:00:26.212] TSC_Regulation start_regulation.c:151 TRACED:>>> Init HW (Garp), TDM-part [90-01-01 00:00:26.214] P_MPSS_LSM lsm_loader.c:2914 TRACED:Started TSC, errCode 0, iad 1440000 [90-01-01 00:00:26.214] P_MPSS_LSM lsm_loader.c:2546 TRACED:Selected crecp from application SW loadfile. [90-01-01 00:00:26.798] CREC_MAIN crec_main.c:245 TRACED:CREC_SW R5A02 CXC1121725_18 [90-01-01 00:00:26.822] IOM_DRV iom_drv.c:1043 TRACED:found:CDU i2c-Bus No:1; i2c-addr = 64 [90-01-01 00:00:26.824] IOM_DRV iom_drv.c:3355 TRACED:Initialize port for bus 0 pio_port 0 [90-01-01 00:00:26.828] P_MPSS_LSM lsm_loader.c:2914 TRACED:Started CREC, errCode 0, iad 14de000 [90-01-01 00:00:26.828] P_MPSS_LSM lsm_loader.c:3500 TRACEH:OperationalReport from CREC [90-01-01 00:00:26.828] P_LOADER csm_oper.c:262 TRACED:FilePath /GLOBAL/TRP_HDR 0 192 [90-01-01 00:00:26.840] TSC_Regulation start_regulation.c:245 TRACED:--- No SPI_DAC support on HW. [90-01-01 00:00:26.842] CENTRAL_ODB codb.c:364 TRACED:OK: Other Local ODB connected: pid=65679 (0x1008F) lodb_ref=2 [90-01-01 00:00:26.856] P_TRNSC_NBS NBS_main.c:871 TRACED:Connected TRX#0 [90-01-01 00:00:26.858] P_TRNSC_NBS NBS_main.c:871 TRACED:Connected TRX#1 [90-01-01 00:00:26.864] TSC_Regulation nvram_lib.c:343 TRACEH:RAM attach OK: 0 10006000 1000 [90-01-01 00:00:26.864] TSC_Regulation start_regulation.c:390 TRACED:No NVRAM-record regulation_rec, waiting for IDB_Ready [90-01-01 00:00:27.630] EC_Main MP/C//EpcBusL3Manager.cpp:435 TRACED:Configuration changed, New HWU 5, Existing 0 [90-01-01 00:00:30.030] P_MPSK_DBG_MAIN debug_main.c:1216 TRACEH:System load: 61.7% [90-01-01 00:00:32.218] O_LocalIDB /IC/LocalIDB_CDU_Cache.ic:926 TRACED:Max PPC IDB area size=131072 bytes [90-01-01 00:00:32.218] O_LocalIDB /IC/LocalIDB_CDU_Cache.ic:927 TRACED:Current IDB used size=37015 bytes [90-01-01 00:00:32.218] O_LocalIDB /IC/LocalIDB_CDU_Cache.ic:928 TRACED:Left IDB size=64617 bytes [90-01-01 00:00:32.222] O_LocalIDB LOMP1.c:18179 TRACEH:Checkpoint: NodeStartState = IDB_Consistency. [90-01-01 00:00:32.226] TSC_Regulation start_regulation.c:665 TRACED:>>> Init HW (Garp), PDM-part [90-01-01 00:00:32.236] P_TRNSC_DLMAN dlman.c:1926 TRACED:Create pending link: CF [90-01-01 00:00:32.240] P_TRNSC_DLMAN dlman.c:1926 TRACED:Create pending link: RemoteOMT [90-01-01 00:00:32.240] P_TRNSC_DLMAN dlman.c:1926 TRACED:Create pending link: RemoteDVT [90-01-01 00:00:32.284] IOM_DRV iom_drv.c:1102 TRACED:found:CXU i2c-Bus No:1 [90-01-01 00:00:32.284] IOM_DRV iom_drv.c:3355 TRACED:Initialize port for bus 0 pio_port 1 [90-01-01 00:00:32.292] CREC_TG tg_equip_ctrl_init.c:266 TRACED:CDU-0 is of type CDU_G or CDU_J [90-01-01 00:00:32.292] CREC_TG tg_equip_ctrl_init.c:344 TRACED:Choosen supervision type: 0 [90-01-01 00:00:32.292] CREC_TG tg_equip_ctrl_init.c:345 TRACED:0=TG_LIMITED_SUP, 1=TG_LIMITED_SUP_CDUL, 2=TG_NORMAL_SUP [90-01-01 00:00:32.292] CREC_TG tg_equip_ctrl_init.c:346 TRACED:3=TG_NORMAL_SUP_CDUL, 4=TG_MIXED_CONF [90-01-01 00:00:32.298] P_PCM_GENERAL pcm_general.c:2493 TRACED:Received a CO_NI_SubscribeCapabilitiesRsp [90-01-01 00:00:32.300] EC_Main C//ClimateCtrlManager.cpp:1126 TRACED:INFO: Configured as Cabinet 2206, CabinetFactor 4.1 [90-01-01 00:00:32.306] EC_Main C//ClimateCtrlManager.cpp:290 TRACED:Limit for low temp, class2 set to 0.0C [90-01-01 00:00:32.306] EC_Main C//ClimateCtrlManager.cpp:292 TRACED:Limit for low temp, class1 set to -10.0C [90-01-01 00:00:32.316] EC_Main MP/C//EpcBusL3Manager.cpp:1515 TRACED:No of PSU: DC/DC Opto = 4, AC/DC Opto = 0, IDB = 4 [90-01-01 00:00:32.316] EC_Main MP/C//EpcBusL3Manager.cpp:1566 TRACED:No of FCU: Opto = 1, IDB = 1 [90-01-01 00:00:32.316] EC_Main MP/C//EpcBusL3Manager.cpp:1641 TRACED:No of FAN: IDB = 4 [90-01-01 00:00:32.316] EC_Main P/C//PowerCtrlManager.cpp:227 TRACED:PSU_PS_Capabilities updated to 1 [90-01-01 00:00:32.316] EC_Main P/C//PowerCtrlManager.cpp:229 TRACED:Number of expected PSUs changed to 4. [90-01-01 00:00:32.320] P_TRNSC_PCM_DRV pcm_drv_ext.c:996 TRACED:Configure for PCM_CRC4_MF [90-01-01 00:00:32.320] P_TRNSC_PCM_DRV pcm_drv_ext.c:996 TRACED:Configure for PCM_CRC4_MF [90-01-01 00:00:32.320] P_TRNSC_PCM_DRV pcm_drv_ext.c:996 TRACED:Configure for PCM_CRC4_MF [90-01-01 00:00:32.320] P_TRNSC_PCM_DRV pcm_drv_ext.c:996 TRACED:Configure for PCM_CRC4_MF [90-01-01 00:00:32.322] TSC_Regulation hw_driver_garp.c:802 TRACED:Ref source UNDEFINED. Initalizing PDM Status only. [90-01-01 00:00:32.322] TSC_Regulation gps_specific.c:4306 TRACED:Seed = 32 [90-01-01 00:00:32.322] TSC_Regulation gps_specific.c:4392 TRACED:Frequency offset for GPS synch = -7 ppb [90-01-01 00:00:32.324] PLS_SIO_GPS sio_gps.c:793 TRACED:START_LINK first time [90-01-01 00:00:32.324] PLS_SIO_GPS sio_gps.c:812 TRACED:START_LINK OK: [90-01-01 00:00:32.324] TSC_CO_Timing start_co_timing.c:326 TRACED:LocalConfigRsp received with interfaceType 4 [90-01-01 00:00:32.326] TSC_CO_Timing hw_driver_garp.c:1798 TRACED:TBus enabled [90-01-01 00:00:32.328] TSC_Regulation gps_specific.c:3830 TRACED:GPS data(IDB),GPS_Present=0,GPS_RX_delay=0,GPS_RX_DXU=0 [90-01-01 00:00:32.328] TSC_Regulation gps_specific.c:4515 TRACED:New GPS delay=17940 [90-01-01 00:00:32.328] TSC_Regulation regulation.c:4046 TRACED:RBS_TF_HoldoverMode received = 0 , 0=IntraCell, 1=InterCell [90-01-01 00:00:32.334] TSC_CO_Timing hw_driver_garp.c:1283 TRACED:NO! TRAFFIC ON SBUS [90-01-01 00:00:32.334] TSC_Regulation regulation.c:1748 TRACED:Send subscrSynchStateRsp: synched 0, frame 0, exec 0, source 0, fsOundef 1 [90-01-01 00:00:32.334] P_MPSS_LSM lsm_loader.c:3500 TRACEH:OperationalReport from TSC [90-01-01 00:00:32.334] P_MPSS_LSM lsm_loader.c:3059 TRACEH:TraceH_Checkpoint: NodeStartState = PlatformOperational [90-01-01 00:00:32.340] TSC_CO_Timing co_timing.c:1288 TRACED:tscESBdelayList.noOfEntries: 0 [90-01-01 00:00:32.340] TSC_CO_Timing co_timing.c:1330 TRACED:RBS_TF_HoldoverMode received = 0 , 0=IntraCell, 1=InterCell [90-01-01 00:00:32.362] O_IDB_Main ../TMP/C/IDB_FDB.c:364 TRACED: Incorrect RU_SerialNumber: s763468129 on CABINET_S, inst. 0 [90-01-01 00:00:32.420] TSC_CO_Timing co_timing.c:516 TRACED:Received DX_DB_Client_DX_DB_Ready [90-01-01 00:00:32.422] P_NPSENSORS npsensors.c:2632 TRACED:IDB reported NOT ok [90-01-01 00:00:32.426] TSC_CO_Timing co_timing.c:1058 TRACED:No parameter RD0010, using already stored defaultvalues [90-01-01 00:00:32.426] TSC_CO_Timing co_timing.c:1067 TRACED:ESB Internal Delays: TX 1956, RX 4641, Loop 57 (capTxChainDelay 16013) [90-01-01 00:00:32.426] TSC_Regulation regulation.c:4117 TRACED:FD_Identity.RevisionData: R5B [90-01-01 00:00:32.430] P_NPSENSORS npsensors.c:2632 TRACED:IDB reported NOT ok [90-01-01 00:00:32.450] TSC_CO_Timing co_timing.c:1147 TRACED:No ESB_Support parameter in RU_DB. Default params is set to: 1 [90-01-01 00:00:32.450] TSC_CO_Timing co_timing.c:1212 TRACED:This RBS is set to handle MASTER, STANDALONE and SLAVE Configurations! [90-01-01 00:00:32.452] TSC_Regulation regulation.c:4168 TRACED:gpsDelays.internal = 65 [90-01-01 00:00:32.452] TSC_Regulation gps_specific.c:4515 TRACED:New GPS delay=18005 [90-01-01 00:00:32.464] TSC_Regulation regulation.c:2235 TRACED:Start use CV from DB: 8576 [90-01-01 00:00:32.498] O_IDB_Main ../TMP/C/IDB_FDB.c:364 TRACED: Incorrect RU_SerialNumber: s763468129 on CABINET_S, inst. 0 [90-01-01 00:00:32.502] O_IDB_Main ../TMP/C/IDB_FDB.c:364 TRACED: Incorrect RU_SerialNumber: s763468129 on CABINET_S, inst. 0 [90-01-01 00:00:32.508] O_IDB_Main ../TMP/C/IDB_FDB.c:364 TRACED: Incorrect RU_SerialNumber: s763468129 on CABINET_S, inst. 0 [90-01-01 00:00:32.514] O_IDB_Main ../TMP/C/IDB_FDB.c:364 TRACED: Incorrect RU_SerialNumber: s763468129 on CABINET_S, inst. 0 [90-01-01 00:00:32.518] O_IDB_Main ../TMP/C/IDB_FDB.c:364 TRACED: Incorrect RU_SerialNumber: s763468129 on CABINET_S, inst. 0 [90-01-01 00:00:32.826] TSC_Regulation regulation.c:4680 TRACED:NEW TEMP_COMP_MODE: 0 [90-01-01 00:00:32.826] TSC_Regulation regulation.c:1748 TRACED:Send subscrSynchStateRsp: synched 0, frame 0, exec 0, source 0, fsOundef 1 [90-01-01 00:00:32.826] TSC_CO_Timing methods.c:1321 TRACED:ESB State was allready off [90-01-01 00:00:33.324] P_PCM_GENERAL pcm_general.c:3730 TRACED:Port A B C D avail 1 0 0 0 error 0 1 1 1 Source_Ref 0 0 Freq_Ref 0 0 [90-01-01 00:00:33.334] TSC_Regulation regulation.c:4680 TRACED:NEW TEMP_COMP_MODE: 4 [90-01-01 00:00:33.578] IOM_DRV iom_drv.c:1312 TRACED:Reading CDU OK 1121 bytes [90-01-01 00:00:33.580] CREC_CD hwu_common.c:943 TRACED:Number of configured sub RU:s = 1 [90-01-01 00:00:33.580] CREC_CD hwu_common.c:944 TRACED:Number of found sub RU:s = 1 [90-01-01 00:00:33.620] O_IDB_Main ../TMP/C/IDB_FDB.c:364 TRACED: Incorrect RU_SerialNumber: s763468129 on CABINET_S, inst. 0 [90-01-01 00:00:33.812] O_RBS_Main RBS_Main.c:901 TRACED:Info: (RBS_SW6 CXC1125820_19.R1AB01) [90-01-01 00:00:33.814] O_Extal IC/Extal_adt_RRUS_body.ic:86 TRACED:Alloc and Initial Memory done [90-01-01 00:00:33.814] O_Extal IC/Extal_adt_RRUS_body.ic:86 TRACED:Alloc and Initial Memory done [90-01-01 00:00:33.824] IOM_DRV iom_drv.c:1312 TRACED:Reading CXU OK 2007 bytes [90-01-01 00:00:33.826] CREC_CX hwu_common.c:943 TRACED:Number of configured sub RU:s = 1 [90-01-01 00:00:33.826] CREC_CX hwu_common.c:944 TRACED:Number of found sub RU:s = 1 [90-01-01 00:00:33.854] CREC_CX hwu_cx.c:2089 TRACED:CXU data to write = 1111111111111011 [90-01-01 00:00:33.876] O_IDB_Main ../TMP/C/IDB_FDB.c:364 TRACED: Incorrect RU_SerialNumber: s763468129 on CABINET_S, inst. 0 [90-01-01 00:00:34.102] P_MPSS_MMI_HNDL LED.c:963 TRACEH:MMI indication for LED_TransmissionOK port A state ON [90-01-01 00:00:34.112] P_MPSS_LSM lsm_loader.c:2914 TRACED:Started RBS, errCode 0, iad 1648000 [90-01-01 00:00:34.120] P_MPSS_LSM lsm_loader.c:3500 TRACEH:OperationalReport from RBS [90-01-01 00:00:34.120] P_MPSS_LSM lsm_loader.c:3063 TRACEH:TraceH_Checkpoint: NodeStartState = SystemOperational [90-01-01 00:00:34.218] O_RBS_Status S_StatusFuncFuncTypeAFR.c:792 TRACED:RBS_StatusFuncAFR_Exclude Not Matching:KRC 131 1003/2 R5F . Revisi [90-01-01 00:00:34.220] O_RBS_Status S_StatusFuncFuncTypeAFR.c:792 TRACED:RBS_StatusFuncAFR_Exclude Not Matching:KRC 131 1003/2 R5F . Revisi [90-01-01 00:00:35.878] O_TGC_Main TGC.c:46965 TRACED:Info: (TGC_SW6 CXC1125819_19.R1AC01) [90-01-01 00:00:35.900] P_MPSS_LSM lsm_loader.c:2914 TRACED:Started TGC, errCode 0, iad 170f000 [90-01-01 00:00:35.976] O_TGC_Main TGC.c:9481 TRACED:TGFC object to IDLE state. [90-01-01 00:00:37.128] O_CF_Main CF1.c:4852 TRACED:Info: ( CF_SW6 CXC1125817_19.R1AC01) [90-01-01 00:00:37.188] O_CF_Dnl_0 CF1.c:119284 TRACED:SubscribeFindRsp for Object PowerCtrl received [90-01-01 00:00:37.232] P_MPSS_LSM lsm_loader.c:2914 TRACED:Started CF, errCode 0, iad 17e2000 [90-01-01 00:00:37.338] TSC_CO_Timing co_timing.c:826 TRACED:Timer ESB distribution allowed expired [90-01-01 00:00:37.338] TSC_CO_Timing methods.c:1321 TRACED:ESB State was allready off [90-01-01 00:00:37.686] O_OMT_Serv OMTH.c:10991 TRACED:Info: (OMTH_SW5 CXC1125823_19.R1J01) [90-01-01 00:00:37.688] P_MPSS_LSM lsm_loader.c:2914 TRACED:Started OMTH, errCode 0, iad 1850000 [90-01-01 00:00:37.688] P_MPSS_LSM lsm_loader.c:3117 TRACEH:TraceH_Checkpoint: NodeStartState = ReadyForRemoteMode [90-01-01 00:00:37.688] P_MPSS_LSM lsm_loader.c:3500 TRACEH:OperationalReport from CF [90-01-01 00:00:37.688] P_MPSS_HWDB_HNDL HardwareDB.c:2148 TRACEH:Fast restart allowed [90-01-01 00:00:37.688] O_CF_Main CF1.c:5165 TRACED:NodeStartState: Ready for remote mode [90-01-01 00:00:37.690] P_TRNSC_NBS NBS_links.c:3113 TRACED:>>> ARLL timer started [90-01-01 00:00:38.012] TSC_Regulation gps_specific.c:4454 TRACED:TxChainDelay=17834 for CoTxPath-0 [90-01-01 00:00:38.012] TSC_Regulation gps_specific.c:4515 TRACED:New GPS delay=17899 [90-01-01 00:00:38.014] TSC_CO_Timing co_timing.c:2906 TRACED:TxChainDelay capability changed from 16013 ns to 15907 ns [90-01-01 00:00:38.384] O_RBS_Status RBS_STATUS_DEF.c:398 FAULT:90-01-01 00:00 FuncType: DX, Instance 0, Raise , EC2, SUPPRESS TERR LINK [90-01-01 00:00:38.688] P_MPSS_LSM lsm_loader.c:5493 TRACED:Start CRC bkg check [90-01-01 00:00:38.852] TSC_Regulation gps_specific.c:4454 TRACED:TxChainDelay=17834 for CoTxPath-1 [90-01-01 00:00:38.852] TSC_Regulation gps_specific.c:4515 TRACED:New GPS delay=17899 [90-01-01 00:00:39.294] O_TGC_Main TGC.c:11249 TRACED:WARN: MO_state received for unexpected mo_id [90-01-01 00:00:39.308] O_TGC_Main TGC.c:11249 TRACED:WARN: MO_state received for unexpected mo_id [90-01-01 00:00:46.552] P_PCM_GENERAL pcm_general.c:3730 TRACED:Port A B C D avail 1 0 0 0 error 1 1 1 1 Source_Ref 4 5 Freq_Ref 0 0 [90-01-01 00:00:46.672] P_MPSS_MMI_HNDL LED.c:963 TRACEH:MMI indication for LED_TransmissionOK port A state OFF [90-01-01 00:00:47.042] P_MPSS_MMI_HNDL LED.c:963 TRACEH:MMI indication for LED_TransmissionOK port A state ON [90-01-01 00:00:47.322] P_PCM_GENERAL pcm_general.c:3730 TRACED:Port A B C D avail 1 0 0 0 error 0 1 1 1 Source_Ref 0 0 Freq_Ref 0 0 [90-01-01 00:00:52.300] CREC_TMA_CM hwu_tma_cm.c:629 TRACED:Timeout, Signal IOM_DRV_GetEEPROMDumpRsp not received [90-01-01 00:00:52.300] CREC_TMA_CM hwu_common.c:943 TRACED:Number of configured sub RU:s = 0 [90-01-01 00:00:52.300] CREC_TMA_CM hwu_common.c:944 TRACED:Number of found sub RU:s = 0 [90-01-01 00:00:52.300] CREC_TMA_CM hwu_tma_cm.c:2042 TRACED:There is no defined_func for tma_cm index: 0 [90-01-01 00:00:52.300] CREC_TMA_CM hwu_tma_cm.c:2042 TRACED:There is no defined_func for tma_cm index: 1 [90-01-01 00:00:52.300] CREC_TMA_CM hwu_tma_cm.c:2042 TRACED:There is no defined_func for tma_cm index: 2 [90-01-01 00:00:52.300] CREC_TMA_CM hwu_tma_cm.c:2042 TRACED:There is no defined_func for tma_cm index: 3 [90-01-01 00:00:52.300] CREC_TMA_CM hwu_tma_cm.c:2042 TRACED:There is no defined_func for tma_cm index: 4 [90-01-01 00:00:52.300] CREC_TMA_CM hwu_tma_cm.c:2042 TRACED:There is no defined_func for tma_cm index: 5 [90-01-01 00:00:57.304] CREC_TMA_CM hwu_tma_cm.c:6107 TRACED:cancel of alna power timer was done [90-01-01 00:01:26.666] P_TRNSC_NBS NBS_links.c:1860 TRACED:Found link, ABIS-A TS=01 SB=0 BW=4 [90-01-01 00:01:26.968] O_CF_Main CF1.c:12072 TRACED:Establish_ind received [90-01-01 00:01:26.970] P_MPSS_MMI_HNDL LED.c:963 TRACEH:MMI indication for LED_Local state OFF [90-01-01 00:01:27.492] P_MPSS_MMI_HNDL LED.c:963 TRACEH:MMI indication for LED_Operational state FLASH [90-01-01 00:01:27.510] O_CF_Main CF1.c:18649 TRACED:AbisIWD:11B OML:G12R13 RSL:G01R15 [90-01-01 00:01:27.520] O_CF_Dnl_0 CF1.c:151160 TRACED:StartRes All expected TRX found [90-01-01 00:01:27.524] EC_Main /C//PowerCtrlImplBase.cpp:176 TRACED:Signal: 23024, PowerCtrl_SubscribeCapabilities received [90-01-01 00:01:27.608] P_MPSS_MMI_HNDL LED.c:963 TRACEH:MMI indication for LED_Operational state ON [90-01-01 00:01:27.712] O_CF_Main CF1.c:16376 TRACED:Connected MO:TF:0 [90-01-01 00:01:27.764] TSC_CO_Timing hw_driver_garp.c:1283 TRACED:NO! TRAFFIC ON SBUS [90-01-01 00:01:27.764] TSC_CO_Timing methods.c:1032 TRACEH:External State = RESET [90-01-01 00:01:27.814] TSC_CO_Timing hw_driver_garp.c:1283 TRACED:NO! TRAFFIC ON SBUS [90-01-01 00:01:27.814] TSC_CO_Timing methods.c:1032 TRACEH:External State = RESET [90-01-01 00:01:27.814] TSC_CO_Timing methods.c:940 TRACEH:External State = DISABLED [90-01-01 00:01:27.822] TSC_CO_Timing hw_driver_garp.c:1283 TRACED:NO! TRAFFIC ON SBUS [90-01-01 00:01:27.910] TSC_CO_Timing methods.c:167 TRACEH:coConfig syncSource = 0, coConfig syncMode = 1 [90-01-01 00:01:27.910] TSC_CO_Timing methods.c:169 TRACEH:coConfig compValue = 0, coConfig FS offset = FFFFFFFFFF [90-01-01 00:01:27.910] TSC_CO_Timing methods.c:174 TRACEH:coConfig, esbTs= 255, master_TgInst= 65535, master_TXChainDelay:=65535 [90-01-01 00:01:27.910] TSC_CO_Timing methods.c:411 TRACEH:The DXU has been configured to Standalone mode! [90-01-01 00:01:27.910] TSC_CO_Timing methods.c:1321 TRACED:ESB State was allready off [90-01-01 00:01:27.910] TSC_CO_Timing co_timing.c:416 TRACED:START_SYNCH already sent [90-01-01 00:01:28.334] TSC_Regulation regulation.c:1748 TRACED:Send subscrSynchStateRsp: synched 0, frame 0, exec 0, source 1, fsOundef 1 [90-01-01 00:01:28.334] TSC_CO_Timing methods.c:1321 TRACED:ESB State was allready off [90-01-01 00:01:31.984] P_MPSK_CLOCK timeout_clock_main.c:419 TRACED:Setting time: 20-11-03 11:46:07.000 [20-11-03 11:46:08.350] TSC_Regulation pcm_specific.c:767 TRACED:*slowStart_p:1 [20-11-03 11:46:52.532] O_RBS_Status RBS_STATUS_DEF.c:398 FAULT:20-11-03 11:46 FuncType: DX, Instance 0, Cease , EC2, SUPPRESS TERR LINK [20-11-03 11:51:01.928] TSC_CO_Timing methods.c:1140 TRACED:Sending ConfigResult [20-11-03 11:51:02.488] TSC_CO_Timing methods.c:883 TRACEH:External State = ENABLED [20-11-03 11:51:02.488] TSC_CO_Timing methods.c:1321 TRACED:ESB State was allready off [20-11-03 11:51:02.488] TSC_Regulation regulation.c:1784 TRACED:Setting cntrAdjAllowed = FALSE [20-11-03 11:51:02.488] TSC_Regulation regulation.c:2647 TRACED:syncState: NOT SYNCHRONIZED [20-11-03 11:51:02.488] TSC_Regulation regulation.c:2674 TRACED:syncStatus.freqSync: BAD [20-11-03 11:51:02.488] TSC_Regulation regulation.c:2699 TRACED:syncStatus.frameSync: BAD [20-11-03 11:51:02.488] TSC_Regulation regulation.c:2722 TRACED:Short Wander Hist PCM_REF1: ffffffff [20-11-03 11:51:02.488] TSC_Regulation regulation.c:2733 TRACED:Long Wander Hist PCM_REF1: ffffffff [20-11-03 11:51:02.488] TSC_Regulation regulation.c:2766 TRACED:Short Wander Hist PCM_REF2: ffffffff [20-11-03 11:51:02.488] TSC_Regulation regulation.c:2777 TRACED:Long Wander Hist PCM_REF2: ffffffff [20-11-03 11:51:02.488] TSC_Regulation regulation.c:2788 TRACED:PCM_REF2 usable: 0 [20-11-03 11:51:02.606] O_CF_Main CF1.c:16376 TRACED:Connected MO:CON:0 [20-11-03 11:51:03.260] O_RBS_Status RBS_STATUS_DEF.c:393 TRACEH:FAULT:20-11-03 11:51 MO: TF, Instance 0, Raise , EC1, PCM SYNCH NO USABLE PCM REFERENCE [20-11-03 11:51:03.264] O_RBS_Status RBS_STATUS_DEF.c:398 FAULT:20-11-03 11:51 FuncType: DX, Instance 0, Raise , EC1, PCM REF HOLD OVER TIMEOUT [20-11-03 11:51:12.706] O_CF_Main CF1.c:16376 TRACED:Connected MO:IS:0 [20-11-03 11:51:12.906] TRNS_IS_CON is_con.c:3471 TRACED:ICP = 536 belongs to NOT EXPECTED nor PREPARED TRX2. Next warning : 2 [20-11-03 11:51:12.906] TRNS_IS_CON is_con.c:3471 TRACED:ICP = 548 belongs to NOT EXPECTED nor PREPARED TRX3. Next warning : 2 [20-11-03 11:51:13.624] O_CF_Main P/IC/oms_abis_oml_body.ic:9881 TRACED:MCTR:0 optional_function_not_supported, DUGwithCPRI:FALSE [20-11-03 11:51:13.674] O_CF_Main P/IC/oms_abis_oml_body.ic:9881 TRACED:MCTR:0 optional_function_not_supported, DUGwithCPRI:FALSE [20-11-03 11:51:13.724] O_CF_Main P/IC/oms_abis_oml_body.ic:9881 TRACED:MCTR:0 optional_function_not_supported, DUGwithCPRI:FALSE [20-11-03 11:53:24.484] TRNS_PATSY_DRV patsy_drv.c:5288 TRACED: AlarmId:64 Uplink Traffic Overwrite TRU: 1 (0) [20-11-03 11:53:39.140] TRNS_PATSY_DRV patsy_drv.c:5288 TRACED: AlarmId:64 Uplink Traffic Overwrite TRU: 0 (0) [20-11-03 12:09:15.646] O_CF_Main CF1.c:12539 TRACED:Release_ind received [20-11-03 12:09:15.648] P_TRNSC_NBS NBS_links.c:3113 TRACED:>>> ARLL timer started [20-11-03 12:09:15.650] P_MPSS_MMI_HNDL LED.c:963 TRACEH:MMI indication for LED_Local state FLASH [20-11-03 12:09:16.568] O_RBS_Status RBS_STATUS_DEF.c:393 TRACEH:FAULT:20-11-03 12:09 MO: CF, Instance 0, Raise , EC2, LINK DISTURBED [20-11-03 12:09:16.572] O_RBS_Status RBS_STATUS_DEF.c:398 FAULT:20-11-03 12:09 FuncType: DX, Instance 0, Raise , EC2, CF LINK LOST [20-11-03 12:09:16.572] O_RBS_Status RBS_STATUS_DEF.c:398 FAULT:20-11-03 12:09 FuncType: DX, Instance 0, Raise , EC2, SUPPRESS TERR LINK [20-11-03 12:11:41.010] P_MPSS_LSM lsm_oper.c:1355 TRACED:All loadfiles OK [20-11-03 12:15:37.182] P_PCS_OMT lr_net.c:2754 TRACEH:OMT connected [20-11-03 12:15:37.358] P_PCS_DVT lr_net.c:2754 TRACEH:DVT connected [20-11-03 12:15:38.380] CREC_TG imited_vswr_supervision.c:198 TRACED:Unexpected signal, 10700, received [20-11-03 12:15:38.502] O_CF_Main CF1.c:21297 TRACED:The result from LocalMonitorManager_CreateW_SignalRsp is NOT OK [20-11-03 12:15:38.704] P_PCS_OMT lr_net.c:2793 TRACEH:OMT disconnected [20-11-03 12:15:38.704] P_TRNSC_NBS NBS_links.c:3128 TRACED:>>> ARLL timer ReStarted [20-11-03 12:15:38.804] P_PCS_DVT lr_net.c:2793 TRACEH:DVT disconnected [20-11-03 12:15:39.058] PLS_COM_L1 sio.c:835 TRACED:baud[1 -> 3] [20-11-03 12:15:39.058] PLS_COM_L1 sio.c:844 TRACED:UART initialized [20-11-03 12:15:41.410] P_PCS_OMT lr_net.c:2754 TRACEH:OMT connected [20-11-03 12:15:41.446] P_PCS_DVT lr_net.c:2754 TRACEH:DVT connected [20-11-03 12:15:47.590] O_OMT_Serv OMTH.c:15968 TRACEH:INFO: Size of IDB to read = 2241 [20-11-03 12:15:53.376] IOM_DRV iom_drv.c:1312 TRACED:Reading CXU OK 2007 bytes [20-11-03 12:15:53.558] IOM_DRV iom_drv.c:1312 TRACED:Reading CDU OK 1121 bytes [20-11-03 12:15:53.570] O_Extal Extal.c:6619 TRACED:Extal_GetAllAlarmPortCapabilities not supported [20-11-03 12:15:53.814] IOM_DRV iom_drv.c:1312 TRACED:Reading CXU OK 2007 bytes [20-11-03 12:15:53.996] IOM_DRV iom_drv.c:1312 TRACED:Reading CDU OK 1121 bytes [20-11-03 12:15:54.008] O_OMT_Serv OMTH.c:52840 TRACED:INFO: FindObjectHWU_Cabinet: Finding object OK [20-11-03 12:15:54.146] P_HWU_CABINET hwucabinet.c:350 TRACED:Extended cabinet capability not found [20-11-03 12:19:15.652] P_MPSS_MMI_HNDL LED.c:963 TRACEH:MMI indication for LED_Operational state OFF [20-11-03 12:36:48.712] IOM_DRV iom_drv.c:1312 TRACED:Reading CXU OK 2007 bytes [20-11-03 12:36:48.892] IOM_DRV iom_drv.c:1312 TRACED:Reading CDU OK 1121 bytes [20-11-03 12:36:48.904] O_Extal Extal.c:6619 TRACED:Extal_GetAllAlarmPortCapabilities not supported [20-11-03 12:36:49.144] IOM_DRV iom_drv.c:1312 TRACED:Reading CXU OK 2007 bytes [20-11-03 12:36:49.324] IOM_DRV iom_drv.c:1312 TRACED:Reading CDU OK 1121 bytes [20-11-03 12:36:49.352] O_OMT_Serv OMTH.c:52840 TRACED:INFO: FindObjectHWU_Cabinet: Finding object OK [20-11-03 12:36:49.494] P_HWU_CABINET hwucabinet.c:350 TRACED:Extended cabinet capability not found [20-11-03 12:37:41.142] P_MPSK_RPA rpa.c:221 TRACEH:Poolsize 11533456 used 3778528 free 7754928 [20-11-03 12:37:41.142] P_MPSK_RPA rpa.c:226 TRACEH: Size 79 allocated 3060 freelist 179 [20-11-03 12:37:41.142] P_MPSK_RPA rpa.c:226 TRACEH: Size 143 allocated 143 freelist 12 [20-11-03 12:37:41.142] P_MPSK_RPA rpa.c:226 TRACEH: Size 303 allocated 248 freelist 22 [20-11-03 12:37:41.142] P_MPSK_RPA rpa.c:226 TRACEH: Size 527 allocated 18 freelist 10 [20-11-03 12:37:41.142] P_MPSK_RPA rpa.c:226 TRACEH: Size 2063 allocated 65 freelist 9 [20-11-03 12:37:41.142] P_MPSK_RPA rpa.c:226 TRACEH: Size 8207 allocated 29 freelist 6 [20-11-03 12:37:41.142] P_MPSK_RPA rpa.c:226 TRACEH: Size 16399 allocated 17 freelist 2 [20-11-03 12:37:41.142] P_MPSK_RPA rpa.c:226 TRACEH: Size 32783 allocated 29 freelist 5 **** General log **** [90-01-01 00:00:00.010] NONAME debug_main.c:2909 TRACEH:OS-info: OSE Delta PowerPC krn-4xx/P2.3.2.0 [90-01-01 00:00:00.010] NONAME debug_main.c:2941 TRACEH:No restart info [90-01-01 00:00:00.010] NONAME debug_main.c:2956 TRACEH:Reset time: Not set [90-01-01 00:00:00.010] NONAME debug_main.c:3066 TRACEH:Load file=DXPR41GZ Program version=VEP-PPU CXC1121730_19.R1L01, System start cause=POWER_ON(0), Appl type=LFINFO_UPDATED_APPL(1) [90-01-01 00:00:00.028] P_MPSF_MICROSM microsm.c:1107 TRACEH:OK: entering COLDSTART phase [90-01-01 00:00:00.706] P_MPSS_LSM lsm_loader.c:4262 TRACEH:RBS Family: 0 [90-01-01 00:00:00.706] P_MPSS_LSM lsm_loader.c:4277 TRACEH:Board type (hex): 9 [90-01-01 00:00:01.070] P_MPSS_LSM lsm_file_info.c:1687 TRACEH:FilePckgName:CXP1040007_09R41G [90-01-01 00:00:10.030] P_MPSK_DBG_MAIN debug_main.c:1209 TRACEH:System load: 99.6% [90-01-01 00:00:19.522] P_MPSS_HWDB_HNDL HardwareDB.c:838 TRACEH:RBS Family: 0 [90-01-01 00:00:19.526] P_MPSS_HWU_MAIN hwuadm_main.c:395 TRACEH:RBS Family: 0 [90-01-01 00:00:19.528] P_MPSS_HWU_MAIN hwuadm_main.c:321 TRACEH:RU Type = 6 [90-01-01 00:00:19.534] P_MPSS_LSM lsm_loader.c:3081 TRACEH:InternalState = _hwu [90-01-01 00:00:20.546] P_MPSS_MMI_HNDL LED.c:963 TRACEH:MMI indication for LED_Local state FLASH [90-01-01 00:00:22.222] P_MPSS_LSM lsm_loader.c:3500 TRACEH:OperationalReport from TRNSC [90-01-01 00:00:22.722] P_MPSS_LSM lsm_loader.c:3865 TRACEH:Waiting for internal report [90-01-01 00:00:22.722] P_MPSS_LSM lsm_loader.c:3081 TRACEH:InternalState = _inst [90-01-01 00:00:25.192] O_IDB_Main ../TMP/C/IDB_Storage.c:1053 TRACEH:CONFIG - IDB structure rev 50:0 (Init cont rev R60D) [90-01-01 00:00:25.192] O_IDB_Main ../TMP/C/IDB_Storage.c:1073 TRACEH:CONFIG - Config Name 2206 SCC 1X2 [90-01-01 00:00:25.192] O_IDB_Main ../TMP/C/IDB_Storage.c:1084 TRACEH:CONFIG - Cabinet 0 [90-01-01 00:00:25.192] O_IDB_Main ../TMP/C/IDB_Storage.c:1106 TRACEH:CONFIG - Type:9 Variant:0 Climate system: 6 Power system: 15 [90-01-01 00:00:25.192] O_IDB_Main ../TMP/C/IDB_Storage.c:1117 TRACEH:CONFIG - Basic Configuration Sectors A: 5616, B: 0, C: 0 [90-01-01 00:00:25.670] P_MPSS_LSM lsm_loader.c:3500 TRACEH:OperationalReport from EC [90-01-01 00:00:25.672] P_MPSS_LSM lsm_loader.c:3500 TRACEH:OperationalReport from LOMP [90-01-01 00:00:25.672] P_MPSS_LSM lsm_loader.c:3500 TRACEH:OperationalReport from IDBP [90-01-01 00:00:25.672] P_MPSS_LSM lsm_loader.c:3500 TRACEH:OperationalReport from MPSM [90-01-01 00:00:25.674] P_MPSS_LSM lsm_loader.c:3500 TRACEH:OperationalReport from MPSR [90-01-01 00:00:25.676] P_MPSS_LSM lsm_loader.c:3055 TRACEH:TraceH_Checkpoint: NodeStartState = SWConsistency [90-01-01 00:00:25.676] P_MPSS_LSM lsm_loader.c:3081 TRACEH:InternalState = _test [90-01-01 00:00:26.828] P_MPSS_LSM lsm_loader.c:3500 TRACEH:OperationalReport from CREC [90-01-01 00:00:26.864] TSC_Regulation nvram_lib.c:343 TRACEH:RAM attach OK: 0 10006000 1000 [90-01-01 00:00:30.030] P_MPSK_DBG_MAIN debug_main.c:1216 TRACEH:System load: 61.7% [90-01-01 00:00:32.222] O_LocalIDB LOMP1.c:18179 TRACEH:Checkpoint: NodeStartState = IDB_Consistency. [90-01-01 00:00:32.334] P_MPSS_LSM lsm_loader.c:3500 TRACEH:OperationalReport from TSC [90-01-01 00:00:32.334] P_MPSS_LSM lsm_loader.c:3059 TRACEH:TraceH_Checkpoint: NodeStartState = PlatformOperational [90-01-01 00:00:34.102] P_MPSS_MMI_HNDL LED.c:963 TRACEH:MMI indication for LED_TransmissionOK port A state ON [90-01-01 00:00:34.120] P_MPSS_LSM lsm_loader.c:3500 TRACEH:OperationalReport from RBS [90-01-01 00:00:34.120] P_MPSS_LSM lsm_loader.c:3063 TRACEH:TraceH_Checkpoint: NodeStartState = SystemOperational [90-01-01 00:00:37.688] P_MPSS_LSM lsm_loader.c:3117 TRACEH:TraceH_Checkpoint: NodeStartState = ReadyForRemoteMode [90-01-01 00:00:37.688] P_MPSS_LSM lsm_loader.c:3500 TRACEH:OperationalReport from CF [90-01-01 00:00:37.688] P_MPSS_HWDB_HNDL HardwareDB.c:2148 TRACEH:Fast restart allowed [90-01-01 00:00:46.672] P_MPSS_MMI_HNDL LED.c:963 TRACEH:MMI indication for LED_TransmissionOK port A state OFF [90-01-01 00:00:47.042] P_MPSS_MMI_HNDL LED.c:963 TRACEH:MMI indication for LED_TransmissionOK port A state ON [90-01-01 00:01:26.970] P_MPSS_MMI_HNDL LED.c:963 TRACEH:MMI indication for LED_Local state OFF [90-01-01 00:01:27.492] P_MPSS_MMI_HNDL LED.c:963 TRACEH:MMI indication for LED_Operational state FLASH [90-01-01 00:01:27.608] P_MPSS_MMI_HNDL LED.c:963 TRACEH:MMI indication for LED_Operational state ON [90-01-01 00:01:27.764] TSC_CO_Timing methods.c:1032 TRACEH:External State = RESET [90-01-01 00:01:27.814] TSC_CO_Timing methods.c:1032 TRACEH:External State = RESET [90-01-01 00:01:27.814] TSC_CO_Timing methods.c:940 TRACEH:External State = DISABLED [90-01-01 00:01:27.910] TSC_CO_Timing methods.c:167 TRACEH:coConfig syncSource = 0, coConfig syncMode = 1 [90-01-01 00:01:27.910] TSC_CO_Timing methods.c:169 TRACEH:coConfig compValue = 0, coConfig FS offset = FFFFFFFFFF [90-01-01 00:01:27.910] TSC_CO_Timing methods.c:174 TRACEH:coConfig, esbTs= 255, master_TgInst= 65535, master_TXChainDelay:=65535 [90-01-01 00:01:27.910] TSC_CO_Timing methods.c:411 TRACEH:The DXU has been configured to Standalone mode! [20-11-03 11:51:02.488] TSC_CO_Timing methods.c:883 TRACEH:External State = ENABLED [20-11-03 11:51:03.260] O_RBS_Status RBS_STATUS_DEF.c:393 TRACEH:FAULT:20-11-03 11:51 MO: TF, Instance 0, Raise , EC1, PCM SYNCH NO USABLE PCM REFERENCE [20-11-03 12:09:15.650] P_MPSS_MMI_HNDL LED.c:963 TRACEH:MMI indication for LED_Local state FLASH [20-11-03 12:09:16.568] O_RBS_Status RBS_STATUS_DEF.c:393 TRACEH:FAULT:20-11-03 12:09 MO: CF, Instance 0, Raise , EC2, LINK DISTURBED [20-11-03 12:15:37.182] P_PCS_OMT lr_net.c:2754 TRACEH:OMT connected [20-11-03 12:15:37.358] P_PCS_DVT lr_net.c:2754 TRACEH:DVT connected [20-11-03 12:15:38.704] P_PCS_OMT lr_net.c:2793 TRACEH:OMT disconnected [20-11-03 12:15:38.804] P_PCS_DVT lr_net.c:2793 TRACEH:DVT disconnected [20-11-03 12:15:41.410] P_PCS_OMT lr_net.c:2754 TRACEH:OMT connected [20-11-03 12:15:41.446] P_PCS_DVT lr_net.c:2754 TRACEH:DVT connected [20-11-03 12:15:47.590] O_OMT_Serv OMTH.c:15968 TRACEH:INFO: Size of IDB to read = 2241 [20-11-03 12:19:15.652] P_MPSS_MMI_HNDL LED.c:963 TRACEH:MMI indication for LED_Operational state OFF [20-11-03 12:37:41.142] P_MPSK_RPA rpa.c:221 TRACEH:Poolsize 11533456 used 3778528 free 7754928 [20-11-03 12:37:41.142] P_MPSK_RPA rpa.c:226 TRACEH: Size 79 allocated 3060 freelist 179 [20-11-03 12:37:41.142] P_MPSK_RPA rpa.c:226 TRACEH: Size 143 allocated 143 freelist 12 [20-11-03 12:37:41.142] P_MPSK_RPA rpa.c:226 TRACEH: Size 303 allocated 248 freelist 22 [20-11-03 12:37:41.142] P_MPSK_RPA rpa.c:226 TRACEH: Size 527 allocated 18 freelist 10 [20-11-03 12:37:41.142] P_MPSK_RPA rpa.c:226 TRACEH: Size 2063 allocated 65 freelist 9 [20-11-03 12:37:41.142] P_MPSK_RPA rpa.c:226 TRACEH: Size 8207 allocated 29 freelist 6 [20-11-03 12:37:41.142] P_MPSK_RPA rpa.c:226 TRACEH: Size 16399 allocated 17 freelist 2 [20-11-03 12:37:41.142] P_MPSK_RPA rpa.c:226 TRACEH: Size 32783 allocated 29 freelist 5 dTRU 0 log ********** **** Detailed log **** [90-01-01 00:00:00.010] NONAME debug_handlers.c:810 TRACED:No sys_env_board_type [90-01-01 00:00:00.010] NONAME debug_main.c:2909 TRACEH:OS-info: OSE Delta PowerPC krn-4xx/P2.3.2.0 [90-01-01 00:00:00.010] NONAME debug_main.c:2941 TRACEH:No restart info [90-01-01 00:00:00.010] NONAME debug_main.c:2956 TRACEH:Reset time: Not set [90-01-01 00:00:00.010] NONAME debug_main.c:3066 TRACEH:Load file=TRPR41GZ Program version=VEP-PPU CXC1121730_19.R1L01, System start cause=POWER_ON(0), Appl type=LFINFO_UPDATED_APPL(1) [90-01-01 00:00:00.014] NONAME fs_util_dex.c:1384 TRACED:Loadfile pointers 0x500000, 0x100000 [90-01-01 00:00:00.020] P_MPSF_MICROSM microsm.c:1107 TRACEH:OK: entering COLDSTART phase [90-01-01 00:00:00.020] P_MPSF_MICROSM microsm.c:404 TRACED:OK: RAM configured, start = 0x0, size = 0x1d00000, TLB usage = 27 (/64). [90-01-01 00:00:00.020] P_MPSF_MICROSM microsm.c:407 TRACED:OK: POOL configured, start = 0x400000, size = 0xb00000. [90-01-01 00:00:00.042] P_MPSF_MICROSM microsm.c:763 TRACED:OK: Loaded MPSC_SHLIB, PAD: f04000 [90-01-01 00:00:00.128] P_MPSF_MICROSM microsm.c:763 TRACED:OK: Loaded MPSO, PAD: f14000 [90-01-01 00:00:00.132] P_MPSS_LSM lsm_loader.c:4262 TRACEH:RBS Family: 0 [90-01-01 00:00:00.134] P_MPSS_LSM lsm_loader.c:4277 TRACEH:Board type (hex): a [90-01-01 00:00:00.134] P_MPSS_LSM lsm_file_info.c:2321 TRACED:init p_write 0x100000 [90-01-01 00:00:00.134] P_MPSS_LSM lsm_file_info.c:2323 TRACED:init w.t. 0 [90-01-01 00:00:00.138] P_MPSF_MICROSM microsm.c:861 TRACED:OK: Started program: MPSO, PAD: f14000, IAD: f52000 [90-01-01 00:00:00.138] P_MPSS_LSM lsm_loader.c:4051 TRACED:zf_start = 0x10001000 [90-01-01 00:00:00.138] P_MPSS_LSM lsm_loader.c:4061 TRACED:Area NOT OK [90-01-01 00:00:00.138] P_MPSS_LSM lsm_loader.c:4062 TRACED:Initializing.... [90-01-01 00:00:00.140] P_MPSS_LSM lsm_loader.c:4070 TRACED:DONE [90-01-01 00:00:00.140] P_MPSS_LSM lsm_loader.c:4073 TRACED:ZF in NVRam Rev=-------- Size=0x0 (0) [90-01-01 00:00:00.140] P_MPSS_LSM lsm_file_info.c:1049 TRACED:LFIF LI=CXC1121974_7,R1 [90-01-01 00:00:00.140] P_MPSS_LSM lsm_file_info.c:1073 TRACED:Known LFIF CXC1121974_7, R1 [90-01-01 00:00:00.140] P_MPSS_LSM lsm_file_info.c:1049 TRACED:LFIF OLI=CXC1121965_1,R5 [90-01-01 00:00:00.140] P_MPSS_LSM lsm_file_info.c:1045 TRACED:LFIF LFIF_INFO=CXC1121974_7,R1,Date20070529 [90-01-01 00:00:00.184] P_MPSS_LSM lsm_loader.c:4648 TRACED:LFIF len=200000 npgm=8 res=0 [90-01-01 00:00:00.196] P_MPSS_LSM lsm_file_info.c:1591 TRACED:FEFC enabled at startup [90-01-01 00:00:00.196] P_MPSS_LSM lsm_file_info.c:1687 TRACEH:FilePckgName:CXP1040007_09R41G [90-01-01 00:00:00.208] P_MPSS_LSM lsm_loader.c:2546 TRACED:Selected FLBI_G_T from application SW loadfile. [90-01-01 00:00:00.236] P_MPSF_MICROSM microsm.c:763 TRACED:OK: Loaded FLASH_SHLIB, PAD: f65000 [90-01-01 00:00:00.240] P_MPSS_LSM lsm_loader.c:2546 TRACED:Selected BIOS_GXT from application SW loadfile. [90-01-01 00:00:00.286] P_MPSF_MICROSM microsm.c:763 TRACED:OK: Loaded BIOS_SHLIB, PAD: f71000 [90-01-01 00:00:00.390] P_MPSF_MICROSM microsm.c:763 TRACED:OK: Loaded MPSS, PAD: f87000 [90-01-01 00:00:00.398] P_MPSF_MICROSM microsm.c:861 TRACED:OK: Started program: MPSS, PAD: f87000, IAD: fe3000 [90-01-01 00:00:00.400] P_MPSS_HWDB_HNDL HardwareDB.c:802 TRACED:MPSS-PPU CXC1121731_21.R1G01 running [90-01-01 00:00:00.400] P_MPSS_HWDB_HNDL HardwareDB.c:838 TRACEH:RBS Family: 0 [90-01-01 00:00:00.402] P_MPSS_HWU_MAIN hwuadm_main.c:395 TRACEH:RBS Family: 0 [90-01-01 00:00:00.406] P_MPSS_HWU_MAIN hwuadm_main.c:321 TRACEH:RU Type = 7 [90-01-01 00:00:00.406] P_MPSS_HWDB_HNDL HardwareDB.c:738 TRACED:Parameter PD0011 not found [90-01-01 00:00:00.406] P_MPSS_HWDB_HNDL HardwareDB.c:738 TRACED:Parameter PD0010 not found [90-01-01 00:00:00.406] P_MPSS_HWDB_HNDL HardwareDB.c:738 TRACED:Parameter PT0008 not found [90-01-01 00:00:00.406] P_MPSS_HWDB_HNDL HardwareDB.c:738 TRACED:Parameter PD4002 not found [90-01-01 00:00:00.406] P_MPSS_HWDB_HNDL HardwareDB.c:1272 TRACED:Parameter PD4002 not found [90-01-01 00:00:00.410] P_MPSS_LSM lsm_loader.c:3081 TRACEH:InternalState = _hwu [90-01-01 00:00:00.418] P_NPSENSORS npsensors.c:623 TRACEH:Process not needed anymore, will be stopped [90-01-01 00:00:00.418] P_MPSS_NVRM_HNDL NV_Ram.c:467 TRACED:max entry 32767, start 10001000 [90-01-01 00:00:00.418] P_MPSS_NVRM_HNDL NV_Ram.c:636 TRACED:Initializing NVRAM... [90-01-01 00:00:00.556] P_TRNSD_CPA trnscpa.c:483 TRACED:TRND-PPU CXC1121735_19.R10A01 running [90-01-01 00:00:00.570] P_MPSS_LSM lsm_loader.c:2914 TRACED:Started TRNSD, errCode 0, iad 1036000 [90-01-01 00:00:00.580] P_MPSS_LSM lsm_file_info.c:1643 TRACED:Using OLI main DEST=DTR [90-01-01 00:00:00.582] P_MPSS_LSM lsm_loader.c:2084 TRACED:Prefer $$$$_P_T [90-01-01 00:00:00.582] P_MPSS_LSM lsm_loader.c:2084 TRACED:Prefer $$$$_tb [90-01-01 00:00:00.582] P_MPSS_LSM lsm_loader.c:2084 TRACED:Prefer $$trxp [90-01-01 00:00:00.582] P_MPSS_LSM lsm_file_info.c:1635 TRACED:Using LI main DEST=DTR [90-01-01 00:00:00.582] P_MPSS_LSM lsm_loader.c:2084 TRACED:Prefer $IOS_GXT [90-01-01 00:00:00.582] P_MPSS_LSM lsm_loader.c:2084 TRACED:Prefer $LBI_G_T [90-01-01 00:00:00.582] P_MPSS_LSM lsm_loader.c:2084 TRACED:Prefer $$$$_tx [90-01-01 00:00:00.582] P_MPSS_LSM lsm_loader.c:2084 TRACED:Prefer $$trxp [90-01-01 00:00:00.596] P_MPSS_LSM lsm_loader.c:3500 TRACEH:OperationalReport from TRNSD [90-01-01 00:00:00.618] TAROT_DRV_MAIN_A tarot_drv_main.c:1549 TRACEH:HWU_Tarot: HW Configured for MASTER only [90-01-01 00:00:00.618] TAROT_DRV_MAIN_A tarot_drv_main.c:1805 TRACEH:HWU_Tarot: Loading file: DSPX0_FW Revision: _17.R5B01 Size: 459 Kbyte [90-01-01 00:00:01.134] TAROT_DRV_MAIN_A tarot_drv_main.c:1647 TRACEH:HWU_Tarot: MASTER TAROT Load and Activation OK (DSPmode DSPG0_FW, CPRIind 0) [90-01-01 00:00:01.154] TAROT_DRV_MAIN_B tarot_drv_main.c:1549 TRACEH:HWU_Tarot: HW Configured for MASTER only [90-01-01 00:00:01.154] TAROT_DRV_MAIN_B tarot_drv_main.c:1805 TRACEH:HWU_Tarot: Loading file: DSPX0_FW Revision: _17.R5B01 Size: 459 Kbyte [90-01-01 00:00:01.668] P_MPSS_MMI_HNDL LED.c:963 TRACEH:MMI indication for LED_Local state FLASH [90-01-01 00:00:01.668] TAROT_DRV_MAIN_B tarot_drv_main.c:1647 TRACEH:HWU_Tarot: MASTER TAROT Load and Activation OK (DSPmode DSPG0_FW, CPRIind 0) [90-01-01 00:00:34.572] P_TRNSD_BM bus_mgr_hw.c:910 TRACEH:Y2 BOOT is ready for TRX1 [90-01-01 00:00:34.636] P_TRNSD_BM bus_mgr_hw.c:910 TRACEH:Y2 BOOT is ready for TRX0 [90-01-01 00:00:34.638] P_TRNSD_ISLHND islhnd.c:1114 TRACED:New channel status. Using 2 channels. 258 is active [90-01-01 00:00:34.638] P_TRNSD_ISLHND islhnd.c:1121 TRACED:channels[0] ch_no=258, isl_state=defined [90-01-01 00:00:34.638] P_TRNSD_ISLHND islhnd.c:1121 TRACED:channels[1] ch_no=259, isl_state=defined [90-01-01 00:00:34.640] P_TRNSD_ISLHND islhnd.c:693 TRACED:Sending initial ISL_CMD_WAKEUP, ch 258 [90-01-01 00:00:34.640] P_TRNSD_ISLHND islhnd.c:693 TRACED:Sending initial ISL_CMD_WAKEUP, ch 259 [90-01-01 00:00:34.640] P_MPSS_LSM lsm_loader.c:3776 TRACED:SetInstList, inst 1, n_func 2 [90-01-01 00:00:34.640] P_TRNSD_ISLHND islhnd.c:803 TRACED:Active channel 258 [90-01-01 00:00:34.646] P_MPSS_HWU_MAIN hwuadm_main.c:1475 TRACED:FuncType[0] = 1 FuncInst[0] = 0 [90-01-01 00:00:34.646] P_MPSS_HWU_MAIN hwuadm_main.c:1475 TRACED:FuncType[1] = 1 FuncInst[1] = 1 [90-01-01 00:00:35.144] P_MPSS_LSM lsm_loader.c:3865 TRACEH:Waiting for internal report [90-01-01 00:00:35.144] P_MPSS_LSM lsm_loader.c:3081 TRACEH:InternalState = _inst [90-01-01 00:00:35.360] O_LOMP_Main LOMP1.c:892 TRACED:Info: (LOMP_SW6 CXC1125822_19.R1AC01) [90-01-01 00:00:35.366] P_MPSS_LSM lsm_loader.c:2914 TRACED:Started LOMP, errCode 0, iad 10c1000 [90-01-01 00:00:35.366] P_MPSS_LSM lsm_loader.c:3500 TRACEH:OperationalReport from LOMP [90-01-01 00:00:39.254] P_MPSS_LSM lsm_loader.c:3543 TRACED:SAP enable [90-01-01 00:00:39.254] P_MPSS_LSM lsm_loader.c:3055 TRACEH:TraceH_Checkpoint: NodeStartState = SWConsistency [90-01-01 00:00:39.256] P_MPSS_LSM lsm_loader.c:3081 TRACEH:InternalState = _test [90-01-01 00:00:39.256] PLS_SAP_MAIN sap_main.c:2134 TRACEH:SAP ENABLED [90-01-01 00:00:39.264] LOCAL_ODB local_odb.c:2440 TRACED:OK: Connected to Central ODB [90-01-01 00:00:39.310] RC_MAIN rc_main.c:847 TRACED:RC_SW CXC1121726_18 R5D01, PPC [90-01-01 00:00:39.312] P_MPSS_LSM lsm_loader.c:2914 TRACED:Started RC, errCode 0, iad 10e5000 [90-01-01 00:00:39.424] LREC_MAIN lrec_main.c:1355 TRACED:LREC_SW CXC1121727_18 R5A01 Started [90-01-01 00:00:39.428] P_MPSS_LSM lsm_loader.c:2914 TRACED:Started LREC, errCode 0, iad 112d000 [90-01-01 00:00:39.450] P_MPSS_LSM lsm_loader.c:2914 TRACED:Started TFS, errCode 0, iad 1157000 [90-01-01 00:00:40.010] P_MPSS_LSM lsm_loader.c:2884 TRACED:Env instance_no = 0 [90-01-01 00:00:40.010] P_MPSS_LSM lsm_loader.c:2884 TRACED:Env TRX_INST = 0 [90-01-01 00:00:40.142] 0\HCOMBS hcombs.c:2267 TRACED:StartProc=HCOMBS [90-01-01 00:00:40.142] 0\HCOMBS hcombs.c:2570 TRACED:ResetScaleFilter 0 [90-01-01 00:00:40.142] 0\HCOMBS hcombs.c:2570 TRACED:ResetScaleFilter 1 [90-01-01 00:00:40.158] 0\HCOMBS hcombs.c:755 TRACED:Trace monitors: trace hcombs 0x0060C41F [90-01-01 00:00:40.160] P_MPSS_LSM lsm_loader.c:2914 TRACED:Started RC_TRX, errCode 0, iad 1298000 [90-01-01 00:00:40.160] P_MPSS_LSM lsm_loader.c:2884 TRACED:Env instance_no = 1 [90-01-01 00:00:40.160] P_MPSS_LSM lsm_loader.c:2884 TRACED:Env TRX_INST = 1 [90-01-01 00:00:40.292] 1\HCOMBS hcombs.c:2267 TRACED:StartProc=HCOMBS [90-01-01 00:00:40.292] 1\HCOMBS hcombs.c:2570 TRACED:ResetScaleFilter 0 [90-01-01 00:00:40.294] 1\HCOMBS hcombs.c:2570 TRACED:ResetScaleFilter 1 [90-01-01 00:00:40.294] 1\HCOMBS hcombs.c:2276 TRACED:Proc. inactive [90-01-01 00:00:40.294] P_MPSS_LSM lsm_loader.c:2914 TRACED:Started RC_TRX, errCode 0, iad 135e000 [90-01-01 00:00:40.502] 1\RC_HWU_RC hwu_rc.c:604 TRACED:TRX_DRV_EquipmentId received 1 times [90-01-01 00:00:40.502] 1\RC_HWU_RC rcsys_startup.c:1888 TRACED:Sending address assignment [90-01-01 00:00:40.502] 1\RC_HWU_RC rcsys_startup.c:1905 TRACED:Load Dirac Loader (rcl00001) [90-01-01 00:00:40.530] 0\RC_HWU_RC hwu_rc.c:604 TRACED:TRX_DRV_EquipmentId received 1 times [90-01-01 00:00:40.530] 0\RC_HWU_RC rcsys_startup.c:1888 TRACED:Sending address assignment [90-01-01 00:00:40.530] 0\RC_HWU_RC rcsys_startup.c:1905 TRACED:Load Dirac Loader (rcl00001) [90-01-01 00:00:40.822] P_MPSS_LSM lsm_loader.c:2884 TRACED:Env instance_no = 0 [90-01-01 00:00:40.822] P_MPSS_LSM lsm_loader.c:2884 TRACED:Env TRX = 0 [90-01-01 00:00:40.838] 0\T_TSAM_TAS t_tsam_tas.cc:428 TRACEH:TFS SW revision: CXP 102 52/14 R7A01 [90-01-01 00:00:40.840] P_MPSS_LSM lsm_loader.c:2914 TRACED:Started TFSSW22P, errCode 0, iad 14f1000 [90-01-01 00:00:40.840] P_MPSS_LSM lsm_loader.c:2546 TRACED:Selected rcl1_tx from application SW loadfile. [90-01-01 00:00:40.840] P_MPSS_LSM lsm_loader.c:2546 TRACED:Selected rcl1_tx from application SW loadfile. [90-01-01 00:00:40.840] P_MPSS_LSM lsm_loader.c:2884 TRACED:Env instance_no = 1 [90-01-01 00:00:40.840] P_MPSS_LSM lsm_loader.c:2884 TRACED:Env TRX = 1 [90-01-01 00:00:40.842] 1\RC_HWU_RC rcsys_startup.c:1928 TRACED:Sending application start [90-01-01 00:00:40.844] 1\RC_HWU_RC rcsys_startup.c:1980 TRACED:Dirac Loader started (rcl00001) [90-01-01 00:00:40.844] 1\RC_HWU_RC rcsys_startup.c:1983 TRACED:Load Dirac Application (rcf00001) [90-01-01 00:00:40.844] 0\RC_HWU_RC rcsys_startup.c:1928 TRACED:Sending application start [90-01-01 00:00:40.844] 0\RC_HWU_RC rcsys_startup.c:1980 TRACED:Dirac Loader started (rcl00001) [90-01-01 00:00:40.844] 0\RC_HWU_RC rcsys_startup.c:1983 TRACED:Load Dirac Application (rcf00001) [90-01-01 00:00:40.876] 1\T_TSAM_TAS t_tsam_tas.cc:428 TRACEH:TFS SW revision: CXP 102 52/14 R7A01 [90-01-01 00:00:40.878] P_MPSS_LSM lsm_loader.c:2914 TRACED:Started TFSSW22P, errCode 0, iad 1521000 [90-01-01 00:00:40.878] P_MPSS_LSM lsm_loader.c:2546 TRACED:Selected rcf1_tx from application SW loadfile. [90-01-01 00:00:40.878] P_MPSS_LSM lsm_loader.c:2546 TRACED:Selected rcf1_tx from application SW loadfile. [90-01-01 00:00:41.670] 0\RC_HWU_RC rcsys_startup.c:1928 TRACED:Sending application start [90-01-01 00:00:41.754] 1\RC_HWU_RC rcsys_startup.c:1928 TRACED:Sending application start [90-01-01 00:00:41.830] 0\RC_HWU_RC rcsys_startup.c:1989 TRACED:Dirac Application started (rcf00001) [90-01-01 00:00:41.864] 0\RC_HWU_RC hwu_rc.c:364 TRACED:Dirac FW: CXC_112_3024/11 R3C01 [90-01-01 00:00:41.914] 1\RC_HWU_RC rcsys_startup.c:1989 TRACED:Dirac Application started (rcf00001) [90-01-01 00:00:41.916] 1\RC_HWU_RC hwu_rc.c:364 TRACED:Dirac FW: CXC_112_3024/11 R3C01 [90-01-01 00:00:41.918] 0\C_DiracComb C_DiracCombine.c:267 TRACED:Datablock id/length(words): 5/4156 [90-01-01 00:00:41.970] 1\C_DiracComb C_DiracCombine.c:267 TRACED:Datablock id/length(words): 5/3133 [90-01-01 00:00:42.084] 0\C_DiracComb C_DiracCombine.c:267 TRACED:Datablock id/length(words): 3/3120 [90-01-01 00:00:42.108] 1\C_DiracComb C_DiracCombine.c:267 TRACED:Datablock id/length(words): 3/3120 [90-01-01 00:00:42.218] 0\C_DiracComb C_DiracCombine.c:267 TRACED:Datablock id/length(words): 2/6150 [90-01-01 00:00:42.242] 1\C_DiracComb C_DiracCombine.c:267 TRACED:Datablock id/length(words): 2/6150 [90-01-01 00:00:42.432] 0\C_DiracComb C_DiracCombine.c:267 TRACED:Datablock id/length(words): 7/820 [90-01-01 00:00:42.504] 0\C_DiracComb C_DiracCombine.c:267 TRACED:Datablock id/length(words): 8/187 [90-01-01 00:00:44.644] O_LocalIDB /IC/LocalIDB_CDU_Cache.ic:926 TRACED:Max PPC IDB area size=131072 bytes [90-01-01 00:00:44.644] O_LocalIDB /IC/LocalIDB_CDU_Cache.ic:927 TRACED:Current IDB used size=37015 bytes [90-01-01 00:00:44.644] O_LocalIDB /IC/LocalIDB_CDU_Cache.ic:928 TRACED:Left IDB size=64617 bytes [90-01-01 00:00:44.648] O_LocalIDB LOMP1.c:18179 TRACEH:Checkpoint: NodeStartState = IDB_Consistency. [90-01-01 00:00:44.654] P_TRNSD_DLMAN dlman.c:1926 TRACED:Create pending link: OML [90-01-01 00:00:44.654] P_TRNSD_DLMAN dlman.c:1926 TRACED:Create pending link: OML [90-01-01 00:00:44.654] P_TRNSD_DLMAN dlman.c:1926 TRACED:Create pending link: RSL [90-01-01 00:00:44.654] P_TRNSD_DLMAN dlman.c:1926 TRACED:Create pending link: RSL [90-01-01 00:00:44.662] LREC_MAIN lrec_main.c:1390 TRACEH:Nr of sub RUs connected to this TRX = 1 [90-01-01 00:00:44.662] LREC_MAIN lrec_main.c:1396 TRACEH:FuncType = 4, FuncInst = 0 [90-01-01 00:00:44.816] P_MPSS_LSM lsm_loader.c:2884 TRACED:Env instance_no = 0 [90-01-01 00:00:44.818] P_MPSS_LSM lsm_loader.c:2884 TRACED:Env TRX_INST = 0 [90-01-01 00:00:44.828] P_MPSS_LSM lsm_loader.c:2914 TRACED:Started LREC_CDTX, errCode 0, iad 159d000 [90-01-01 00:00:44.828] P_MPSS_LSM lsm_loader.c:2884 TRACED:Env instance_no = 1 [90-01-01 00:00:44.828] P_MPSS_LSM lsm_loader.c:2884 TRACED:Env TRX_INST = 1 [90-01-01 00:00:44.838] P_MPSS_LSM lsm_loader.c:2914 TRACED:Started LREC_CDTX, errCode 0, iad 15bf000 [90-01-01 00:00:44.844] 0\LREC_CD_TX lrec_cd_tx.c:2770 TRACED:INFO: Waiting for HWU_CD_TX_GetSynchAttributes [90-01-01 00:00:44.844] 0\LREC_CD_TX lrec_cd_tx.c:1723 TRACED:INFO: Wait for First HWU_CD_TX_SetSynchMode [90-01-01 00:00:44.846] 1\LREC_CD_TX lrec_cd_tx.c:2770 TRACED:INFO: Waiting for HWU_CD_TX_GetSynchAttributes [90-01-01 00:00:44.846] 1\LREC_CD_TX lrec_cd_tx.c:1723 TRACED:INFO: Wait for First HWU_CD_TX_SetSynchMode [90-01-01 00:00:46.062] 0\RC_HWU_RX hwu_rx.c:990 TRACED:-----> LocalIDB_RBS_ExtendedRF_CableSupervision element Found in IDB and Flag = 0 [90-01-01 00:00:46.064] 1\RC_HWU_RX hwu_rx.c:990 TRACED:-----> LocalIDB_RBS_ExtendedRF_CableSupervision element Found in IDB and Flag = 0 [90-01-01 00:00:46.638] 0\RC_HWU_RC funcdb.c:254 TRACED:RT12--: Head: No=34,Len=6226,Calc: NoTrans=23,NoOther=11,Len=6226,Last=1599 [90-01-01 00:00:46.638] 0\RC_HWU_RC funcdb.c:254 TRACED:RT11--: Head: No=29,Len=12286,Calc: NoTrans=27,NoOther=2,Len=12286,Last=1499 [90-01-01 00:00:46.638] 0\RC_HWU_RC funcdb.c:254 TRACED:RT13--: Head: No=28,Len=8298,Calc: NoTrans=22,NoOther=6,Len=8298,Last=1699 [90-01-01 00:00:46.642] 1\RC_HWU_RC funcdb.c:254 TRACED:RT12--: Head: No=34,Len=6226,Calc: NoTrans=23,NoOther=11,Len=6226,Last=1599 [90-01-01 00:00:46.642] 1\RC_HWU_RC funcdb.c:254 TRACED:RT11--: Head: No=29,Len=12286,Calc: NoTrans=27,NoOther=2,Len=12286,Last=1499 [90-01-01 00:00:46.642] 1\RC_HWU_RC funcdb.c:254 TRACED:RT13--: Head: No=28,Len=6252,Calc: NoTrans=22,NoOther=6,Len=6252,Last=1699 [90-01-01 00:00:46.656] P_MPSS_LSM lsm_loader.c:3500 TRACEH:OperationalReport from LREC [90-01-01 00:00:46.668] LREC_RXD lrec_db_server.c:1289 TRACED:Using RU_Type8_0 = 7 from RXD/HCOMB DB [90-01-01 00:00:46.874] P_MPSS_LSM lsm_loader.c:3500 TRACEH:OperationalReport from TFS [90-01-01 00:00:48.114] P_MPSS_MMI_HNDL LED.c:958 TRACED:MMI indication for LED_RF_Off state ON [90-01-01 00:00:48.466] 0\RC_HWU_TX tx_db_server.c:716 TRACED:INFO: Failed reading RT1130 TSPS, set to TSPS Not Supported [90-01-01 00:00:48.466] 0\C_DiracOoM C_Lib.c:235 TRACED:CPU->Dirac - Length=2 (20:5) [90-01-01 00:00:48.468] 0\C_DiracOoM C_Lib.c:235 TRACED:CPU<-Dirac - Length=8 (20:5) [90-01-01 00:00:48.468] 0\RC_HWU_TX tx_db_server.c:793 TRACED:TRX_DRV_ReadFW_CapabilityRsp: TxCap=0x001F, RxCap=0x0007 [90-01-01 00:00:48.468] 0\RC_HWU_TX tx_db_server.c:555 TRACED:TCC=1, TSPS=0, GMSK_pwr=15-45 dBm, 8PSK_pwr=16-42 dBm, [90-01-01 00:00:48.468] 0\RC_HWU_TX tx_db_server.c:558 TRACED:16QAM_pwr=16-41 dBm, 32QAM_pwr=16-40 dBm, AQPSK_pwr=16-42 dBm [90-01-01 00:00:48.468] 0\RC_CO_TxP co_tx_local_conf.c:1608 TRACED:GMSK_cap=33-45 dBm, 8PSK_cap=33-42 dBm [90-01-01 00:00:48.468] 0\RC_CO_TxP co_tx_local_conf.c:1616 TRACED:16QAM_cap=33-41 dBm, 32QAM_cap=33-40 dBm, AQPSK_cap=33-42 dBm [90-01-01 00:00:48.522] 0\RC_HWU_RC funcdb.c:1370 TRACED:No tuning_support. Using default parameters RT1013, RT1014, RT1016 [90-01-01 00:00:48.530] 1\RC_HWU_TX tx_db_server.c:716 TRACED:INFO: Failed reading RT1130 TSPS, set to TSPS Not Supported [90-01-01 00:00:48.530] 1\C_DiracOoM C_Lib.c:235 TRACED:CPU->Dirac - Length=2 (20:5) [90-01-01 00:00:48.530] 1\C_DiracOoM C_Lib.c:235 TRACED:CPU<-Dirac - Length=8 (20:5) [90-01-01 00:00:48.532] 1\RC_HWU_TX tx_db_server.c:793 TRACED:TRX_DRV_ReadFW_CapabilityRsp: TxCap=0x001F, RxCap=0x0007 [90-01-01 00:00:48.532] 1\RC_HWU_TX tx_db_server.c:555 TRACED:TCC=1, TSPS=0, GMSK_pwr=15-45 dBm, 8PSK_pwr=16-42 dBm, [90-01-01 00:00:48.532] 1\RC_HWU_TX tx_db_server.c:558 TRACED:16QAM_pwr=16-41 dBm, 32QAM_pwr=16-40 dBm, AQPSK_pwr=16-42 dBm [90-01-01 00:00:48.532] 1\RC_CO_TxP co_tx_local_conf.c:1608 TRACED:GMSK_cap=33-45 dBm, 8PSK_cap=33-42 dBm [90-01-01 00:00:48.532] 1\RC_CO_TxP co_tx_local_conf.c:1616 TRACED:16QAM_cap=33-41 dBm, 32QAM_cap=33-40 dBm, AQPSK_cap=33-42 dBm [90-01-01 00:00:48.536] 0\TRX_DRV C_Lib.c:1053 TRACED:0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 [90-01-01 00:00:48.538] 1\TRX_DRV C_Lib.c:1053 TRACED:0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 [90-01-01 00:00:48.540] 0\RC_HWU_TX hwu_tx_super_mask.c:93 TRACED:SupervisionMask=0000 [90-01-01 00:00:48.540] 1\RC_HWU_TX hwu_tx_super_mask.c:93 TRACED:SupervisionMask=0000 [90-01-01 00:00:48.628] 1\RC_HWU_RC funcdb.c:1370 TRACED:No tuning_support. Using default parameters RT1013, RT1014, RT1016 [90-01-01 00:00:49.456] 0\RC_CO_RX_P rx_dep_way_config.c:865 TRACED:RX in switch: 1, (A 1, B 1) [90-01-01 00:00:49.456] 0\RC_CO_RX_P rx_dep_way_config.c:866 TRACED:RX_Path_Config: 0 [90-01-01 00:00:49.456] 0\RC_CO_RX_P rx_dep_way_config.c:886 TRACED:RxDelay:A/B=20/20-RxInSwitch=0x0001,A=0x0001,B=0x0001,RxPathCon=0 [90-01-01 00:00:49.456] 0\RC_CO_RX_P rx_dep_way_config.c:764 TRACED:RSSI A/B: base=-14.6/-14.4,offs[base]=-10.0/-10.5 [90-01-01 00:00:49.458] 0\RC_CO_RX_P rx_dep_way_config.c:764 TRACED:Loop A/B: base=0.0/0.4,offs[base]=-10.6/-10.7 [90-01-01 00:00:49.458] 0\RC_CO_RX_P rx_dep_way_config.c:903 TRACED:Margin A/B=0/0 [90-01-01 00:00:49.464] 0\RC_HWU_RC db.c:183 TRACED:No debug RCFDB file found, sending created RCFDB [90-01-01 00:00:49.466] 0\C_DiracSplit C_DiracSplit.c:103 TRACED:RCFDB tot_size/revision/num_of_params/entry_offset (hex): 3a63/401/60/39be [90-01-01 00:00:49.690] 0\C_DiracSplit C_DiracSplit.c:107 TRACED:RCFDB crc: 0x9c56 [90-01-01 00:00:49.696] 0\RC_HWU_RC funcdb.c:1075 TRACED:RCFDB load complete, outcome: 0 [90-01-01 00:00:49.698] 0\RC_HWU_RC funcdb.c:1096 TRACED:INFO: PT0008 not found, assume not RRU-N [90-01-01 00:00:49.698] 0\RC_HWU_RC funcdb.c:800 TRACED:UC_HC = 0 [90-01-01 00:00:49.698] 0\C_DiracOoM C_Lib.c:1053 TRACED:00000: 0600 0000 [90-01-01 00:00:49.708] 1\RC_CO_RX_P rx_dep_way_config.c:865 TRACED:RX in switch: 1, (A 1, B 1) [90-01-01 00:00:49.708] 1\RC_CO_RX_P rx_dep_way_config.c:866 TRACED:RX_Path_Config: 0 [90-01-01 00:00:49.708] 1\RC_CO_RX_P rx_dep_way_config.c:886 TRACED:RxDelay:A/B=20/20-RxInSwitch=0x0001,A=0x0001,B=0x0001,RxPathCon=0 [90-01-01 00:00:49.708] 1\RC_CO_RX_P rx_dep_way_config.c:764 TRACED:RSSI A/B: base=-14.6/-14.4,offs[base]=-11.5/-11.9 [90-01-01 00:00:49.708] 1\RC_CO_RX_P rx_dep_way_config.c:764 TRACED:Loop A/B: base=0.0/0.4,offs[base]=-11.6/-11.6 [90-01-01 00:00:49.708] 1\RC_CO_RX_P rx_dep_way_config.c:903 TRACED:Margin A/B=0/0 [90-01-01 00:00:49.714] 1\RC_HWU_RC db.c:183 TRACED:No debug RCFDB file found, sending created RCFDB [90-01-01 00:00:49.714] 1\C_DiracSplit C_DiracSplit.c:103 TRACED:RCFDB tot_size/revision/num_of_params/entry_offset (hex): 3664/401/60/35bf [90-01-01 00:00:49.900] 1\C_DiracSplit C_DiracSplit.c:107 TRACED:RCFDB crc: 0xa7d [90-01-01 00:00:49.900] 1\RC_HWU_RC funcdb.c:1075 TRACED:RCFDB load complete, outcome: 0 [90-01-01 00:00:49.900] 1\RC_HWU_RC funcdb.c:1096 TRACED:INFO: PT0008 not found, assume not RRU-N [90-01-01 00:00:49.900] 1\RC_HWU_RC funcdb.c:800 TRACED:UC_HC = 0 [90-01-01 00:00:49.902] 1\C_DiracOoM C_Lib.c:1053 TRACED:00000: 0600 0000 [90-01-01 00:00:50.408] 0\RC_CO_TxP co_tx_super.c:549 TRACED:INFO: TRX_RU LocalIDB_RU_Type8_0 = 7 [90-01-01 00:00:50.408] 0\RC_CO_TxP co_tx_super.c:563 TRACED:INFO: Not DRU/EDRU/RRU_N, Do not run HCOMBS Load Power Test [90-01-01 00:00:50.414] 0\RC_CO_TxP co_tx_rf_loop.c:739 TRACED:Fetching HWU_Main from ODB [90-01-01 00:00:50.414] 0\RC_CO_TxP co_tx_rf_loop.c:744 TRACED:HWU_MAIN successfully fetched from ODB [90-01-01 00:00:50.416] 0\RC_CO_TxP tx_tempsensor_cd.c:342 TRACED:Subscribe on CLASS=TempSensorCD && FuncId=CD0 [90-01-01 00:00:50.418] 0\RC_CO_TxP se_trx_vswr.c:269 TRACED:INFO: alarm report DISABLED for SE_CD_INPUT_VSWR [90-01-01 00:00:50.426] 0\RC_CO_RX_P rx_dep_way_config.c:1396 TRACED:Number of TRX:es/RXD=2 [90-01-01 00:00:50.430] 0\RC_CO_RX_P rx_dep_way_config.c:1396 TRACED:Number of TRX:es/RXD=2 [90-01-01 00:00:50.430] 0\RC_CO_RX_P co_rx_path.c:2016 TRACEH:### CO_RxPath ready for services ### [90-01-01 00:00:50.436] 0\RC_CO_TxP se_trx_pa_temperature.c:607 TRACED:PA Temp high lim C1=340 x 0.25C, low lim C1=0 x 0.25C [90-01-01 00:00:50.436] 0\RC_CO_TxP se_trx_pa_temperature.c:608 TRACED:PA Temp high lim C2=320 x 0.25C, low lim C2=20 x 0.25C [90-01-01 00:00:50.442] 0\RC_CO_TxP se_pf_fault_prefl.c:169 TRACED:This is not a CDU A/C/C++, SE_PF_FAULT NOT installed [90-01-01 00:00:50.442] 0\RC_CO_TxP se_trx_hc_load_power.c:128 TRACED:Install SE_TRX_HC_LOAD_POWER SUCCEEDED [90-01-01 00:00:50.446] 0\RC_CO_TxP co_tx_path.c:343 TRACEH:### CO_TxPath ready for services ### [90-01-01 00:00:50.446] 0\RC_CO_TxP o_tx_subscr_chain_delay.c:122 TRACED:tx_chain_delay = 17834 ns (FD_Delay7_0 17784 + TX path 50) [90-01-01 00:00:50.446] 0\RC_CO_TxP co_tx_subscribe_cap.c:108 TRACED:Send CO_TxPath_SubscribeCapabilitiesRsp: [90-01-01 00:00:50.446] 0\RC_CO_TxP co_tx_subscribe_cap.c:115 TRACED: txBand=2, #Arfcn=374, arfcnBase=512, hopp=3, tcc=0, tsps=0, [90-01-01 00:00:50.446] 0\RC_CO_TxP co_tx_subscribe_cap.c:121 TRACED: txMaxBW=0 kHz, pwrGmsk=33-45 dBm, pwr8psk=33-42 dBm, [90-01-01 00:00:50.446] 0\RC_CO_TxP co_tx_subscribe_cap.c:128 TRACED: pwr16qam=33-41 dBm, pwr32qam=33-40 dBm, pwrAqpsk=33-42 dBm [90-01-01 00:00:50.498] 0\RC_CO_TxP se_cd_opwr_vswr.c:2478 TRACED:VSWR Sup.=1, VSWR_class1[5] (220), VSWR_class2[3] (180) [90-01-01 00:00:50.498] 0\RC_CO_TxP se_cd_opwr_vswr.c:2478 TRACED:VSWR Sup.=1, VSWR_class1[5] (220), VSWR_class2[3] (180) [90-01-01 00:00:50.498] 0\RC_CO_TxP se_cd_opwr_vswr.c:2478 TRACED:VSWR Sup.=1, VSWR_class1[5] (220), VSWR_class2[3] (180) [90-01-01 00:00:50.498] 0\RC_CO_TxP tx_tempsensor_cd.c:380 TRACED:Attached to TempSensorCD, s_obj=0x6b, c_obj=0x2a [90-01-01 00:00:50.502] 0\RC_CO_TxP tx_tempsensor_cd.c:466 TRACED:TempSensorCD Status change - UN->OK,Temp=301 [90-01-01 00:00:50.502] 0\RC_CO_TxP tx_tempsensor_cd.c:479 TRACED:TempSensorCD - CurrTemp=301 (from CDU) [90-01-01 00:00:51.176] 0\RC_HWU_RX hwu_rx_operate.c:1931 TRACED:RX temp comp: start -10, step 5, number 20 [90-01-01 00:00:51.258] 1\RC_CO_TxP co_tx_super.c:549 TRACED:INFO: TRX_RU LocalIDB_RU_Type8_0 = 7 [90-01-01 00:00:51.258] 1\RC_CO_TxP co_tx_super.c:563 TRACED:INFO: Not DRU/EDRU/RRU_N, Do not run HCOMBS Load Power Test [90-01-01 00:00:51.262] 1\RC_CO_TxP co_tx_rf_loop.c:739 TRACED:Fetching HWU_Main from ODB [90-01-01 00:00:51.264] 1\RC_CO_TxP co_tx_rf_loop.c:744 TRACED:HWU_MAIN successfully fetched from ODB [90-01-01 00:00:51.266] 1\RC_CO_TxP tx_tempsensor_cd.c:342 TRACED:Subscribe on CLASS=TempSensorCD && FuncId=CD0 [90-01-01 00:00:51.268] 1\RC_CO_TxP se_trx_vswr.c:269 TRACED:INFO: alarm report DISABLED for SE_CD_INPUT_VSWR [90-01-01 00:00:51.276] 1\RC_CO_RX_P rx_dep_way_config.c:1396 TRACED:Number of TRX:es/RXD=2 [90-01-01 00:00:51.282] 1\RC_CO_RX_P rx_dep_way_config.c:1396 TRACED:Number of TRX:es/RXD=2 [90-01-01 00:00:51.282] 1\RC_CO_RX_P co_rx_path.c:2016 TRACEH:### CO_RxPath ready for services ### [90-01-01 00:00:51.282] P_MPSS_LSM lsm_loader.c:3500 TRACEH:OperationalReport from RC [90-01-01 00:00:51.282] P_MPSS_LSM lsm_loader.c:3059 TRACEH:TraceH_Checkpoint: NodeStartState = PlatformOperational [90-01-01 00:00:51.282] P_MPSS_LSM lsm_loader.c:3063 TRACEH:TraceH_Checkpoint: NodeStartState = SystemOperational [90-01-01 00:00:51.288] 1\RC_CO_TxP se_trx_pa_temperature.c:607 TRACED:PA Temp high lim C1=340 x 0.25C, low lim C1=0 x 0.25C [90-01-01 00:00:51.288] 1\RC_CO_TxP se_trx_pa_temperature.c:608 TRACED:PA Temp high lim C2=320 x 0.25C, low lim C2=20 x 0.25C [90-01-01 00:00:51.294] 1\RC_CO_TxP se_pf_fault_prefl.c:169 TRACED:This is not a CDU A/C/C++, SE_PF_FAULT NOT installed [90-01-01 00:00:51.296] 1\RC_CO_TxP se_trx_hc_load_power.c:128 TRACED:Install SE_TRX_HC_LOAD_POWER SUCCEEDED [90-01-01 00:00:51.298] 1\RC_CO_TxP co_tx_path.c:343 TRACEH:### CO_TxPath ready for services ### [90-01-01 00:00:51.300] 1\RC_CO_TxP o_tx_subscr_chain_delay.c:122 TRACED:tx_chain_delay = 17834 ns (FD_Delay7_0 17784 + TX path 50) [90-01-01 00:00:51.300] 1\RC_CO_TxP co_tx_subscribe_cap.c:108 TRACED:Send CO_TxPath_SubscribeCapabilitiesRsp: [90-01-01 00:00:51.300] 1\RC_CO_TxP co_tx_subscribe_cap.c:115 TRACED: txBand=2, #Arfcn=374, arfcnBase=512, hopp=3, tcc=0, tsps=0, [90-01-01 00:00:51.300] 1\RC_CO_TxP co_tx_subscribe_cap.c:121 TRACED: txMaxBW=0 kHz, pwrGmsk=33-45 dBm, pwr8psk=33-42 dBm, [90-01-01 00:00:51.300] 1\RC_CO_TxP co_tx_subscribe_cap.c:128 TRACED: pwr16qam=33-41 dBm, pwr32qam=33-40 dBm, pwrAqpsk=33-42 dBm [90-01-01 00:00:51.316] 1\RC_CO_TxP tx_tempsensor_cd.c:380 TRACED:Attached to TempSensorCD, s_obj=0x6b, c_obj=0x2e [90-01-01 00:00:51.316] 1\RC_CO_TxP se_cd_opwr_vswr.c:2478 TRACED:VSWR Sup.=1, VSWR_class1[5] (220), VSWR_class2[3] (180) [90-01-01 00:00:51.316] 1\RC_CO_TxP se_cd_opwr_vswr.c:2478 TRACED:VSWR Sup.=1, VSWR_class1[5] (220), VSWR_class2[3] (180) [90-01-01 00:00:51.316] 1\RC_CO_TxP se_cd_opwr_vswr.c:2478 TRACED:VSWR Sup.=1, VSWR_class1[5] (220), VSWR_class2[3] (180) [90-01-01 00:00:51.320] 1\RC_CO_TxP tx_tempsensor_cd.c:466 TRACED:TempSensorCD Status change - UN->OK,Temp=301 [90-01-01 00:00:51.320] 1\RC_CO_TxP tx_tempsensor_cd.c:479 TRACED:TempSensorCD - CurrTemp=301 (from CDU) [90-01-01 00:00:51.374] 0\C_Super C_Super.c:1140 TRACED:Dirac ExtendedFaultMap - Bit 88:0->1 [90-01-01 00:00:51.618] O_TRXC_Main_0 TRXC1.c:6405 TRACED:Info: ( TRXC_SW6 CXC1125818_19.R1AA01), TRXC_instNr:1 [90-01-01 00:00:51.666] O_TRXC_Main_1 TRXC1.c:6405 TRACED:Info: ( TRXC_SW6 CXC1125818_19.R1AA01), TRXC_instNr:0 [90-01-01 00:00:51.676] 0\RC_HWU_PA tempsensor_pa.c:178 TRACED:Status changed to OK, temperature 275 [90-01-01 00:00:51.676] 0\RC_HWU_PA hwu_pa.c:890 TRACED:Voltage sup. hlc1=3200,llc1=2800,hlc2=3150,llc2=2850 [90-01-01 00:00:51.742] P_MPSS_LSM lsm_loader.c:2914 TRACED:Started TRXC, errCode 0, iad 1695000 [90-01-01 00:00:51.742] P_MPSS_LSM lsm_loader.c:3117 TRACEH:TraceH_Checkpoint: NodeStartState = ReadyForRemoteMode [90-01-01 00:00:51.742] P_MPSS_LSM lsm_loader.c:3500 TRACEH:OperationalReport from TRXC [90-01-01 00:00:51.742] P_MPSS_HWDB_HNDL HardwareDB.c:2148 TRACEH:Fast restart allowed [90-01-01 00:00:51.742] O_TRXC_Main_0 TRXC1.c:58803 TRACED:node start state ready for remote mode [90-01-01 00:00:51.748] O_TRXC_Main_1 TRXC1.c:58803 TRACED:node start state ready for remote mode [90-01-01 00:00:51.758] O_TRXC_Dnl_0 P/IC/HandleMoData_Body.ic:1067 TRACED:Error in file: /ARFCN/ARFCN Magic text error trxc:1 [90-01-01 00:00:51.758] O_TRXC_Dnl_0 CF_AbisUtilities.c:11083 TRACED:readFromFile error for TestARFCN_TRXC1 len:0, data:0 [90-01-01 00:00:51.760] O_TRXC_Dnl_0 TRXC1.c:83076 TRACED:INFO: SO TRX1 nvRam_len:0 stored_ARFCN:0 [90-01-01 00:00:51.760] O_TRXC_Dnl_0 TRXC1.c:83098 TRACED:SO TRX1 nvRam_len:0 stored_ARFCN:0 [90-01-01 00:00:51.760] O_TRXC_Dnl_0 TRXC1.c:83120 TRACED:SO TRX1 nvRam_len:0 stored_ARFCN:0 [90-01-01 00:00:51.764] O_TRXC_Dnl_100 P/IC/HandleMoData_Body.ic:1067 TRACED:Error in file: /ARFCN/ARFCN Magic text error trxc:0 [90-01-01 00:00:51.764] O_TRXC_Dnl_100 CF_AbisUtilities.c:11083 TRACED:readFromFile error for TestARFCN_TRXC0 len:0, data:0 [90-01-01 00:00:51.764] O_TRXC_Dnl_100 TRXC1.c:83076 TRACED:INFO: SO TRX0 nvRam_len:0 stored_ARFCN:0 [90-01-01 00:00:51.764] O_TRXC_Dnl_100 TRXC1.c:83098 TRACED:SO TRX0 nvRam_len:0 stored_ARFCN:0 [90-01-01 00:00:51.764] O_TRXC_Dnl_100 TRXC1.c:83120 TRACED:SO TRX0 nvRam_len:0 stored_ARFCN:0 [90-01-01 00:00:51.766] O_TRXC_Main_0 TRXC1.c:40397 TRACED:Unsubscribe Slave [90-01-01 00:00:51.774] O_TRXC_Dnl_0 TRXC1.c:120302 TRACED:not FuncTypeMCTR [90-01-01 00:00:51.786] O_TRXC_Main_1 TRXC1.c:10156 TRACEH:TRX-0 not 4WRD capable acc. to IDB [90-01-01 00:00:51.788] O_TRXC_Dnl_100 TRXC1.c:120302 TRACED:not FuncTypeMCTR [90-01-01 00:00:51.892] 1\C_DiracOoM C_DiracOoMSup1.c:308 TRACED:Dirac Fault Map = 0x0000.0000.0030.0000, Bit 20:0->1 [90-01-01 00:00:51.892] 1\C_DiracOoM C_DiracOoMSup1.c:308 TRACED:Dirac Fault Map = 0x0000.0000.0030.0000, Bit 21:0->1 [90-01-01 00:00:51.892] 1\RC_HWU_RX hwu_rx_operate.c:1931 TRACED:RX temp comp: start -10, step 5, number 20 [90-01-01 00:00:52.088] 1\C_Super C_Super.c:1140 TRACED:Dirac ExtendedFaultMap - Bit 88:0->1 [90-01-01 00:00:52.386] 1\RC_HWU_PA tempsensor_pa.c:178 TRACED:Status changed to OK, temperature 270 [90-01-01 00:00:52.388] 1\RC_HWU_PA hwu_pa.c:890 TRACED:Voltage sup. hlc1=3200,llc1=2800,hlc2=3150,llc2=2850 [90-01-01 00:00:52.394] 1\RC_HWU_RX hwu_rx_operate.c:3219 TRACED:Second Sys RXA RXD inport 0x54 is not RX3 or RX4 [90-01-01 00:00:52.396] 1\RC_HWU_RX hwu_rx_operate.c:2645 TRACED:RX_Cable1_not_connected [90-01-01 00:00:52.396] 1\RC_HWU_RX hwu_rx_operate.c:2671 TRACED:RX_Cable2_not_connected [90-01-01 00:00:52.742] P_MPSS_LSM lsm_loader.c:5493 TRACED:Start CRC bkg check [90-01-01 00:01:04.762] 0\LREC_CD_TX supervision.c:824 TRACED:Prep bef inst, SE_TRX_CDU_BUS_TX_CONTROL, freqClass2: 7 [90-01-01 00:01:04.762] 0\LREC_CD_TX supervision.c:825 TRACED:Prep bef inst, SE_TRX_CDU_BUS_TX_CONTROL, freqTimeInterval: 65 sek [90-01-01 00:01:04.794] 0\LREC_CD_TX lrec_cd_tx.c:2985 TRACED:First SetSynchMode rcvd, CD_SYNCH_MASTER , CD_VSWR_LIMITED , iss_nr 0 [90-01-01 00:01:04.802] 0\LREC_CD_TX cd_tx_sw_client.c:3418 TRACED:Since it is a CDU-G/J/L set state to APPL_CONFIG [90-01-01 00:01:04.802] 0\LREC_CD_TX lrec_cd_tx.c:1463 TRACED:Wait for RCFW ATC_State_Synchronized & TX_state_Local_Configured [90-01-01 00:01:44.848] 1\LREC_CD_TX lrec_cd_tx.c:1916 TRACED:INFO ONLY: Waited 1 minutes for FIRST SetSynchMode signal from CREC_TG! [90-01-01 00:01:53.430] P_MPSK_CLOCK timeout_clock_main.c:419 TRACED:Setting time: 20-11-03 11:46:15.908 [20-11-03 11:47:07.252] 1\LREC_CD_TX lrec_cd_tx.c:1916 TRACED:INFO ONLY: Waited 2 minutes for FIRST SetSynchMode signal from CREC_TG! [20-11-03 11:48:07.178] 1\LREC_CD_TX lrec_cd_tx.c:1916 TRACED:INFO ONLY: Waited 3 minutes for FIRST SetSynchMode signal from CREC_TG! [20-11-03 11:49:07.090] 1\LREC_CD_TX lrec_cd_tx.c:1916 TRACED:INFO ONLY: Waited 4 minutes for FIRST SetSynchMode signal from CREC_TG! [20-11-03 11:50:07.002] 1\LREC_CD_TX lrec_cd_tx.c:1916 TRACED:INFO ONLY: Waited 5 minutes for FIRST SetSynchMode signal from CREC_TG! [20-11-03 11:51:06.914] 1\LREC_CD_TX lrec_cd_tx.c:1914 TRACED:WARNING! Waited 6 minutes for FIRST SetSynchMode signal from CREC_TG! [20-11-03 11:51:13.808] O_TRXC_Main_1 TRXC1.c:11379 TRACED:Establish_ind received [20-11-03 11:51:13.862] O_TRXC_Main_1 TRXC1.c:12338 TRACEH:InterfaceVersion = G12R13_INTERFACE_VERSION [20-11-03 11:51:13.868] P_MPSS_MMI_HNDL LED.c:963 TRACEH:MMI indication for LED_Local state OFF [20-11-03 11:51:18.798] P_MPSS_MMI_HNDL LED.c:958 TRACED:MMI indication for LED_Operational state FLASH [20-11-03 11:51:18.816] 0\TRX_DRV C_Lib.c:1053 TRACED:0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0001 [20-11-03 11:51:18.818] 1\TRX_DRV C_Lib.c:1053 TRACED:0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0001 [20-11-03 11:51:18.838] 0\RC_CO_RX_P co_rx_operate.c:792 TRACED:Rx in state configured with diversity=2,arfcn=0,freq_spec_mrk=1 [20-11-03 11:51:22.822] 0\RC_HWU_RX hwu_rx_operate.c:592 TRACED:No ATC_State subscribe response received within 4 sec [20-11-03 11:51:22.822] 0\RC_CO_RX_P co_rx_operate.c:699 TRACED:Failed to enable Rx [20-11-03 11:51:22.824] O_TRXC_Dnl_100 TRXC1.c:146151 TRACED:ERROR: CO_EnableRsp CO_RX Failed. [20-11-03 11:51:22.826] 0\TRX_DRV C_Lib.c:1053 TRACED:0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 [20-11-03 11:51:22.826] 1\TRX_DRV C_Lib.c:1053 TRACED:0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 [20-11-03 11:51:22.836] 0\C_DiracOoM C_Lib.c:235 TRACED:CPU->Dirac - Length=2 (22:5) [20-11-03 11:51:22.838] 0\C_DiracOoM C_Lib.c:235 TRACED:CPU<-Dirac - Length=4 (22:5) [20-11-03 11:51:22.838] 0\RC_CO_RX_P co_rx_operate.c:862 TRACED:Rx in state reset. [20-11-03 11:51:23.006] 0\RC_CO_TxP co_tx_path.c:659 TRACED:CO_TX_Reset [20-11-03 11:51:23.010] 0\C_DiracOoM C_Lib.c:235 TRACED:CPU->Dirac - Length=2 (19:5) [20-11-03 11:51:23.028] 0\C_DiracOoM C_Lib.c:235 TRACED:CPU<-Dirac - Length=4 (19:5) [20-11-03 11:51:23.054] 0\RC_CO_TxP co_tx_path.c:659 TRACED:CO_TX_Reset [20-11-03 11:51:23.056] 0\C_DiracOoM C_Lib.c:235 TRACED:CPU->Dirac - Length=2 (19:5) [20-11-03 11:51:23.068] 0\C_DiracOoM C_Lib.c:235 TRACED:CPU<-Dirac - Length=4 (19:5) [20-11-03 11:51:23.102] O_TRXC_AoDnl_120 TRXC1.c:209298 TRACED:State changed for MO:TX:0 Distribute. [20-11-03 11:51:23.156] 0\RC_CO_TxP co_tx_config.c:399 TRACED:TxCfg Pwr=33,Ch=800,F=0,Tun=1,Mrk=0,Ad=0,Dl=0,Lp=1,Tcc=0,Bcc=7,Fpwr=0 [20-11-03 11:51:23.156] 0\RC_CO_TxP co_tx_config.c:400 TRACED:Hopping = 0 [20-11-03 11:51:23.156] 0\RC_CO_TxP co_tx_config.c:406 TRACED:BCCHPS; Act mode 0 Idl mode 0 pwr_red_offs 0 tn_bitmap 0x0 [20-11-03 11:51:23.260] 0\TRX_DRV C_Lib.c:1053 TRACED:0001 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 [20-11-03 11:51:23.260] 1\TRX_DRV C_Lib.c:1053 TRACED:0001 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 [20-11-03 11:51:27.264] 0\RC_HWU_TX hwu_tx_state.c:223 TRACED:TX Enable FAILED!, RCFW_ATC_State NOT Synchronized [20-11-03 11:51:27.266] 0\TRX_DRV C_Lib.c:1053 TRACED:0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 [20-11-03 11:51:27.268] 1\TRX_DRV C_Lib.c:1053 TRACED:0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 [20-11-03 11:51:27.336] P_MPSS_MMI_HNDL LED.c:958 TRACED:MMI indication for LED_Operational state ON [20-11-03 11:51:27.434] 0\C_DiracOoM C_Lib.c:235 TRACED:CPU->Dirac - Length=2 (22:5) [20-11-03 11:51:27.434] 0\C_DiracOoM C_Lib.c:235 TRACED:CPU<-Dirac - Length=4 (22:5) [20-11-03 11:51:27.434] 0\RC_CO_RX_P co_rx_operate.c:862 TRACED:Rx in state reset. [20-11-03 11:51:27.484] 0\C_DiracOoM C_Lib.c:235 TRACED:CPU->Dirac - Length=2 (22:5) [20-11-03 11:51:27.484] 0\C_DiracOoM C_Lib.c:235 TRACED:CPU<-Dirac - Length=4 (22:5) [20-11-03 11:51:27.484] 0\RC_CO_RX_P co_rx_operate.c:862 TRACED:Rx in state reset. [20-11-03 11:51:27.534] O_TRXC_AoDnl_118 TRXC1.c:209298 TRACED:State changed for MO:RX:0 Distribute. [20-11-03 11:51:27.590] 0\RC_CO_RX_P co_rx_operate.c:792 TRACED:Rx in state configured with diversity=1,arfcn=0,freq_spec_mrk=1 [20-11-03 11:51:31.668] 0\RC_HWU_RX hwu_rx_operate.c:592 TRACED:No ATC_State subscribe response received within 4 sec [20-11-03 11:51:31.668] 0\RC_CO_RX_P co_rx_operate.c:699 TRACED:Failed to enable Rx [20-11-03 11:51:31.670] O_TRXC_AoDnl_118 TRXC1.c:174474 TRACED:WARN: CO_EnableRsp NOT OK [20-11-03 11:51:32.086] 0\T_PCS_EXEC t_pcs_exec.cc:459 TRACEH:TIMING_REQ Error: result 3, current state 0 [20-11-03 11:51:33.086] 0\T_PCA t_pca_enable.cc:186 TRACEH:PCT START REQ timeout [20-11-03 11:51:33.086] 0\CO_TS t_tsam_co_ts.cc:2269 TRACEH:PCC enable NOT_OK [20-11-03 11:51:33.510] 0\T_PCS_EXEC t_pcs_exec.cc:459 TRACEH:TIMING_REQ Error: result 3, current state 0 [20-11-03 11:51:34.510] 0\T_PCA t_pca_enable.cc:186 TRACEH:PCT START REQ timeout [20-11-03 11:51:34.510] 0\CO_TS t_tsam_co_ts.cc:2269 TRACEH:PCC enable NOT_OK [20-11-03 11:51:34.930] 0\T_PCS_EXEC t_pcs_exec.cc:459 TRACEH:TIMING_REQ Error: result 3, current state 0 [20-11-03 11:51:35.930] 0\T_PCA t_pca_enable.cc:186 TRACEH:PCT START REQ timeout [20-11-03 11:51:35.930] 0\CO_TS t_tsam_co_ts.cc:2269 TRACEH:PCC enable NOT_OK [20-11-03 11:51:36.348] 0\T_PCS_EXEC t_pcs_exec.cc:459 TRACEH:TIMING_REQ Error: result 3, current state 0 [20-11-03 11:51:37.350] 0\T_PCA t_pca_enable.cc:186 TRACEH:PCT START REQ timeout [20-11-03 11:51:37.350] 0\CO_TS t_tsam_co_ts.cc:2269 TRACEH:PCC enable NOT_OK [20-11-03 11:51:37.768] 0\T_PCS_EXEC t_pcs_exec.cc:459 TRACEH:TIMING_REQ Error: result 3, current state 0 [20-11-03 11:51:38.768] 0\T_PCA t_pca_enable.cc:186 TRACEH:PCT START REQ timeout [20-11-03 11:51:38.768] 0\CO_TS t_tsam_co_ts.cc:2269 TRACEH:PCC enable NOT_OK [20-11-03 11:51:39.186] 0\T_PCS_EXEC t_pcs_exec.cc:459 TRACEH:TIMING_REQ Error: result 3, current state 0 [20-11-03 11:51:40.186] 0\T_PCA t_pca_enable.cc:186 TRACEH:PCT START REQ timeout [20-11-03 11:51:40.186] 0\CO_TS t_tsam_co_ts.cc:2269 TRACEH:PCC enable NOT_OK [20-11-03 11:51:40.604] 0\T_PCS_EXEC t_pcs_exec.cc:459 TRACEH:TIMING_REQ Error: result 3, current state 0 [20-11-03 11:51:41.588] 0\T_PCA t_pca_enable.cc:186 TRACEH:PCT START REQ timeout [20-11-03 11:51:41.588] 0\CO_TS t_tsam_co_ts.cc:2269 TRACEH:PCC enable NOT_OK [20-11-03 11:51:42.028] 0\T_PCS_EXEC t_pcs_exec.cc:459 TRACEH:TIMING_REQ Error: result 3, current state 0 [20-11-03 11:51:43.028] 0\T_PCA t_pca_enable.cc:186 TRACEH:PCT START REQ timeout [20-11-03 11:51:43.028] 0\CO_TS t_tsam_co_ts.cc:2269 TRACEH:PCC enable NOT_OK [20-11-03 11:52:06.824] 1\LREC_CD_TX lrec_cd_tx.c:1914 TRACED:WARNING! Waited 7 minutes for FIRST SetSynchMode signal from CREC_TG! [20-11-03 11:53:06.736] 1\LREC_CD_TX lrec_cd_tx.c:1914 TRACED:WARNING! Waited 8 minutes for FIRST SetSynchMode signal from CREC_TG! [20-11-03 11:54:06.648] 1\LREC_CD_TX lrec_cd_tx.c:1914 TRACED:WARNING! Waited 9 minutes for FIRST SetSynchMode signal from CREC_TG! [20-11-03 11:55:06.560] 1\LREC_CD_TX lrec_cd_tx.c:1914 TRACED:WARNING! Waited 10 minutes for FIRST SetSynchMode signal from CREC_TG! [20-11-03 11:56:06.472] 1\LREC_CD_TX lrec_cd_tx.c:1914 TRACED:WARNING! Waited 11 minutes for FIRST SetSynchMode signal from CREC_TG! [20-11-03 11:57:06.400] 1\LREC_CD_TX lrec_cd_tx.c:1914 TRACED:WARNING! Waited 12 minutes for FIRST SetSynchMode signal from CREC_TG! [20-11-03 11:58:06.318] 1\LREC_CD_TX lrec_cd_tx.c:1914 TRACED:WARNING! Waited 13 minutes for FIRST SetSynchMode signal from CREC_TG! [20-11-03 11:59:06.230] 1\LREC_CD_TX lrec_cd_tx.c:1914 TRACED:WARNING! Waited 14 minutes for FIRST SetSynchMode signal from CREC_TG! [20-11-03 12:00:06.142] 1\LREC_CD_TX lrec_cd_tx.c:1914 TRACED:WARNING! Waited 15 minutes for FIRST SetSynchMode signal from CREC_TG! [20-11-03 12:00:10.732] P_MPSS_LSM lsm_oper.c:1355 TRACED:All loadfiles OK [20-11-03 12:01:06.054] 1\LREC_CD_TX lrec_cd_tx.c:1914 TRACED:WARNING! Waited 16 minutes for FIRST SetSynchMode signal from CREC_TG! [20-11-03 12:02:05.966] 1\LREC_CD_TX lrec_cd_tx.c:1914 TRACED:WARNING! Waited 17 minutes for FIRST SetSynchMode signal from CREC_TG! [20-11-03 12:03:05.880] 1\LREC_CD_TX lrec_cd_tx.c:1914 TRACED:WARNING! Waited 18 minutes for FIRST SetSynchMode signal from CREC_TG! [20-11-03 12:04:05.792] 1\LREC_CD_TX lrec_cd_tx.c:1914 TRACED:WARNING! Waited 19 minutes for FIRST SetSynchMode signal from CREC_TG! [20-11-03 12:05:05.700] 1\LREC_CD_TX lrec_cd_tx.c:1914 TRACED:WARNING! Waited 20 minutes for FIRST SetSynchMode signal from CREC_TG! [20-11-03 12:06:05.630] 1\LREC_CD_TX lrec_cd_tx.c:1914 TRACED:WARNING! Waited 21 minutes for FIRST SetSynchMode signal from CREC_TG! [20-11-03 12:07:05.544] 1\LREC_CD_TX lrec_cd_tx.c:1914 TRACED:WARNING! Waited 22 minutes for FIRST SetSynchMode signal from CREC_TG! [20-11-03 12:08:05.456] 1\LREC_CD_TX lrec_cd_tx.c:1914 TRACED:WARNING! Waited 23 minutes for FIRST SetSynchMode signal from CREC_TG! [20-11-03 12:09:05.368] 1\LREC_CD_TX lrec_cd_tx.c:1914 TRACED:WARNING! Waited 24 minutes for FIRST SetSynchMode signal from CREC_TG! [20-11-03 12:09:23.466] O_TRXC_Main_1 TRXC1.c:12584 TRACED:Release_ind received [20-11-03 12:09:23.466] O_TRXC_AoDnl_120 TRXC1.c:152319 TRACED:LinkStateRpt MO:TX:0 Start 85s Timer [20-11-03 12:09:23.468] O_TRXC_AoDnl_102 TRXC1.c:152319 TRACED:LinkStateRpt MO:TS:0 Start 85s Timer [20-11-03 12:09:23.468] O_TRXC_AoDnl_104 TRXC1.c:152319 TRACED:LinkStateRpt MO:TS:1 Start 85s Timer [20-11-03 12:09:23.468] P_MPSS_MMI_HNDL LED.c:963 TRACEH:MMI indication for LED_Local state FLASH [20-11-03 12:09:23.468] O_TRXC_AoDnl_106 TRXC1.c:152319 TRACED:LinkStateRpt MO:TS:2 Start 85s Timer [20-11-03 12:09:23.468] O_TRXC_AoDnl_108 TRXC1.c:152319 TRACED:LinkStateRpt MO:TS:3 Start 85s Timer [20-11-03 12:09:23.468] O_TRXC_AoDnl_110 TRXC1.c:152319 TRACED:LinkStateRpt MO:TS:4 Start 85s Timer [20-11-03 12:09:23.468] O_TRXC_AoDnl_112 TRXC1.c:152319 TRACED:LinkStateRpt MO:TS:5 Start 85s Timer [20-11-03 12:09:23.468] O_TRXC_AoDnl_114 TRXC1.c:152319 TRACED:LinkStateRpt MO:TS:6 Start 85s Timer [20-11-03 12:09:23.468] O_TRXC_AoDnl_116 TRXC1.c:152319 TRACED:LinkStateRpt MO:TS:7 Start 85s Timer [20-11-03 12:09:23.468] O_TRXC_AoDnl_118 TRXC1.c:152319 TRACED:LinkStateRpt MO:RX:0 Start 85s Timer [20-11-03 12:10:05.278] 1\LREC_CD_TX lrec_cd_tx.c:1914 TRACED:WARNING! Waited 25 minutes for FIRST SetSynchMode signal from CREC_TG! [20-11-03 12:10:48.380] P_MPSS_MMI_HNDL LED.c:958 TRACED:MMI indication for LED_Operational state OFF [20-11-03 12:11:05.190] 1\LREC_CD_TX lrec_cd_tx.c:1914 TRACED:WARNING! Waited 26 minutes for FIRST SetSynchMode signal from CREC_TG! [20-11-03 12:12:05.102] 1\LREC_CD_TX lrec_cd_tx.c:1914 TRACED:WARNING! Waited 27 minutes for FIRST SetSynchMode signal from CREC_TG! [20-11-03 12:13:05.018] 1\LREC_CD_TX lrec_cd_tx.c:1914 TRACED:WARNING! Waited 28 minutes for FIRST SetSynchMode signal from CREC_TG! [20-11-03 12:14:04.934] 1\LREC_CD_TX lrec_cd_tx.c:1914 TRACED:WARNING! Waited 29 minutes for FIRST SetSynchMode signal from CREC_TG! [20-11-03 12:15:04.848] 1\LREC_CD_TX lrec_cd_tx.c:1914 TRACED:WARNING! Waited 30 minutes for FIRST SetSynchMode signal from CREC_TG! [20-11-03 12:25:03.972] 1\LREC_CD_TX lrec_cd_tx.c:1914 TRACED:WARNING! Waited 40 minutes for FIRST SetSynchMode signal from CREC_TG! [20-11-03 12:25:20.834] P_MPSK_RPA rpa.c:221 TRACEH:Poolsize 11533456 used 4145936 free 7387520 [20-11-03 12:25:20.834] P_MPSK_RPA rpa.c:226 TRACEH: Size 79 allocated 1573 freelist 70 [20-11-03 12:25:20.834] P_MPSK_RPA rpa.c:226 TRACEH: Size 143 allocated 98 freelist 30 [20-11-03 12:25:20.834] P_MPSK_RPA rpa.c:226 TRACEH: Size 303 allocated 311 freelist 50 [20-11-03 12:25:20.834] P_MPSK_RPA rpa.c:226 TRACEH: Size 527 allocated 181 freelist 4 [20-11-03 12:25:20.834] P_MPSK_RPA rpa.c:226 TRACEH: Size 2063 allocated 41 freelist 12 [20-11-03 12:25:20.834] P_MPSK_RPA rpa.c:226 TRACEH: Size 8207 allocated 84 freelist 0 [20-11-03 12:25:20.834] P_MPSK_RPA rpa.c:226 TRACEH: Size 16399 allocated 12 freelist 4 [20-11-03 12:25:20.834] P_MPSK_RPA rpa.c:226 TRACEH: Size 32783 allocated 8 freelist 4 [20-11-03 12:30:35.186] P_MPSS_MMI_HNDL LED.c:1324 TRACED:LED::Receive monitor start for numer 3 [20-11-03 12:30:35.196] P_MPSS_MMI_HNDL LED.c:1324 TRACED:LED::Receive monitor start for numer 2 [20-11-03 12:30:35.204] P_MPSS_MMI_HNDL LED.c:1324 TRACED:LED::Receive monitor start for numer 0 [20-11-03 12:30:35.214] P_MPSS_MMI_HNDL LED.c:1324 TRACED:LED::Receive monitor start for numer 1 [20-11-03 12:35:03.076] 1\LREC_CD_TX lrec_cd_tx.c:1914 TRACED:WARNING! Waited 50 minutes for FIRST SetSynchMode signal from CREC_TG! [20-11-03 12:37:42.694] P_MPSK_RPA rpa.c:221 TRACEH:Poolsize 11533456 used 4162480 free 7370976 [20-11-03 12:37:42.694] P_MPSK_RPA rpa.c:226 TRACEH: Size 79 allocated 1581 freelist 62 [20-11-03 12:37:42.694] P_MPSK_RPA rpa.c:226 TRACEH: Size 143 allocated 97 freelist 31 [20-11-03 12:37:42.694] P_MPSK_RPA rpa.c:226 TRACEH: Size 303 allocated 311 freelist 50 [20-11-03 12:37:42.694] P_MPSK_RPA rpa.c:226 TRACEH: Size 527 allocated 181 freelist 4 [20-11-03 12:37:42.694] P_MPSK_RPA rpa.c:226 TRACEH: Size 2063 allocated 41 freelist 12 [20-11-03 12:37:42.694] P_MPSK_RPA rpa.c:226 TRACEH: Size 8207 allocated 84 freelist 2 [20-11-03 12:37:42.694] P_MPSK_RPA rpa.c:226 TRACEH: Size 16399 allocated 12 freelist 4 [20-11-03 12:37:42.694] P_MPSK_RPA rpa.c:226 TRACEH: Size 32783 allocated 8 freelist 4 **** General log **** [90-01-01 00:00:00.010] NONAME debug_main.c:2909 TRACEH:OS-info: OSE Delta PowerPC krn-4xx/P2.3.2.0 [90-01-01 00:00:00.010] NONAME debug_main.c:2941 TRACEH:No restart info [90-01-01 00:00:00.010] NONAME debug_main.c:2956 TRACEH:Reset time: Not set [90-01-01 00:00:00.010] NONAME debug_main.c:3066 TRACEH:Load file=TRPR41GZ Program version=VEP-PPU CXC1121730_19.R1L01, System start cause=POWER_ON(0), Appl type=LFINFO_UPDATED_APPL(1) [90-01-01 00:00:00.020] P_MPSF_MICROSM microsm.c:1107 TRACEH:OK: entering COLDSTART phase [90-01-01 00:00:00.132] P_MPSS_LSM lsm_loader.c:4262 TRACEH:RBS Family: 0 [90-01-01 00:00:00.134] P_MPSS_LSM lsm_loader.c:4277 TRACEH:Board type (hex): a [90-01-01 00:00:00.196] P_MPSS_LSM lsm_file_info.c:1687 TRACEH:FilePckgName:CXP1040007_09R41G [90-01-01 00:00:00.400] P_MPSS_HWDB_HNDL HardwareDB.c:838 TRACEH:RBS Family: 0 [90-01-01 00:00:00.402] P_MPSS_HWU_MAIN hwuadm_main.c:395 TRACEH:RBS Family: 0 [90-01-01 00:00:00.406] P_MPSS_HWU_MAIN hwuadm_main.c:321 TRACEH:RU Type = 7 [90-01-01 00:00:00.410] P_MPSS_LSM lsm_loader.c:3081 TRACEH:InternalState = _hwu [90-01-01 00:00:00.418] P_NPSENSORS npsensors.c:623 TRACEH:Process not needed anymore, will be stopped [90-01-01 00:00:00.596] P_MPSS_LSM lsm_loader.c:3500 TRACEH:OperationalReport from TRNSD [90-01-01 00:00:00.618] TAROT_DRV_MAIN_A tarot_drv_main.c:1549 TRACEH:HWU_Tarot: HW Configured for MASTER only [90-01-01 00:00:00.618] TAROT_DRV_MAIN_A tarot_drv_main.c:1805 TRACEH:HWU_Tarot: Loading file: DSPX0_FW Revision: _17.R5B01 Size: 459 Kbyte [90-01-01 00:00:01.134] TAROT_DRV_MAIN_A tarot_drv_main.c:1647 TRACEH:HWU_Tarot: MASTER TAROT Load and Activation OK (DSPmode DSPG0_FW, CPRIind 0) [90-01-01 00:00:01.154] TAROT_DRV_MAIN_B tarot_drv_main.c:1549 TRACEH:HWU_Tarot: HW Configured for MASTER only [90-01-01 00:00:01.154] TAROT_DRV_MAIN_B tarot_drv_main.c:1805 TRACEH:HWU_Tarot: Loading file: DSPX0_FW Revision: _17.R5B01 Size: 459 Kbyte [90-01-01 00:00:01.668] P_MPSS_MMI_HNDL LED.c:963 TRACEH:MMI indication for LED_Local state FLASH [90-01-01 00:00:01.668] TAROT_DRV_MAIN_B tarot_drv_main.c:1647 TRACEH:HWU_Tarot: MASTER TAROT Load and Activation OK (DSPmode DSPG0_FW, CPRIind 0) [90-01-01 00:00:34.572] P_TRNSD_BM bus_mgr_hw.c:910 TRACEH:Y2 BOOT is ready for TRX1 [90-01-01 00:00:34.636] P_TRNSD_BM bus_mgr_hw.c:910 TRACEH:Y2 BOOT is ready for TRX0 [90-01-01 00:00:35.144] P_MPSS_LSM lsm_loader.c:3865 TRACEH:Waiting for internal report [90-01-01 00:00:35.144] P_MPSS_LSM lsm_loader.c:3081 TRACEH:InternalState = _inst [90-01-01 00:00:35.366] P_MPSS_LSM lsm_loader.c:3500 TRACEH:OperationalReport from LOMP [90-01-01 00:00:39.254] P_MPSS_LSM lsm_loader.c:3055 TRACEH:TraceH_Checkpoint: NodeStartState = SWConsistency [90-01-01 00:00:39.256] P_MPSS_LSM lsm_loader.c:3081 TRACEH:InternalState = _test [90-01-01 00:00:39.256] PLS_SAP_MAIN sap_main.c:2134 TRACEH:SAP ENABLED [90-01-01 00:00:40.838] 0\T_TSAM_TAS t_tsam_tas.cc:428 TRACEH:TFS SW revision: CXP 102 52/14 R7A01 [90-01-01 00:00:40.876] 1\T_TSAM_TAS t_tsam_tas.cc:428 TRACEH:TFS SW revision: CXP 102 52/14 R7A01 [90-01-01 00:00:44.648] O_LocalIDB LOMP1.c:18179 TRACEH:Checkpoint: NodeStartState = IDB_Consistency. [90-01-01 00:00:44.662] LREC_MAIN lrec_main.c:1390 TRACEH:Nr of sub RUs connected to this TRX = 1 [90-01-01 00:00:44.662] LREC_MAIN lrec_main.c:1396 TRACEH:FuncType = 4, FuncInst = 0 [90-01-01 00:00:46.656] P_MPSS_LSM lsm_loader.c:3500 TRACEH:OperationalReport from LREC [90-01-01 00:00:46.874] P_MPSS_LSM lsm_loader.c:3500 TRACEH:OperationalReport from TFS [90-01-01 00:00:50.430] 0\RC_CO_RX_P co_rx_path.c:2016 TRACEH:### CO_RxPath ready for services ### [90-01-01 00:00:50.446] 0\RC_CO_TxP co_tx_path.c:343 TRACEH:### CO_TxPath ready for services ### [90-01-01 00:00:51.282] 1\RC_CO_RX_P co_rx_path.c:2016 TRACEH:### CO_RxPath ready for services ### [90-01-01 00:00:51.282] P_MPSS_LSM lsm_loader.c:3500 TRACEH:OperationalReport from RC [90-01-01 00:00:51.282] P_MPSS_LSM lsm_loader.c:3059 TRACEH:TraceH_Checkpoint: NodeStartState = PlatformOperational [90-01-01 00:00:51.282] P_MPSS_LSM lsm_loader.c:3063 TRACEH:TraceH_Checkpoint: NodeStartState = SystemOperational [90-01-01 00:00:51.298] 1\RC_CO_TxP co_tx_path.c:343 TRACEH:### CO_TxPath ready for services ### [90-01-01 00:00:51.742] P_MPSS_LSM lsm_loader.c:3117 TRACEH:TraceH_Checkpoint: NodeStartState = ReadyForRemoteMode [90-01-01 00:00:51.742] P_MPSS_LSM lsm_loader.c:3500 TRACEH:OperationalReport from TRXC [90-01-01 00:00:51.742] P_MPSS_HWDB_HNDL HardwareDB.c:2148 TRACEH:Fast restart allowed [90-01-01 00:00:51.786] O_TRXC_Main_1 TRXC1.c:10156 TRACEH:TRX-0 not 4WRD capable acc. to IDB [20-11-03 11:51:13.862] O_TRXC_Main_1 TRXC1.c:12338 TRACEH:InterfaceVersion = G12R13_INTERFACE_VERSION [20-11-03 11:51:13.868] P_MPSS_MMI_HNDL LED.c:963 TRACEH:MMI indication for LED_Local state OFF [20-11-03 11:51:32.086] 0\T_PCS_EXEC t_pcs_exec.cc:459 TRACEH:TIMING_REQ Error: result 3, current state 0 [20-11-03 11:51:33.086] 0\T_PCA t_pca_enable.cc:186 TRACEH:PCT START REQ timeout [20-11-03 11:51:33.086] 0\CO_TS t_tsam_co_ts.cc:2269 TRACEH:PCC enable NOT_OK [20-11-03 11:51:33.510] 0\T_PCS_EXEC t_pcs_exec.cc:459 TRACEH:TIMING_REQ Error: result 3, current state 0 [20-11-03 11:51:34.510] 0\T_PCA t_pca_enable.cc:186 TRACEH:PCT START REQ timeout [20-11-03 11:51:34.510] 0\CO_TS t_tsam_co_ts.cc:2269 TRACEH:PCC enable NOT_OK [20-11-03 11:51:34.930] 0\T_PCS_EXEC t_pcs_exec.cc:459 TRACEH:TIMING_REQ Error: result 3, current state 0 [20-11-03 11:51:35.930] 0\T_PCA t_pca_enable.cc:186 TRACEH:PCT START REQ timeout [20-11-03 11:51:35.930] 0\CO_TS t_tsam_co_ts.cc:2269 TRACEH:PCC enable NOT_OK [20-11-03 11:51:36.348] 0\T_PCS_EXEC t_pcs_exec.cc:459 TRACEH:TIMING_REQ Error: result 3, current state 0 [20-11-03 11:51:37.350] 0\T_PCA t_pca_enable.cc:186 TRACEH:PCT START REQ timeout [20-11-03 11:51:37.350] 0\CO_TS t_tsam_co_ts.cc:2269 TRACEH:PCC enable NOT_OK [20-11-03 11:51:37.768] 0\T_PCS_EXEC t_pcs_exec.cc:459 TRACEH:TIMING_REQ Error: result 3, current state 0 [20-11-03 11:51:38.768] 0\T_PCA t_pca_enable.cc:186 TRACEH:PCT START REQ timeout [20-11-03 11:51:38.768] 0\CO_TS t_tsam_co_ts.cc:2269 TRACEH:PCC enable NOT_OK [20-11-03 11:51:39.186] 0\T_PCS_EXEC t_pcs_exec.cc:459 TRACEH:TIMING_REQ Error: result 3, current state 0 [20-11-03 11:51:40.186] 0\T_PCA t_pca_enable.cc:186 TRACEH:PCT START REQ timeout [20-11-03 11:51:40.186] 0\CO_TS t_tsam_co_ts.cc:2269 TRACEH:PCC enable NOT_OK [20-11-03 11:51:40.604] 0\T_PCS_EXEC t_pcs_exec.cc:459 TRACEH:TIMING_REQ Error: result 3, current state 0 [20-11-03 11:51:41.588] 0\T_PCA t_pca_enable.cc:186 TRACEH:PCT START REQ timeout [20-11-03 11:51:41.588] 0\CO_TS t_tsam_co_ts.cc:2269 TRACEH:PCC enable NOT_OK [20-11-03 11:51:42.028] 0\T_PCS_EXEC t_pcs_exec.cc:459 TRACEH:TIMING_REQ Error: result 3, current state 0 [20-11-03 11:51:43.028] 0\T_PCA t_pca_enable.cc:186 TRACEH:PCT START REQ timeout [20-11-03 11:51:43.028] 0\CO_TS t_tsam_co_ts.cc:2269 TRACEH:PCC enable NOT_OK [20-11-03 12:09:23.468] P_MPSS_MMI_HNDL LED.c:963 TRACEH:MMI indication for LED_Local state FLASH [20-11-03 12:25:20.834] P_MPSK_RPA rpa.c:221 TRACEH:Poolsize 11533456 used 4145936 free 7387520 [20-11-03 12:25:20.834] P_MPSK_RPA rpa.c:226 TRACEH: Size 79 allocated 1573 freelist 70 [20-11-03 12:25:20.834] P_MPSK_RPA rpa.c:226 TRACEH: Size 143 allocated 98 freelist 30 [20-11-03 12:25:20.834] P_MPSK_RPA rpa.c:226 TRACEH: Size 303 allocated 311 freelist 50 [20-11-03 12:25:20.834] P_MPSK_RPA rpa.c:226 TRACEH: Size 527 allocated 181 freelist 4 [20-11-03 12:25:20.834] P_MPSK_RPA rpa.c:226 TRACEH: Size 2063 allocated 41 freelist 12 [20-11-03 12:25:20.834] P_MPSK_RPA rpa.c:226 TRACEH: Size 8207 allocated 84 freelist 0 [20-11-03 12:25:20.834] P_MPSK_RPA rpa.c:226 TRACEH: Size 16399 allocated 12 freelist 4 [20-11-03 12:25:20.834] P_MPSK_RPA rpa.c:226 TRACEH: Size 32783 allocated 8 freelist 4 [20-11-03 12:37:42.694] P_MPSK_RPA rpa.c:221 TRACEH:Poolsize 11533456 used 4162480 free 7370976 [20-11-03 12:37:42.694] P_MPSK_RPA rpa.c:226 TRACEH: Size 79 allocated 1581 freelist 62 [20-11-03 12:37:42.694] P_MPSK_RPA rpa.c:226 TRACEH: Size 143 allocated 97 freelist 31 [20-11-03 12:37:42.694] P_MPSK_RPA rpa.c:226 TRACEH: Size 303 allocated 311 freelist 50 [20-11-03 12:37:42.694] P_MPSK_RPA rpa.c:226 TRACEH: Size 527 allocated 181 freelist 4 [20-11-03 12:37:42.694] P_MPSK_RPA rpa.c:226 TRACEH: Size 2063 allocated 41 freelist 12 [20-11-03 12:37:42.694] P_MPSK_RPA rpa.c:226 TRACEH: Size 8207 allocated 84 freelist 2 [20-11-03 12:37:42.694] P_MPSK_RPA rpa.c:226 TRACEH: Size 16399 allocated 12 freelist 4 [20-11-03 12:37:42.694] P_MPSK_RPA rpa.c:226 TRACEH: Size 32783 allocated 8 freelist 4 -------------- next part -------------- A non-text attachment was scrubbed... Name: dsc1800.cfg Type: application/octet-stream Size: 2275 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: filtered_om200_rsl.pcap Type: application/octet-stream Size: 24685 bytes Desc: not available URL: From laforge at osmocom.org Wed Nov 11 09:14:09 2020 From: laforge at osmocom.org (Harald Welte) Date: Wed, 11 Nov 2020 10:14:09 +0100 Subject: Ericsson RBS-2206 startup with OSMO In-Reply-To: References: Message-ID: <20201111091409.GR1838861@nataraja> Hi Ivan, On Wed, Nov 11, 2020 at 01:26:01AM +0300, Ivan Babanov wrote: > After it we tried to use default config from master branch initially > created for RBS-2308. > It worked pretty fine except RF Power which was configured as 41dBm and 41 > - 12 = 29 dBm. Value 29 was not acceptable for our RBS. > I checked with Ericsson BSC Doc and found that our RBS2206 has max RF > output 47dBm for DCS1800. (btw, RBS2308 has only 34dBm max output according > to the same document, maybe config needs to be corrected) feel free to send a patch. > Looks like internal oscillator is not ready. So, the question is how to > make internal oscillator synchronized? Could it be an E1 Sync stability > issue caused by Digium cards? The question is not "could". Any BTS always needs a proper, stable reference clock. So unless your BTS has a built-in GPS clock refrence (and that reference is configured/enabled), your E1 will have to provide a stable clock reference. "stable" means (likely) fulfilling a clock stability that is _at the very least_ the stability of what commercial TDM/ISDN networks used to have. It doesn't hurt to have better stability. Any crystal oscillator on any E1/T1 peripheral card (digium or not) is by far not stable enough, possibly up to 1000 times worse than required. > 1. Set Digium card to get Sync from RBS. Now Digium is configured for > Internal clocking and acts as master. Maybe in case when both sides will be > configured to get sync from E1 it will decrease difference between internal > clock of RBS and E1 and RBS will get Synced state. And what would that get you to? In the end, a BTS that transmits at a frequency that will likely be so far off that you have serious problems connecting phones to it. > 2. Theoretically I can try to use Nokia DX200 BSC as a clock master for > Digium and deliver sync to RBS from Digium. I'm not sure if timing accuracy > is the same for Nokia and Ericsson HW. Sure, that should work. You can use any proper clock reference. One option I'm using here is to use a SIU-02. It has a 1PPS input for GPS, and it clocks up to 16 E1/T1 interfaces with that clock. You can then feed that clock signal to one port of your multi-port Digium card, and configure that as clock source, and the other ports will use that clock when talking to your BTSs. > One more question is where can I find some info about timing accuracy for > BTS and any possible way to check it on the existing E1 line? You would have to use some kind of test equipment that has a much more accurate/stable clock itself, like a rubidium oscillator or a GPS-DO. And then you can try to measure the Allan deviation/variance. But why do that? It's obvious that a normal crystal oscillator is way insufficient, no need to measure it. -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From ralph at schmid.xxx Thu Nov 12 10:33:21 2020 From: ralph at schmid.xxx (Ralph A. Schmid, dk5ras) Date: Thu, 12 Nov 2020 11:33:21 +0100 Subject: Ericsson RBS-2206 startup with OSMO In-Reply-To: <20201111091409.GR1838861@nataraja> References: <20201111091409.GR1838861@nataraja> Message-ID: <269501d6b8df$3e21f940$ba65ebc0$@schmid.xxx> Hi, > The question is not "could". Any BTS always needs a proper, stable reference > clock. So unless your BTS has a built-in GPS clock refrence (and that > reference is configured/enabled), your E1 will have to provide a stable clock > reference. How does the BTS judge if the clock satisfies its needs? Less sophisticated systems don't care and simply are unstable / off the frequency when the master clock is unstable / off-freq. The question is just because I am technically interested in the topic. Everyday there pops up some exciting stuff to learn out there :) Ralph. From 246tnt at gmail.com Thu Nov 12 10:44:33 2020 From: 246tnt at gmail.com (Sylvain Munaut) Date: Thu, 12 Nov 2020 11:44:33 +0100 Subject: Ericsson RBS-2206 startup with OSMO In-Reply-To: <269501d6b8df$3e21f940$ba65ebc0$@schmid.xxx> References: <20201111091409.GR1838861@nataraja> <269501d6b8df$3e21f940$ba65ebc0$@schmid.xxx> Message-ID: Hi, > How does the BTS judge if the clock satisfies its needs? Less sophisticated > systems don't care and simply are unstable / off the frequency when the > master clock is unstable / off-freq. The question is just because I am > technically interested in the topic. Everyday there pops up some exciting > stuff to learn out there :) I can't be 100% sure, but my understanding is it just compares to its internal OCXO. It know the margin of error of its OCXO, so if the incoming freq is more different than what it expects, Either the OCXO went bad or the incoming clock is bad. In either case, it's a fault. Cheers, Sylvain From ralph at schmid.xxx Thu Nov 12 10:47:49 2020 From: ralph at schmid.xxx (Ralph A. Schmid, dk5ras) Date: Thu, 12 Nov 2020 11:47:49 +0100 Subject: Ericsson RBS-2206 startup with OSMO In-Reply-To: References: <20201111091409.GR1838861@nataraja> <269501d6b8df$3e21f940$ba65ebc0$@schmid.xxx> Message-ID: <269901d6b8e1$43f6d2d0$cbe47870$@schmid.xxx> Hi, > I can't be 100% sure, but my understanding is it just compares to its internal > OCXO. > > It know the margin of error of its OCXO, so if the incoming freq is more > different than what it expects, Either the OCXO went bad or the incoming > clock is bad. In either case, it's a fault. OK, possibly less sophisticated than expected :) I have thought about some crazy jitter and drift detection... > Cheers, > > Sylvain Thanks! Ralph. From ivan.babanov at gmail.com Tue Nov 17 21:00:29 2020 From: ivan.babanov at gmail.com (Ivan Babanov) Date: Wed, 18 Nov 2020 00:00:29 +0300 Subject: Ericsson RBS-2206 startup with OSMO In-Reply-To: <20201111091409.GR1838861@nataraja> References: <20201111091409.GR1838861@nataraja> Message-ID: Hello Harald, Today I was able to achieve a state similar to your *.pcap file from here: https://osmocom.org/issues/4645 I see my RBS produces the pcap with the same data. I'm a bit worried about MO CONN which has DISABLED state and ERROR in RSL after sending 5ter to RBS. Is it possible to try calls in this state? I had no time today to connect Spectrum Analyser to RF output and check signal, and until next visit to the lab I hope that signal exists onAir :) At least I see that led "RF Off" is switched off now on dTRU. Regarding clock stability issue that I was describing in previous mail, I solved it by using CISCO 3640 with E1 card as the root for SYNC. My Digium card takes clock from CISCO and provides it to RBS. RBS looks happy with it. All other tricks I planned to try were unsuccessful. Setting both sides of E1 to get sync from the neighbour did not work as expected. When I tried with real BSC DX200, it looked like BSC was un-configured and was not able to bring E1 link up. So, my next steps are checking RF signal with analyser and trying to make a call with real UE. What do you think, is it possible? Thank you Babanov Ivan ??, 11 ????. 2020 ?. ? 12:14, Harald Welte : > Hi Ivan, > > On Wed, Nov 11, 2020 at 01:26:01AM +0300, Ivan Babanov wrote: > > After it we tried to use default config from master branch initially > > created for RBS-2308. > > It worked pretty fine except RF Power which was configured as 41dBm and > 41 > > - 12 = 29 dBm. Value 29 was not acceptable for our RBS. > > I checked with Ericsson BSC Doc and found that our RBS2206 has max RF > > output 47dBm for DCS1800. (btw, RBS2308 has only 34dBm max output > according > > to the same document, maybe config needs to be corrected) > > feel free to send a patch. > > > Looks like internal oscillator is not ready. So, the question is how to > > make internal oscillator synchronized? Could it be an E1 Sync stability > > issue caused by Digium cards? > > The question is not "could". Any BTS always needs a proper, stable > reference clock. So unless your BTS has a built-in GPS clock refrence > (and that > reference is configured/enabled), your E1 will have to provide a stable > clock > reference. > > "stable" means (likely) fulfilling a clock stability that is _at the very > least_ the > stability of what commercial TDM/ISDN networks used to have. It doesn't > hurt to have > better stability. > > Any crystal oscillator on any E1/T1 peripheral card (digium or not) is by > far not stable > enough, possibly up to 1000 times worse than required. > > > 1. Set Digium card to get Sync from RBS. Now Digium is configured for > > Internal clocking and acts as master. Maybe in case when both sides will > be > > configured to get sync from E1 it will decrease difference between > internal > > clock of RBS and E1 and RBS will get Synced state. > > And what would that get you to? In the end, a BTS that transmits at a > frequency that > will likely be so far off that you have serious problems connecting phones > to it. > > > 2. Theoretically I can try to use Nokia DX200 BSC as a clock master for > > Digium and deliver sync to RBS from Digium. I'm not sure if timing > accuracy > > is the same for Nokia and Ericsson HW. > > Sure, that should work. You can use any proper clock reference. One > option I'm using > here is to use a SIU-02. It has a 1PPS input for GPS, and it clocks up to > 16 E1/T1 > interfaces with that clock. You can then feed that clock signal to one > port of your > multi-port Digium card, and configure that as clock source, and the other > ports will > use that clock when talking to your BTSs. > > > One more question is where can I find some info about timing accuracy for > > BTS and any possible way to check it on the existing E1 line? > > You would have to use some kind of test equipment that has a much more > accurate/stable > clock itself, like a rubidium oscillator or a GPS-DO. And then you can > try to measure the Allan deviation/variance. But why do that? It's > obvious that a normal crystal oscillator is way insufficient, no need to > measure it. > > -- > - Harald Welte > http://laforge.gnumonks.org/ > > ============================================================================ > "Privacy in residential applications is a desirable marketing option." > (ETSI EN 300 175-7 Ch. > A6) > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mychaela.falconia at gmail.com Fri Nov 20 03:41:58 2020 From: mychaela.falconia at gmail.com (Mychaela Falconia) Date: Thu, 19 Nov 2020 19:41:58 -0800 Subject: Understanding GSM BTS Tx power levels Message-ID: Hello GSM network side community, I am doing some research in preparation for possibly setting up my own GSM/2G BTS in my rural town of Middle-of-Nowhere, California to serve as a replacement for our current GSM/2G service provided by T-Mobile USA, a contingency plan to be activated if and when the evil corporate owners of T-Mobile shut down their 2G service. I haven't bought my BTS hardware yet - I am still doing research and comparing options, and I also need to do some other preparatory work without which the BTS won't be of any use. I have a question about GSM BTS Tx power levels. Some BTS vendors advertise models with up to 10 W power output, but I don't understand how such high power output from a BTS can be useful when MS power output in the other direction is limited to 1 W in high bands or to 2 W in low bands. The whole point of a BTS is to provide service to subscribers, and in order for a subscriber to be able to make a call or to engage in a text conversation, there has to be two-way communication between the BTS and the MS: the MS needs to hear the downlink signal from the BTS, and the BTS needs to hear the uplink signal sent by the MS. If you have a BTS that puts out 10 W on the downlink, wouldn't the effective range be limited at the point where the BTS can no longer receive the 1 W (high bands) or 2 W (low bands) uplink put out by the MS? And if the range limit is set by the Tx power limit of standard GSM MS units, what is the point of having the BTS put out more power on the downlink than the very same 1 W or 2 W limit that applies to uplink Tx power? I can only reason that I must be missing something big here, as those BTS manufacturers who offer models with 10 W output surely make such hardware for some very valid use cases - but I would like to understand it better. Can someone perhaps explain this mystery to me? TIA, Mychaela From cleb at defcon-3.net Fri Nov 20 03:58:26 2020 From: cleb at defcon-3.net (Caleb Pal) Date: Thu, 19 Nov 2020 19:58:26 -0800 Subject: Understanding GSM BTS Tx power levels In-Reply-To: References: Message-ID: Good Evening, I'd look at a GSM link budget planning tool to get some ideas of where losses/gains are. Something like: https://home.zhaw.ch/~kunr/NTM1/tools/simplified_gsm_link_budget.xls The most influential factor is the MS has a 0dB gain omni antenna and is fairly deaf. The BTS is much more sensitive, with a high gain sector antenna (somewhere around 15-17dB gain). You may add diversity gain to the BTS RX as well. So the BTS has to pump the power out to reach the deaf MS on the downlink, but due to the BTS being more sensitive on RX, the small MS power is OK. Other factors on older BTS config (non-towertop) radios is coax line loss, especially at 1800/1900Mhz. More power needed to overcome line loss. Some have TMA's on the uplink side of the BTS to amplify the received MS signal before going down to the BTS radio. Hope that helps, c On 11/19/2020 19:41, Mychaela Falconia wrote: > Hello GSM network side community, > > I am doing some research in preparation for possibly setting up my own > GSM/2G BTS in my rural town of Middle-of-Nowhere, California to serve > as a replacement for our current GSM/2G service provided by T-Mobile > USA, a contingency plan to be activated if and when the evil corporate > owners of T-Mobile shut down their 2G service. I haven't bought my > BTS hardware yet - I am still doing research and comparing options, > and I also need to do some other preparatory work without which the > BTS won't be of any use. > > I have a question about GSM BTS Tx power levels. Some BTS vendors > advertise models with up to 10 W power output, but I don't understand > how such high power output from a BTS can be useful when MS power > output in the other direction is limited to 1 W in high bands or to > 2 W in low bands. The whole point of a BTS is to provide service to > subscribers, and in order for a subscriber to be able to make a call > or to engage in a text conversation, there has to be two-way > communication between the BTS and the MS: the MS needs to hear the > downlink signal from the BTS, and the BTS needs to hear the uplink > signal sent by the MS. If you have a BTS that puts out 10 W on the > downlink, wouldn't the effective range be limited at the point where > the BTS can no longer receive the 1 W (high bands) or 2 W (low bands) > uplink put out by the MS? And if the range limit is set by the Tx > power limit of standard GSM MS units, what is the point of having the > BTS put out more power on the downlink than the very same 1 W or 2 W > limit that applies to uplink Tx power? > > I can only reason that I must be missing something big here, as those > BTS manufacturers who offer models with 10 W output surely make such > hardware for some very valid use cases - but I would like to understand > it better. Can someone perhaps explain this mystery to me? > > TIA, > Mychaela From mychaela.falconia at gmail.com Fri Nov 20 05:25:46 2020 From: mychaela.falconia at gmail.com (Mychaela Falconia) Date: Thu, 19 Nov 2020 21:25:46 -0800 Subject: Understanding GSM BTS Tx power levels In-Reply-To: References: Message-ID: Hi Caleb, Thanks for the explanation regarding "proper" BTS setups having much more sensitive antennas for receiving uplink. In my case, I will be operating my BTS indoors inside my apartment (no tower), it will be a sort of clandestine operation squatting on an unused frequency *without* the usual billion dollar license, and the antennas hooked up to the Tx & Rx ports on the indoor BTS will be the ordinary omnidirectional kind. At first I was thinking about using the same kind of 5 cm antennas as these ones sold by Sysmocom: http://shop.sysmocom.de/products/ant-sma-quad I have a big bag of SPK ECL antennas similar to the above, except that mine are the straight version - I use them with all of my GSM MS development boards - but now that I think about it, there is another antenna which probably has higher gain which I can probably use for the BTS: https://www.sparkfun.com/products/8347 If I use either of the above, the Rx and Tx antennas on my BTS will probably be a little better than the internal antenna built into most cellphones, but it will be comparable to the MS antenna if the MS is one of my development boards. :) The two BTS models I am currently considering as my top choices are either the PCS band version of ip.access nanoBTS (used from ebay) or sysmoBTS 1002, and both of these seem to have the same maximum Tx power output of 23 dBm. Am I correct in assuming that if my BTS puts out 23 dBm, then I will hit my range limit when the MS stops being able to hear the BTS, before I hit the limit in the uplink direction? Any guesses as to what kind of range I should expect? I don't expect that my illegal BTS will ever serve any users other than just me - as I understand it, the total number of people *on the entire planet* who would voluntarily wish to use a 2G phone (as opposed to 5G/whatever) will never exceed maybe 10 users max planetwide, and I am pretty certain that right now I am the only active 2G user in all of California, if not in all of USA. As of today, T-Mobile USA still has active 2G service across all parts of California which I frequent these days - my travels nowadays are much less than pre-Covid, but I still occasionally drive as far south as downtown San Diego and as far north as almost hitting LA, and so far I have working service almost everywhere. But I can only reason that all those GSM cells must sit there 100% idle with exactly zero traffic almost all of the time, except during those brief moments when I happen to drive by that cell in my car - I don't see how it can be any other way when absolutely everyone else has standard sheeple 4G/5G phones. The only T-Mobile 2G cell that has nearly constant activity on it is the cell that serves my apartment, as that is where I stay 99% of the time in this Covid-driven reality. Thus I can only reason that T-Mobile USA currently maintains a GSM/2G network that has *only one active user* perhaps in the entire country, so it is understandable that they are threatening to shut it down. If they shut it down before I kick the bucket, I am thinking of setting up my own illegal BTS (on the very same ARFCN on which wrongfully- shutdown T-Mobile service used to be) inside my apartment, connected to a VoIP tunnel on the back end. It won't help me at times when I have to drive somewhere, but it would be neat if it can cover areas within walking distance of my apartment - the two grocery stores in our little rural town both happen to be within walking distance. Sorry for ranting, Mychaela From domi at tomcsanyi.net Fri Nov 20 08:18:18 2020 From: domi at tomcsanyi.net (=?UTF-8?Q?Tomcs=C3=A1nyi=2C_Domonkos?=) Date: Fri, 20 Nov 2020 09:18:18 +0100 Subject: Understanding GSM BTS Tx power levels In-Reply-To: References: Message-ID: Hi Mychaela, Your concerns are understandable given what happened e.g. in Australia earlier (they switched of 2G completely). However the current trend amongst operators seems to be keeping 2G and 4G while switching off 3G. 3G turned out to be the worst technology for carriers, because it does not have good coverage for simple voice calls and also it is quite cumbersome to operate while data rates are inadequate for today's subscribers. So this means 2G is kept for good coverage, basic voice service and 4G is kept for high data rates, assisting 5G in coverage etc. Some coverage about this in the news: https://www.vodafoneziggo.nl/en/verhalen/end-3g-era/ https://www.telekom.com/en/media/media-information/archive/bye-bye-3g-now-lte-is-coming-for-everyone-608220 Of course in the US the situation might be different because of frequency allocation differences, nevertheless I'd still place my bets on 2G staying with us for a long time. Naturally you are free to do whatever you wish, and having a BTS at home is great in many cases even if commercial service is available as well. I just wanted to chime in on the discussion about 2Gs possible future not trying to change your mind. I only have limited knowledge about BTS ranges, one time I tried to operate a BTS with an SDR board (USRP B200) and you could probably guess how bad it was :) - inaccurate clock, almost no TX power, resulting in a mighty 5m or ~6yards :). With a good clock source and an amplifier though I think even with an SDR one could have good ranges, however the burden of operating a complete PC just for handling the SDR makes buying a nano/sysmoBTS much more attractive. Kind regards, Domi On Fri, Nov 20, 2020 at 6:25 AM Mychaela Falconia wrote: > > Hi Caleb, > > Thanks for the explanation regarding "proper" BTS setups having much > more sensitive antennas for receiving uplink. > > In my case, I will be operating my BTS indoors inside my apartment (no > tower), it will be a sort of clandestine operation squatting on an > unused frequency *without* the usual billion dollar license, and the > antennas hooked up to the Tx & Rx ports on the indoor BTS will be the > ordinary omnidirectional kind. At first I was thinking about using > the same kind of 5 cm antennas as these ones sold by Sysmocom: > > http://shop.sysmocom.de/products/ant-sma-quad > > I have a big bag of SPK ECL antennas similar to the above, except that > mine are the straight version - I use them with all of my GSM MS > development boards - but now that I think about it, there is another > antenna which probably has higher gain which I can probably use for > the BTS: > > https://www.sparkfun.com/products/8347 > > If I use either of the above, the Rx and Tx antennas on my BTS will > probably be a little better than the internal antenna built into most > cellphones, but it will be comparable to the MS antenna if the MS is > one of my development boards. :) > > The two BTS models I am currently considering as my top choices are > either the PCS band version of ip.access nanoBTS (used from ebay) or > sysmoBTS 1002, and both of these seem to have the same maximum Tx > power output of 23 dBm. Am I correct in assuming that if my BTS puts > out 23 dBm, then I will hit my range limit when the MS stops being > able to hear the BTS, before I hit the limit in the uplink direction? > Any guesses as to what kind of range I should expect? > > I don't expect that my illegal BTS will ever serve any users other > than just me - as I understand it, the total number of people *on the > entire planet* who would voluntarily wish to use a 2G phone (as > opposed to 5G/whatever) will never exceed maybe 10 users max > planetwide, and I am pretty certain that right now I am the only > active 2G user in all of California, if not in all of USA. As of > today, T-Mobile USA still has active 2G service across all parts of > California which I frequent these days - my travels nowadays are much > less than pre-Covid, but I still occasionally drive as far south as > downtown San Diego and as far north as almost hitting LA, and so far I > have working service almost everywhere. But I can only reason that > all those GSM cells must sit there 100% idle with exactly zero traffic > almost all of the time, except during those brief moments when I > happen to drive by that cell in my car - I don't see how it can be any > other way when absolutely everyone else has standard sheeple 4G/5G > phones. The only T-Mobile 2G cell that has nearly constant activity > on it is the cell that serves my apartment, as that is where I stay > 99% of the time in this Covid-driven reality. > > Thus I can only reason that T-Mobile USA currently maintains a GSM/2G > network that has *only one active user* perhaps in the entire country, > so it is understandable that they are threatening to shut it down. If > they shut it down before I kick the bucket, I am thinking of setting > up my own illegal BTS (on the very same ARFCN on which wrongfully- > shutdown T-Mobile service used to be) inside my apartment, connected > to a VoIP tunnel on the back end. It won't help me at times when I > have to drive somewhere, but it would be neat if it can cover areas > within walking distance of my apartment - the two grocery stores in > our little rural town both happen to be within walking distance. > > Sorry for ranting, > Mychaela From mykola at kingmuffin.com Sun Nov 29 07:42:35 2020 From: mykola at kingmuffin.com (Mykola Shchetinin) Date: Sun, 29 Nov 2020 09:42:35 +0200 Subject: nano3g with genieACS In-Reply-To: <65ca2c74-99ea-a3ba-733d-0249c851bfbf@manateeshome.com> References: <65ca2c74-99ea-a3ba-733d-0249c851bfbf@manateeshome.com> Message-ID: Hello Pierre, > Hi, could you share your gist that you have posted earlier in the > following url? > > https://gist.github.com/efistokl/b95538772e54e5edb7765021c2b5a745#22-configuring-genieacs-to-use-a-specific-configuration-file I think the README.md of the repo https://github.com/Pentonet/pentonet-genieacs-package has the same contents as the gist you mentioned used to have. (I've just made the repo public) Also, the repository contains a package I used to set up my nano3g. I didn't document it at all though. Also, I think in the gist I didn't include these two fields: Device.Services.FAPService.1.CellConfig.UMTS.RAN.X_000295_DataOnFACHEnable = false (xsd:boolean) Device.Services.FAPService.1.CellConfig.UMTS.RAN.X_000295_FdEnabled = false (xsd:boolean) They are important for PS to work properly (as said by ip.access support). > I am trying to set up my nano3Gs once again and I remember reading this > awesome guide before, but when I visited the page today, sadly it was > not available anymore. Thanks, I am glad it was useful. Kind regards, Mykola From mariolucas75 at mail.ru Thu Nov 19 18:14:57 2020 From: mariolucas75 at mail.ru (=?UTF-8?B?TWFyaW8gTHVjYXM=?=) Date: Thu, 19 Nov 2020 21:14:57 +0300 Subject: =?UTF-8?B?T3Ntb2NvbSBDIGZpbGVzIHN5bnRheCB1bmRlcnN0YW5kaW5n?= Message-ID: <1605809697.574718486@f708.i.mail.ru> Dear openBSC society, ? Would you be so kind to advise me on the following: ? I desire (dramatically want very much) to learn / understand Osmocom projects. I am a beginner in programming and i try to understand / learn C files that the project is build of. ? As an example i tried to learn / understand for example an Osmocom message buffer ? msgb.h file. ? But immediately faced some syntax difficulties: ? This is the extract of msgb.h file: ? struct msgb { ?? ?struct llist_head list; /*!< \brief linked list header */ ?? ?/* Part of which TRX logical channel we were received / transmitted */ ?? ?/* FIXME: move them into the control buffer */ ?? ?union { ?? ??? ?void *dst; /*!< \brief reference of origin/destination */ ?? ??? ? struct gsm_bts_trx *trx; ?? ?}; ? As it can be seen a structure ?msgb? has as one of its components another structure ? ?gsm_bts_trx? ? But in whole Osmocom BB project files i could not find definition / description of struct ?gsm_bts_trx?. ? Would you kindly advise me please how to see which components / constituents / elements are in this gsm_bts_trx structure? From which components is struct gsm_bts_trx build of? ? Thank you so much for your kind advise. ? -- Mario Lucas -------------- next part -------------- An HTML attachment was scrubbed... URL: From laforge at osmocom.org Sat Nov 28 09:25:46 2020 From: laforge at osmocom.org (Harald Welte) Date: Sat, 28 Nov 2020 10:25:46 +0100 Subject: Humor of people involved in GSM standardization Message-ID: Dear Osmocom community, I'd like to share this with you, as I believe not many have read the book "GSM and UMTS; The Creation of Global Mobile Communications" by Friedhelm Hillebrand (who by the way just received the Order of Merit of the Federal Republic of Germany for his substantial contributions to mobile communications). The document (and some others on the included CD-ROM that comes with the book) reminds me to the much more widely known "Aprils Fool RFCs" within the IETF. It's a pity that ETSI - unlike IETF - didn't go through with it and hence those documents were never officially published, so that today only some fax scans seem to exist. Enjoy! -- - Harald Welte http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte -------------- next part -------------- A non-text attachment was scrubbed... Name: Fundamental requirements for Members and Documents.pdf Type: application/pdf Size: 499315 bytes Desc: not available URL: