baseband-devel

baseband-devel@lists.osmocom.org

2 participants
1984 discussions

how to run osmocom-bb with grgsm in usrp b210 to connect openBTS?

by hellowangfang＠gmail.com

I used osmocom-bb and grgsm with usrp b210 to connect openBTS, but failed. The command is "./mobile -c /home/oi/wf/osmocom-bb/doc/examples/mobile/default.cfg","./trxcon -p 5075 " ,"grgsm_trx -p 5075" . When i used “./cell_log -A 1 ”， it could find plmn 1-1 with arfcn 1 which is same with openBTS. DSUM INFO cell_log.c:344 Sync ARFCN 1 (rxlev -105, 1 syncs left) DSUM INFO cell_log.c:372 Measure from 1 to 1 DSUM INFO l1ctl.c:1177 start_pm L1CTL_PM_CONF DSUM INFO cell_log.c:400 start_pm S_L1CTL_PM_DONE DSUM INFO cell_log.c:363 Measurement done DSUM INFO cell_log.c:372 Measure from 1 to 1 DSUM INFO l1ctl.c:1177 start_pm L1CTL_PM_CONF DSUM INFO cell_log.c:400 start_pm S_L1CTL_PM_DONE DSUM INFO cell_log.c:363 Measurement done DSUM INFO cell_log.c:372 Measure from 1 to 1 DSUM INFO l1ctl.c:1177 start_pm L1CTL_PM_CONF DSUM INFO cell_log.c:400 start_pm S_L1CTL_PM_DONE DSUM INFO cell_log.c:363 Measurement done DSUM INFO cell_log.c:372 Measure from 1 to 1 DSUM INFO l1ctl.c:1177 start_pm L1CTL_PM_CONF DSUM INFO cell_log.c:400 start_pm S_L1CTL_PM_DONE DSUM INFO cell_log.c:363 Measurement done DSUM INFO cell_log.c:372 Measure from 1 to 1 DSUM INFO l1ctl.c:1177 start_pm L1CTL_PM_CONF DSUM INFO cell_log.c:400 start_pm S_L1CTL_PM_DONE DSUM INFO cell_log.c:363 Measurement done DSUM INFO cell_log.c:344 Sync ARFCN 1 (rxlev -105, 1 syncs left) DSUM INFO cell_log.c:190 Cell: ARFCN=1 MCC-MNC=001-01 (Test, Test) But when test with sim testcard 1, it failed to find the 1-1 cell. Could anyone give any suggestion about this? Thanks a lot! 6.5.0-25-generic #25~22.04.1-Ubuntu osmocom-bb: commit 0d1ab4c8d2cbe0ba72662d5b466fb6c60cb8b45f (HEAD -> master, origin/master, origin/HEAD) grgsm: https://github.com/bkerler/gr-gsm.git origin/maint-3.10_with_multiarfcn

1 year, 1 month

problem on registering osmocombb SDR PHY setup to my virtual bts

by daniollama＠gmail.com

I want to implement osmocombb SDR PHY project on USRP N210 in Dragon OS. for this purpose i setup Yate BTS with Blade RF in ARFCN 1. i test this bts by making call with two phone in this network. then i ran grgsm_scanner by USRP N210 and the log is >> Found CCCH arfcn: 1 Dont capture immediate assignments, skip extract SDCCH/8 info and scan... ARFCN: 1, Freq: 935.2M, CID: 10, LAC: 1000, MCC: 432, MNC: 35, Pwr: -27 |---- Configuration: 1 CCCH, combined |---- Cell ARFCNs: 0 |---- Neighbour Cells: 1, 2, 4, 6, 9, 10, 12, 14, 17, 18, 20, 22, 25, 33, 34, 35, 36, 38, 44, 46, 47, 48, 49, 50, 57, 58, 61, 63, 66, 69, 70, 71, 72, 75, 77, 78, 80, 82, 84, 90, 91, 92, 96, 97, 98, 99, 100, 101, 106, 107, 113, 115, 116, 118, 119, 121, 122 then i run grgsm_trx, trxcon and mobile with this configuration shown below ! ! OsmocomBB example configuration for mobile application !! ! line vty no login ! gps device /dev/ttyACM0 gps baudrate default no gps enable ! no hide-default ! ms 1 layer2-socket /tmp/osmocom_l2 sap-socket /tmp/osmocom_sap stick 1 sim none network-selection-mode auto imei 000000000000000 0 imei-fixed no emergency-imsi no sms-service-center no call-waiting no auto-answer no force-rekey no clip no clir tx-power auto no simulated-delay location-updating neighbour-measurement codec full-speed prefer codec half-speed no abbrev support sms a5/1 a5/2 p-gsm e-gsm r-gsm gsm-850 dcs no pcs class-900 4 class-850 4 class-dcs 1 class-pcs 1 channel-capability sdcch+tchf+tchh full-speech-v1 full-speech-v2 half-speech-v1 min-rxlev -60 dsc-max 90 no skip-max-per-band test-sim imsi 001010412345678 ki comp128 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 no barred-access rplmn 001 01 ! io-format ti no shutdown I enter commands OsmocomBB> en OsmocomBB# sim t OsmocomBB# sim testcard 1 in telnet. the log for grgsm_trx is Copyright (C) 2016-2018 by Vadim Yanitskiy <axilirator(a)gmail.com> Copyright (C) 2017-2018 by Piotr Krysik <ptrkrysik(a)gmail.com> License GPLv2+: GNU GPL version 2 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. [i] Init UHD Radio interface (L:0.0.0.0:6702 <-> R:127.0.0.1:6802) [INFO] [UHD] linux; GNU C++ version 11.3.0; Boost_107400; UHD_4.1.0.5-0-unknown [INFO] [USRP2] Opening a USRP2/N-Series device... [INFO] [USRP2] Current recv frame size: 1472 bytes [INFO] [USRP2] Current send frame size: 1472 bytes [i] Init CTRL interface (L:0.0.0.0:6701 <-> R:127.0.0.1:6801) [i] Init complete [i] Recv POWEROFF cmd [i] Resetting transceiver [i] Setting TA value 0 [i] Recv ECHO cmd [i] Recv POWEROFF cmd [i] Resetting transceiver [i] Setting TA value 0 [i] Recv ECHO cmd [i] Recv MEASURE cmd [i] Recv POWEROFF cmd [i] Resetting transceiver [i] Setting TA value 0 [i] Recv ECHO cmd [i] Recv SETSLOT cmd [i] Configure timeslot filter to: tn=0 [i] Recv RXTUNE cmd [i] Recv TXTUNE cmd [i] Recv POWERON CMD [i] Starting transceiver... [i] Recv POWEROFF cmd [i] Stopping transceiver... [i] Recv ECHO cmd [i] Recv SETSLOT cmd [i] Configure timeslot filter to: drop all . . . the log for texcon is 20240812161421520 DL1C NOTICE l1ctl.c:303 FBSB timer fired for ARFCN 1 20240812161421520 DL1C NOTICE l1ctl.c:422 Received reset request (1) 20240812161421520 DSCH NOTICE sched_trx.c:191 Reset scheduler and clock counter 20240812161421520 DSCH NOTICE sched_trx.c:237 Delete TDMA timeslot #0 20240812161421520 DL1C NOTICE l1ctl.c:395 Received power measurement request (GSM900: 1 -> 1) 20240812161421521 DL1C NOTICE l1ctl.c:422 Received reset request (1) 20240812161421521 DSCH NOTICE sched_trx.c:191 Reset scheduler and clock counter 20240812161421521 DL1C NOTICE l1ctl.c:338 Received FBSB request (GSM900 1) 20240812161421521 DSCH NOTICE sched_trx.c:191 Reset scheduler and clock counter 20240812161421521 DSCH NOTICE sched_trx.c:213 Add a new TDMA timeslot #0 20240812161421521 DSCH NOTICE sched_trx.c:288 (Re)configure TDMA timeslot #0 as BCCH+CCCH 20240812161421521 DSCH NOTICE sched_trx.c:445 Activating lchan=SCH on ts=0 20240812161421521 DSCH NOTICE sched_trx.c:445 Activating lchan=BCCH on ts=0 20240812161421521 DSCH NOTICE sched_trx.c:445 Activating lchan=RACH on ts=0 20240812161421521 DSCH NOTICE sched_trx.c:445 Activating lchan=CCCH on ts=0 20240812161421606 DSCHD ERROR sched_lchan_xcch.c:99 Received bad BCCH frame (rc=-1, ber=62/456) at fn=369446 20240812161421611 DSCHD NOTICE sched_trx.c:695 Substituting lost TDMA frame 369435 on CCCH 20240812161421611 DSCHD NOTICE sched_trx.c:695 Substituting lost TDMA frame 369436 on CCCH 20240812161421611 DSCHD NOTICE sched_trx.c:695 Substituting lost TDMA frame 369437 on CCCH 20240812161421611 DSCHD NOTICE sched_trx.c:695 Substituting lost TDMA frame 369438 on CCCH 20240812161421611 DSCHD ERROR sched_lchan_xcch.c:99 Received bad CCCH frame (rc=-1, ber=456/456) at fn=369435 20240812161421611 DSCHD NOTICE sched_trx.c:695 Substituting lost TDMA frame 369439 on CCCH 20240812161421611 DSCHD NOTICE sched_trx.c:695 Substituting lost TDMA frame 369440 on CCCH 20240812161421611 DSCHD NOTICE sched_trx.c:695 Substituting lost TDMA frame 369441 on CCCH 20240812161421611 DSCHD NOTICE sched_trx.c:695 Substituting lost TDMA frame 369442 on CCCH 20240812161421611 DSCHD ERROR sched_lchan_xcch.c:99 Received bad CCCH frame (rc=-1, ber=456/456) at fn=369439 20240812161421624 DSCHD ERROR sched_lchan_xcch.c:99 Received bad CCCH frame (rc=-1, ber=59/456) at fn=369450 20240812161421684 DSCHD NOTICE sched_trx.c:695 Substituting lost TDMA frame 369456 on CCCH 20240812161421684 DSCHD NOTICE sched_trx.c:695 Substituting lost TDMA frame 369457 on CCCH 20240812161421684 DSCHD NOTICE sched_trx.c:695 Substituting lost TDMA frame 369458 on CCCH 20240812161421684 DSCHD NOTICE sched_trx.c:695 Substituting lost TDMA frame 369459 on CCCH 20240812161421684 DSCHD ERROR sched_lchan_xcch.c:99 Received bad CCCH frame (rc=-1, ber=456/456) at fn=369456 20240812161421684 DSCHD NOTICE sched_trx.c:695 Substituting lost TDMA frame 369460 on CCCH 20240812161421684 DSCHD NOTICE sched_trx.c:695 Substituting lost TDMA frame 369461 on CCCH 20240812161421684 DSCHD NOTICE sched_trx.c:695 Substituting lost TDMA frame 369462 on CCCH 20240812161421684 DSCHD NOTICE sched_trx.c:695 Substituting lost TDMA frame 369463 on CCCH 20240812161421684 DSCHD ERROR sched_lchan_xcch.c:99 Received bad CCCH frame (rc=-1, ber=456/456) at fn=369460 20240812161421698 DSCHD ERROR sched_lchan_xcch.c:99 Received bad CCCH frame (rc=-1, ber=61/456) at fn=369466 20240812161421717 DSCHD ERROR sched_lchan_xcch.c:99 Received bad CCCH frame (rc=-1, ber=65/456) at fn=369470 20240812161421777 DSCHD NOTICE sched_trx.c:695 Substituting lost TDMA frame 369476 on CCCH 20240812161421777 DSCHD NOTICE sched_trx.c:695 Substituting lost TDMA frame 369477 on CCCH 20240812161421777 DSCHD NOTICE sched_trx.c:695 Substituting lost TDMA frame 369478 on CCCH 20240812161421777 DSCHD NOTICE sched_trx.c:695 Substituting lost TDMA frame 369479 on CCCH 20240812161421777 DSCHD ERROR sched_lchan_xcch.c:99 Received bad CCCH frame (rc=-1, ber=456/456) at fn=369476 20240812161421777 DSCHD NOTICE sched_trx.c:695 Substituting lost TDMA frame 369480 on CCCH 20240812161421777 DSCHD NOTICE sched_trx.c:695 Substituting lost TDMA frame 369481 on CCCH 20240812161421777 DSCHD NOTICE sched_trx.c:695 Substituting lost TDMA frame 369482 on CCCH 20240812161421777 DSCHD NOTICE sched_trx.c:695 Substituting lost TDMA frame 369483 on CCCH 20240812161421777 DSCHD ERROR sched_lchan_xcch.c:99 Received bad CCCH frame (rc=-1, ber=456/456) at fn=369480 20240812161421790 DSCHD ERROR sched_lchan_xcch.c:99 Received bad CCCH frame (rc=-1, ber=56/456) at fn=369486 20240812161421809 DSCHD ERROR sched_lchan_xcch.c:99 Received bad CCCH frame (rc=-1, ber=58/456) at fn=369490 20240812161421874 DSCHD NOTICE sched_trx.c:695 Substituting lost TDMA frame 369501 on CCCH 20240812161421874 DSCHD NOTICE sched_trx.c:695 Substituting lost TDMA frame 369502 on CCCH 20240812161421874 DSCHD NOTICE sched_trx.c:695 Substituting lost TDMA frame 369503 on CCCH 20240812161421874 DSCHD NOTICE sched_trx.c:695 Substituting lost TDMA frame 369504 on CCCH 20240812161421874 DSCHD ERROR sched_lchan_xcch.c:99 Received bad CCCH frame (rc=-1, ber=456/456) at fn=369501 20240812161421887 DSCHD ERROR sched_lchan_xcch.c:99 Received bad CCCH frame (rc=-1, ber=62/456) at fn=369507 20240812161421906 DSCHD ERROR sched_lchan_xcch.c:99 Received bad CCCH frame (rc=-1, ber=57/456) at fn=369511 20240812161421966 DSCHD NOTICE sched_trx.c:695 Substituting lost TDMA frame 369517 on CCCH 20240812161421966 DSCHD NOTICE sched_trx.c:695 Substituting lost TDMA frame 369518 on CCCH 20240812161421966 DSCHD NOTICE sched_trx.c:695 Substituting lost TDMA frame 369519 on CCCH 20240812161421966 DSCHD NOTICE sched_trx.c:695 Substituting lost TDMA frame 369520 on CCCH 20240812161421966 DSCHD ERROR sched_lchan_xcch.c:99 Received bad CCCH frame (rc=-1, ber=456/456) at fn=369517 20240812161421966 DSCHD NOTICE sched_trx.c:695 Substituting lost TDMA frame 369521 on CCCH 20240812161421966 DSCHD NOTICE sched_trx.c:695 Substituting lost TDMA frame 369522 on CCCH 20240812161421966 DSCHD NOTICE sched_trx.c:695 Substituting lost TDMA frame 369523 on CCCH 20240812161421966 DSCHD NOTICE sched_trx.c:695 Substituting lost TDMA frame 369524 on CCCH 20240812161421966 DSCHD ERROR sched_lchan_xcch.c:99 Received bad CCCH frame (rc=-1, ber=456/456) at fn=369521 20240812161421980 DSCHD ERROR sched_lchan_xcch.c:99 Received bad CCCH frame (rc=-1, ber=62/456) at fn=369527 and the log for mobile is <0003> gsm322.c:2919 Found signal (ARFCN 1 rxlev <=-110 (0)) <0003> gsm322.c:2933 Done with power scanning range. <0003> gsm322.c:2793 Scanning power for sticked cell. <0003> gsm322.c:2845 Found 1 frequencies. <0003> gsm322.c:2260 Scanning frequency 1 (rxlev <=-110). <0003> gsm322.c:479 Sync to ARFCN=1 rxlev=<=-110 (No sysinfo yet, ccch mode NONE) <0003> gsm322.c:2280 30 frequencies left in band 955..124 <000c> l1ctl.c:301 Dropping frame with 200 bit errors <000c> l1ctl.c:301 Dropping frame with 61 bit errors <000c> l1ctl.c:301 Dropping frame with 60 bit errors <000c> l1ctl.c:301 Dropping frame with 200 bit errors <000c> l1ctl.c:301 Dropping frame with 200 bit errors <000c> l1ctl.c:301 Dropping frame with 63 bit errors <000c> l1ctl.c:301 Dropping frame with 59 bit errors <000c> l1ctl.c:301 Dropping frame with 61 bit errors <000c> l1ctl.c:301 Dropping frame with 200 bit errors <000c> l1ctl.c:301 Dropping frame with 200 bit errors <000c> l1ctl.c:301 Dropping frame with 62 bit errors <000c> l1ctl.c:301 Dropping frame with 200 bit errors <000c> l1ctl.c:301 Dropping frame with 200 bit errors <000c> l1ctl.c:301 Dropping frame with 62 bit errors <000c> l1ctl.c:301 Dropping frame with 65 bit errors <000c> l1ctl.c:301 Dropping frame with 200 bit errors <000c> l1ctl.c:301 Dropping frame with 200 bit errors <000c> l1ctl.c:169 FBSB RESP: result=255 <0003> gsm322.c:3014 Channel sync error. <0003> gsm322.c:3019 free sysinfo ARFCN=1 <0003> gsm322.c:2748 Cell selection failed, sync timeout. <0003> gsm322.c:532 ARFCN |MCC |MNC |LAC |cell ID|forb.LA|prio |min-db |max-pwr|rx-lev <0003> gsm322.c:532 -------+-------+-------+-------+-------+-------+-------+-------+-------+------- <0003> gsm322.c:532 <0003> gsm322.c:2136 Cell search finished without result. <0003> gsm322.c:834 new state 'C6 any cell selection' -> 'C0 null' <0002> gsm322.c:3831 (ms 1) Event 'EVENT_NO_CELL_FOUND' for automatic PLMN selection in state 'A4 wait for PLMN to appear' <0003> gsm322.c:4062 (ms 1) Event 'EVENT_NO_CELL_FOUND' for Cell selection in state 'C0 null' <0003> gsm322.c:834 new state 'C0 null' -> 'C6 any cell selection' <0003> gsm322.c:2793 Scanning power for sticked cell. <0003> gsm322.c:2870 Scanning frequencies. (1..1) <0005> gsm48_mm.c:4308 (ms 1) Received 'MM_EVENT_NO_CELL_FOUND' event in state MM IDLE, no cell available <0005> gsm48_mm.c:4321 Message unhandled at this state. what should i do to connect mobile to my virtual bts? thanks.

1 year, 2 months

Re: osmocombb project does not work with any cable

by Craig Comstock

Hi there, You have to give these things some time. There are some good notes of expected behavior and bytes here: https://osmocom.org/projects/baseband/wiki/CompalRamloader -Craig On July 9, 2024 1:35:27 PM CDT, "حمۆدِيَ M" <jafar.jjjh63(a)gmail.com> wrote: >Hello . Please answer me, I have cp2102, FT232RL, and DSD TECH USB RS232 to >3.5mm Serial Cable with FTDI FT232RL Chip 6FT. >I have a conversion from 2.5mm to 3.5mm, but it does not work at all. But >in the cp2102 and FT232RL it works, but not completely, as it receives data >without sending the firmware download. What is the solution ? This is an >attached file that shows how to connect the phone with the CP2102 and >Ft232RL modules, and another picture showing what results appear to me. >Please reply to get the answer on how to send the firmware download >successfully! >For your information, I have 3 Motorola devices, C118, C115, and C139. They >all have the same result

1 year, 3 months

In search of broken Calypso phone

by Alexander Huemer

Hi I am on the hunt for a Calypso phone that isn't functional for whatever reason for the purpose of de-capping and photographing the Calypso/Iota/Rita ICs that a friendly individual would be able to do. This isn't something important, but the pictures would definitely be entertaining to look at. Of course somebody could donate a working phone to the cause, including myself, but a specimen that doesn't serve any other purpose anymore would be ideal. If you are in possession of such a phone, please let me know. Thanks, -Alex^Wblackbit

1 year, 4 months

How to add gdb info when build mobile and trx? Thank you!

by hellowangfang＠gmail.com

I used mobile, trx,grgsm,sdr to connect to openBTS, still failed. I want to use gdb to trace the internal info, how to enable gdb info when build them? Thank.

1 year, 6 months

Excel in NURS FPX 4010 Assessments with Our Expert Online Tutoring

by williammores96＠gmail.com

Excel in NURS FPX 4010 Assessments with Our Expert Online Tutoring Dominate your NURS FPX 4010 assessments with our specialized tutoring services. From Assessment 1 to 4, we provide comprehensive support to complete your nursing program with top grades. Start your success story today! Introduction to NURS FPX 4010 Series Assessments The NURS FPX 4010 series represents a significant milestone in the journey of nursing students. It challenges students to apply their knowledge in real-world scenarios, enhancing their clinical reasoning and decision-making skills. Whether you're just starting with NURS FPX 4010 Assessment 1 or gearing up for NURS FPX 4010 Assessment 4, each assessment is a step closer to achieving your academic and professional goals in nursing. Why Our Tutoring Services Are Essential for Your Success Navigating through the NURS FPX 4010 series requires more than just hard work; it demands strategic study plans and insights from experienced professionals. Our tutoring services are designed to guide you through each assessment, including NURS FPX 4010 Assessment 2 and NURS FPX 4010 Assessment 3, ensuring you grasp the core concepts and apply them effectively. Customized Learning for Maximum Impact We believe in a personalized approach to learning, recognizing that each student has unique strengths and challenges. Our tutors tailor their teaching methods to suit your individual needs, focusing on areas that require additional attention, such as NURS FPX 4010 Assessment 4, to maximize your learning outcome. Expert Tutors Ready to Assist You Our team comprises seasoned nursing educators who excel in their respective fields. They bring a wealth of knowledge and practical experience, providing invaluable insights into successfully completing assessments like NURS FPX 4010 Assessment 1. With our experts, you're not just preparing for an exam; you're gearing up for a successful career in nursing. Achieve Excellence in One Billing Cycle Our goal is to help you complete your BSN and MSN programs efficiently, without compromising the depth of learning. By focusing on crucial assessments, including NURS FPX 4010 Assessment 2 and NURS FPX 4010 Assessment 3, we streamline your study process to ensure you're exam-ready in the shortest possible time. Comprehensive Support Tailored to Your Needs From "Write my assessment" to "Online assessment help," we offer a range of services to support your academic journey. Our comprehensive tutoring package includes review sessions, practice questions, and personalized feedback, covering every aspect of the NURS FPX 4010 Assessment 4 and beyond. Your Partner in Nursing Education Choosing our tutoring services for the NURS FPX 4010 series is a step towards academic excellence and professional mastery. With our personalized support, expert guidance, and comprehensive resources, you'll be well-equipped to tackle each assessment with confidence and achieve your goals in the competitive field of nursing. Elevate your nursing education with our expert tutors. Contact us now to learn how we can help you excel in the NURS FPX 4010 series and advance your career with confidence.

1 year, 7 months

pycrate repo update

by benoit michau

Dear osmocom developpers, This is just to let you know that the Python library pycrate has a new home : https://github.com/pycrate-org/pycrate. The packages on Pypi are now feeded from there. This library can be used in many cases dealing with mobile signalling. I wanted to let you know, as even if I am not aware of any osmocom projects depending on it, some of you may use the library from time to time, or could have local applications depending on it. Best Regards Benoit

1 year, 7 months

Please Read and Support Compilation error in OSMOCOM BB

by Neeraj Chaudhary

Hello Team, I hope you are well and good . While I am doing the compilation of osmocom BB , There are errors as following , I committed the "Hello world" in the Makefile then there was another error and it kept coming one after another after I did the commit . Please note I have installed all the pre-requisites , GnuARM ToolChain and Libsomocomcore as directed in document . Also I have tried on both Ubuntu 20 and 22 but still the error keep coming . Please let me know for any know solutions for the same and also let me know if you need some more information from myside . Advance thanks for your support and all this good work . comm/timer.c: In function ‘timer_irq’: comm/timer.c:184: warning: unused parameter ‘irq’ AR comm/libcomm.a CC tiffs/globals.o CC tiffs/init.o CC tiffs/readfile.o AR tiffs/libtiffs.a LD board/compal_e88/hello_world.compalram.elf arm-elf-gcc: board/compal_e88/hello_world.compalram.map: No such file or directory make[1]: *** [Makefile.inc:139: board/compal_e88/hello_world.compalram.elf] Error 1 make[1]: Leaving directory '/home/lab3/osmocom-bb/src/target/firmware' make: *** [Makefile:100: firmware] Error 2 BR// Niraj Kumar

1 year, 7 months

Please Read and Support Compilation error in OSMOCOM BB

by Neeraj Chaudhary

Hello Team, I hope you are well and good . While I am doing the compilation of osmocom BB , There are errors as following , I committed the "Hello world" in the Makefile then there was another error and it kept coming one after another after I did the commit . Please note I have installed all the prerequisites , GnuARM ToolChain and Libsomocomcore as directed in document . Also I have tried on both Ubuntu 20 and 22 but still the error keep coming . Please let me know for any know solutions for the same and also let me know if you need some more information from myside . Advance thanks for your support and all this good work . comm/timer.c: In function ‘timer_irq’: comm/timer.c:184: warning: unused parameter ‘irq’ AR comm/libcomm.a CC tiffs/globals.o CC tiffs/init.o CC tiffs/readfile.o AR tiffs/libtiffs.a LD board/compal_e88/hello_world.compalram.elf arm-elf-gcc: board/compal_e88/hello_world.compalram.map: No such file or directory make[1]: *** [Makefile.inc:139: board/compal_e88/hello_world.compalram.elf] Error 1 make[1]: Leaving directory '/home/lab3/osmocom-bb/src/target/firmware' make: *** [Makefile:100: firmware] Error 2 BR// Niraj Kumar

1 year, 8 months

Does anyone from the community want the airprobe.org domain?

by Harald Welte

Hi all, I was approached by the person currently holding the [unused] airprobe.org domain name. I guess it was at some point registered and intended to be used for the project (back in the pre-osmocom days). As far as I know it was never actually used for that. So the question is now if anyone wants to get that domain transferred in order to do something useful with it, or whether the current registrant should simply let it expire? Regards, Harald -- - Harald Welte <laforge(a)osmocom.org> https://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

1 year, 8 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

baseband-devel