Hi Dave, Can you try putting a breakpoint in the ISR & swiConvertAnalogValuesFxn and see which breakpoint is hit first ? Also, is AtoD_ISR a regular Hwi or a zero-latency Hwi ? Best, Ashish
↧
Forum Post: RE: swi runs before posted
↧
Forum Post: RE: C6678 H264 encoder output shows artifacts with CBR
Hi Sudheesh, Thank you very much for the info. I'm doing high profile H.264 RTP streaming at 30 bps using CBR, and I'm forcing every 10th frame to IDR. This works with v1.0.1.4, although with some quality artifacts. v1.0.2.0 fixes the artifacts, but seems to ignoring some of the IDR frames, as my decoder sometimes is waiting a long time for SPS/PPS info. What other changes do I need to do? Is there any other configuration parameter other than forceFrame? Thank you, Harshal Patel HPC Systems Engineer Signalogic Inc.
↧
↧
Forum Post: RE: Undefined reference to ipc_gates and ipc_heaps
[quote user="Mike Stich"]I would gladly use the most recent version of all the tools, but I've been pretty confused as to what works with which device/bios/xdc/CCS versions. It has seemed to me that not all tool versions are backward compatible. I.e. new/old bios needs to be matched with new/old xdc[/quote] I've recently discovered that if you're using XDC 3.30 or higher then you need to use SYSBIOS 6.40 or higher, due to a change where platforms no longer come shipped with the XDC 3.30 "core" product and are instead shipped in SYSBIOS 6.40 (and higher). This would explain an issue that you mentioned in a previous post, where your CCS project's Platform: field on the RTSC tab didn't have a populated list of platforms. I ran into this issue when trying to use XDC 3.30 with SYSBIOS 6.37. As soon as I changed to use an XDC otherProcCtrl->recvInitStatus != NotifyDriverShm_INIT_STAMP) { /* * This may be used for polling till the other driver is ready, so * do not assert or error */ return (Notify_E_NOTINITIALIZED); } Regards, - Rob
↧
Forum Post: RE: How to use System_printf in tirtos_simplelink_2_11_00_03_eng
Hi Ashish, Sorry I forgot to mention my environment. The Compile is IAR 7.30.3 The Chip core is M3(this SOC is under NDA now so I can not mention chip name) My config is : var Defaults = xdc.useModule('xdc.runtime.Defaults'); var Types = xdc.useModule('xdc.runtime.Types'); var Diags = xdc.useModule('xdc.runtime.Diags'); var Error = xdc.useModule('xdc.runtime.Error'); var Main = xdc.useModule('xdc.runtime.Main'); var Memory = xdc.useModule('xdc.runtime.Memory') var SysCallback = xdc.useModule('xdc.runtime.SysCallback'); var System = xdc.useModule('xdc.runtime.System'); var Text = xdc.useModule('xdc.runtime.Text'); var HeapMem = xdc.useModule('ti. sysbios .heaps.HeapMem'); var Reset = xdc.useModule('xdc.runtime.Reset'); var BIOS = xdc.useModule('ti. sysbios .BIOS'); var Clock = xdc.useModule('ti. sysbios .knl.Clock'); var Task = xdc.useModule('ti. sysbios .knl.Task'); var Semaphore = xdc.useModule('ti. sysbios .knl.Semaphore'); var Hwi = xdc.useModule('ti. sysbios .hal.Hwi'); var M3Hwi = xdc.useModule('ti. sysbios .family.arm.m3.Hwi'); var Power = xdc.useModule('ti. sysbios .family.arm.cc26xx.Power'); /* Use the minimal user-supplied callback provider */ System.SupportProxy = SysCallback; /* no exit handlers needed */ System.maxAtexitHandlers = 0; and the app also has include /********************************************************************* * INCLUDES */ #include #include #include #include #include #include #include #include #include #include #include "bcomdef.h" #include "gatt.h" #include "ll.h" #include "hci.h" #include "gapgattserver.h" #include "gattservapp.h" #include "central.h" #include "gapbondmgr.h" #include "simpleGATTprofile.h" #include "osal_snv.h" #include "ICallBleAPIMSG.h" #include "util.h" #include "board_key.h" #include "board_lcd.h" #include "Board.h" #include #include "simpleBLECentral.h" but the System_printf has nothing out via uart0 Do I need define GPIO fun first or enable UART fun. Thanks
↧
Forum Post: RE: Use xdc tools to create the DEv.h header file
Hi George, If you dont mind I would like to understand why you need to modify DeviceParams structure ? In order to modify the structure, you would need to update the structure definition in ti/ sysbios /io/DEV.xdc file and rebuild the SYS/BIOS product (rebuilding the product will re-generate the DEV.h header file). For instructions on how to rebuild BIOS please refer "Rebuilding SYS/BIOS" chapter in the SYS/BIOS user guide. Best, Ashish
↧
↧
Forum Post: RE: C64+ Atomic Interrupt
Hi Geir, Are you building a SYS/BIOS (BIOS 6) or DSP/BIOS (BIOS 5) application ? I am guessing in order to register an interrupt for intNum 15, you are creating a Hwi ? When do you see the interrupt mask being set to all ? If you create an interrupt with disableMask set to all, then when this interrupt is serviced, it will disable all other interrupts (basically not allow nesting). The other interrupts will not be lost though. They will get executed once this interrupt is finished. Best, Ashish
↧
Forum Post: RE: TIVA Connect Launchpad with TI-RTOS semaphore problem
Hi Randall, You did not share the error you are getting so I am not sure what the problem is but I did a quick review of the code you shared and found a problem. I see that you are creating an instance of sReaderTask called sreader on the stack and passing a pointer to it as an argument to all the tasks. This is bad because the sreader object is on main's stack (also the system stack) and will be overwritten by the time SYS/BIOS starts up and the task function is called. You should either make sreader a global or malloc it. /* create tasks */ sReaderTask sreader; <------ created on main's stack sreader.pmailbox = &mailbox; sreader.psemaphore = &semaphore; Task_Params_init(&tskParams); tskParams.priority = 1; tskParams.arg0 = (UArg) &sreader; <------- pointer to a stack object Task_create(writer, &tskParams, NULL); Task_create(superVisor, &tskParams, NULL); Task_create(reader, &tskParams, NULL); Best, Ashish
↧
Forum Post: RE: UART TI RTOS driver problem tm4c123gh6pm tiva c
Hi Marinkovic, The first argument to UART_open() is suppose to be an index into the UART's HWAttrs table. The HWAttrs table may list more than one UARTs and the index tells UART_open() which one you want to open. The UART's HWAttrs table is defined in the board.c file. I have shown a screenshot of this structure below: Since you are new to TI-RTOS, I would recommend starting with an existing UART example. TI-RTOS ships with 3 UART examples - UART Console, UART Echo and UART Logging. You can import one of these through TI Resource Explorer in CCS. Best, Ashish
↧
Forum Post: RE: How to use System_printf in tirtos_simplelink_2_11_00_03_eng
Hi Now I do this like below: in appBLE.cfg var SysCallback = xdc.useModule('xdc.runtime.SysCallback'); var SysStd = xdc.useModule('xdc.runtime.SysStd'); var System = xdc.useModule('xdc.runtime.System'); /* Use the minimal user-supplied callback provider */ System.SupportProxy = SysStd; in app #include void func (void){ ..... System_printf("Printf Fun Ok"); } But IAR build project show the error message no definition for "__dwrite"[referenced from xxwritebuffered.o(dl7M_tln.a)] Error while running Linker So the problem is about setting IAR compile or xxx.cfg Thanks
↧
↧
Forum Post: RE: swi runs before posted
Thanks Ashish, As you suggested I put a breakpoint in the ADC_FIFO_Full_ISR & in swiConvertAnalogValuesFxn. The ADC_FIFO_Full_ISR runs first. I commented out "ADCProcessorTrigger(ADC0_BASE, 0);" in the clock ISR routine BUT the ADC_FIFO_Full_ISR routine STILL runs! and stops at the breakpoint. How can an ISR execute when there is no interrupt? Can an irq flag persist from one debug run to the next? In case that's true I'm going to try specifically disabling "ADC0 Sequence 0" interrupt (30) before BIOS_start(); and let u know results. Ah Ha! As it turns out: my ADC initialization routine was enabling ADC interrupts like this: ADCIntEnable(ADC0_BASE, 0); IntEnable(INT_ADC0SS0); when i commented out... ADCIntEnable(ADC0_BASE, 0); // IntEnable(INT_ADC0SS0); the desired/expected behavior ensued. whew! About "regular Hwi and zero-latency Hwi" I did not know there were two types of interrupt. If you point me at the info i will look it up. I appreciate your help, Cheers, Dave
↧
Forum Post: RE: am335x_evm and sdk ver 07.00 having problems
Hi Ivan, Yes. I agree too. In fact I wondered why the .dtb file is not being loaded. That is one of the doubts I thought of asking you. Can you please share your include/configs/am335x_evm.h config file. Ok. I'll try with another memory card and let you know the result. Please share the am335x_evm.h file meanwhile. Thank u for your patience. :) Regards, Vijaykumar.
↧
Forum Post: RE: How to use System_printf in tirtos_simplelink_2_11_00_03_eng
Hi it is me again, now I do this document "TI-RTOS 2.10 User’s Guide" UART driver chapt.... UART_Params_init(¶ms); //params.baudRate = someNewBaudRate; params.baudRate = 115200; params.parityType = UART_PAR_NONE; params.dataLength = UART_LEN_8; params.stopBits = UART_STOP_ONE; params.writeDataMode = UART_DATA_BINARY; params.readDataMode = UART_DATA_BINARY; params.readReturnMode = UART_RETURN_FULL; params.readEcho = UART_ECHO_OFF; handle = UART_open(Board_UART, ¶ms); //<=======This line does work if (!handle) { System_printf("UART did not open"); } uint8_t str[] = "SimpleBLECentral_init Dome\r\n"; UART_write(handle, str, sizeof(str)); //<===============This line does work too System_printf("Printf Fun========================== Ok");//<=========but this System_printf also does not work........why? System_flush();
↧
Forum Post: RE: Use xdc tools to create the DEv.h header file
Thank you for the aswer. It was a wrong approach when we tried to change SIO with GIO .In any case I tries this that is described in section rebuilt bios but the new DEV.h was not generated. Best regards George
↧
↧
Forum Post: SPI driver C6748
Hi, Whether it is possible to use SPI driver from C6748 BIOS PSP for data acquisition from the device which forms a ready about the new data? That is in the device after each sample cycle, the sensor data loads into the output registers and pulses, providing a new data ready control signal for driving system-level interrupt service routines. What program design can be used for this purpose? Whether it is possible to use procedure GIO_write(spiHandle, &dataparam, &size) in HWI DSP/BIOS? Thanks.
↧
Forum Post: RE: C6678 H264 encoder output shows artifacts with CBR
Hi Harshal, Since your IDR insertion is not random (forceframe feature may not be required), you can do that as shown below: intraFrameInterval = 10; IDRFrameInterval = 1; Regards Sudheesh
↧
Forum Post: How to modify _c_int00 startup code of SYS/BIOS boot module?
Hi I am using Sys/Bios with Tiva uC Before my software starts, I need to execute RAM pattern test for entire memory for that reason I cannot just simply register to one of startup hook function pointers because this code is using stack already (wheres my RAM test overwrites entire memory) In linker map file I see that _c_int00 startup code is located in boot.oem4f module and it seems, that is different code than boot.asm delivered with standard library. So my question is how can I modify boot.oem4f _c_int00 startup code to meet my needs, it is possible at all when using Sys/Bios? My configuration: Tiva TM4c129encpdt Sys/Bios: 6.37.4.32 XDC tools: 3.25.6.96 CGT: 5.010 Gregor
↧
Forum Post: RE: [DM385-H.264]flickering in right end of image at very low-bitrate
Hi folks, I have set the input and output resolution on the H.264 encoder to 2032x1536. My understanding is that this resolution will not require the MegaPixel encoding element to be enabled. However, I am still seeing flickering at the right hand side of the image. Is there a maximum resolution that can be encoded without enabling the MegaPixel encoding element and will not result in flickering at the right hand side of the image? The H.264 encoder version that I am using is version 2.00.02.02. Thanks in advance, Terry
↧
↧
Forum Post: SecondsClock usage
TIRTOS on a TM4C123GH6PGE . tirtos_tivac_2_10_01_38 Code Composer Studio Version: 6.0.1.00040 From the cfg file: var SecondsClock = xdc.useModule('ti. sysbios .hal.SecondsClock'); From this users guide "SYS/BIOS (TI-RTOS Kernel) v6.41" it appears I can use SecondsClock to keep calendar time on my system. However when compiling this error is generated: Undefined reference to 'ti_ sysbios _hal_Seconds_get__E' in file ./main.obj .xdchelp /WM24 TIRTOS C/C++ Problem The compiler suggests this a fix: var ti_ sysbios _hal_Seconds = xdc.useModule('ti. sysbios .hal.Seconds'); Adding this to the project lets the program compile, but the unit lockups in Seconds_set at the clock enable bit. Understandable because this hardware is not used on this unit. Void Seconds_set(UInt32 seconds) { UInt32 curSeconds; /* Turn on the clock enable bit. */ HWREG(HIB_CTL) |= HIB_CTL_CLK32EN; The question is how do you get it to compile and use an increment from the clock module like mentioned in the TIRTOS user's guide?
↧
Forum Post: RE: How to use System_printf in tirtos_simplelink_2_11_00_03_eng
I find the problem is in IAR Arm compile does not support System_printf. So I am going to find the How to define the "__dwrite" in IAR.
↧
Forum Post: RE: Beagleboard with USB OTG
Hello Bin Liu, It seems that it works, but only partly. It has some disconnections every several seconds, and after such disconnect I need to set the ip again, and only then can check ping with PC. Do you find any problem in the attched log below ? root@beagleboard:~# root@beagleboard:~# ifconfig lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:6 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:672 (672.0 B) TX bytes:672 (672.0 B) usb0 Link encap:Ethernet HWaddr 36:19:CA:A6:B0:B2 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:258 errors:0 dropped:12 overruns:0 frame:0 TX packets:10 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:21820 (21.3 KiB) TX bytes:2828 (2.7 KiB) root@beagleboard:~# [ 141.243835] dhclient[340]: DHCPDISCOVER on usb0 to 255.255.255.255 port 67 interval 6 [ 141.252990] NetworkManager[132]: DHCPDISCOVER on usb0 to 255.255.255.255 port 67 interval 6 ifconfig usb0 10.0.0.20 [ 145.770416] avahi-daemon[143]: root@beagleboardJoining mDNS multicast group on interface usb0.IPv4 with address 10.0.0.20.:~# [ 145.785308] avahi-daemon[143]: New relevant interface usb0.IPv4 for mDNS. [ 145.792846] avahi-daemon[143]: Registering new address record for 10.0.0.20 on usb0.IPv4. ifconfig usb0 10.0.0.20[ 147.258056] dhclient[340]: DHCPDISCOVER on usb0 to 255.255.255.255 port 67 interval 13 [ 147.268096] NetworkManager[132]: DHCPDISCOVER on usb0 to 255.255.255.255 port 67 interval 13 ping 10.0.0.17 PING 10.0.0.17 (10.0.0.17): 56 data bytes 64 bytes from 10.0.0.17: seq=0 ttl=128 time=4.558 ms 64 bytes from 10.0.0.17: seq=1 ttl=128 time=0.681 ms 64 bytes from 10.0.0.17: seq=2 ttl=128 time=0.545 ms 64 bytes from 10.0.0.17: seq=3 ttl=128 time=0.626 ms 64 bytes from 10.0.0.17: seq=4 ttl=128 time=0.682 ms 64 bytes from 10.0.0.17: seq=5 ttl=128 time=0.484 ms 64 bytes from 10.0.0.17: seq=6 ttl=128 time=0.682 ms 64 bytes from 10.0.0.17: seq=7 ttl=128 time=0.699 ms 64 bytes from 10.0.0.17: seq=8 ttl=128 time=0.569 ms 64 bytes from 10.0.0.17: seq=9 ttl=128 time=0.602 ms 64 bytes from 10.0.0.17: seq=10 ttl=128 time=0.664 ms [ 160.271301] dhclient[340]: DHCPDISCOVER on usb0 to 255.255.255.255 port 67 interval 9 [ 160.280273] NetworkManager[132]: DHCPDISCOVER on usb0 to 255.255.255.255 port 67 interval 9 64 bytes from 10.0.0.17: seq=11 ttl=128 time=0.716 ms 64 bytes from 10.0.0.17: seq=12 ttl=128 time=0.654 ms 64 bytes from 10.0.0.17: seq=13 ttl=128 time=0.585 ms 64 bytes from 10.0.0.17: seq=14 ttl=128 time=0.658 ms 64 bytes from 10.0.0.17: seq=15 ttl=128 time=0.657 ms 64 bytes from 10.0.0.17: seq=16 ttl=128 time=0.507 ms 64 bytes from 10.0.0.17: seq=17 ttl=128 time=0.650 ms 64 bytes from 10.0.0.17: seq=18 ttl=128 time=0.657 ms 64 bytes from 10.0.0.17: seq=19 ttl=128 time=0.664 ms [ 169.280670] dhclient[340]: DHCPDISCOVER on usb0 to 255.255.255.255 port 67 interval 13 [ 169.289825] NetworkManager[132]: DHCPDISCOVER on usb0 to 255.255.255.255 port 67 interval 13 64 bytes from 10.0.0.17: seq=20 ttl=128 time=0.750 ms 64 bytes from 10.0.0.17: seq=21 ttl=128 time=0.645 ms 64 bytes from 10.0.0.17: seq=22 ttl=128 time=0.509 ms 64 bytes from 10.0.0.17: seq=23 ttl=128 time=0.652 ms 64 bytes from 10.0.0.17: seq=24 ttl=128 time=0.661 ms 64 bytes from 10.0.0.17: seq=25 ttl=128 time=0.614 ms 64 bytes from 10.0.0.17: seq=26 ttl=128 time=0.605 ms [ 175.687316] NetworkManager[132]: (usb0): DHCPv4 request timed out. [ 175.696746] NetworkManager[132]: NetworkManager[132]: (usb0): DHCPv4 request timed out. [ 175.890899] NetworkManager[132]: (usb0): canceled DHCP transaction, DHCP client pid 340 [ 175.900848] NetworkManager[132]: Activation (usb0) Stage 4 of 5 (IP4 Configure Timeout) scheduled... [ 175.911895] NetworkManager[132]: Activation (usb0) Stage 4 of 5 (IP4 Configure Timeout) started... [ 175.924743] NetworkManager[132]: Activation (usb0) Stage 5 of 5 (IP Configure Commit) scheduled... [ 175.935516] NetworkManager[132]: Activation (usb0) Stage 4 of 5 (IP4 Configure Timeout) complete. [ 175.946166] NetworkManager[132]: NetworkManager[132]: (usb0): canceled DHCP transaction, DHCP client pid 340 [ 175.957763] NetworkManager[132]: NetworkManager[132]: Activation (usb0) Stage 4 of 5 (IP4 Configure Timeout) scheduled... [ 175.972564] NetworkManager[132]: NetworkManager[132]: Activation (usb0) Stage 4 of 5 (IP4 Configure Timeout) started... [ 175.985260] NetworkManager[132]: NetworkManager[132]: Activation (usb0) Stage 5 of 5 (IP Configure Commit) scheduled... [ 175.997924] NetworkManager[132]: NetworkManager[132]: Activation (usb0) Stage 4 of 5 (IP4 Configure Timeout) complete. [ 176.010406] NetworkManager[132]: NetworkManager[132]: Activation (usb0) Stage 5 of 5 (IP Configure Commit) started... [ 176.026794] NetworkManager[132]: Activation (usb0) Stage 5 of 5 (IP Configure Commit) started... [ 176.039611] NetworkManager[132]: NetworkManager[132]: Activation (usb0) Stage 5 of 5 (IP Configure Commit) failed (no IP configuration found) [ 176.054565] NetworkManager[132]: Activation (usb0) Stage 5 of 5 (IP Configure Commit) failed (no IP configuration found) [ 176.067382] NetworkManager[132]: (usb0): device state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5] [ 176.081024] NetworkManager[132]: NetworkManager[132]: (usb0): device state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5] [ 176.095947] NetworkManager[132]: Activation (usb0) failed. [ 176.102752] NetworkManager[132]: NetworkManager[132]: Activation (usb0) failed. [ 176.111511] NetworkManager[132]: Activation (usb0) Stage 5 of 5 (IP Configure Commit) complete. [ 176.121734] NetworkManager[132]: NetworkManager[132]: Activation (usb0) Stage 5 of 5 (IP Configure Commit) complete. [ 176.133880] NetworkManager[132]: (usb0): device state change: failed -> disconnected (reason 'none') [120 30 0] [ 176.145538] NetworkManager[132]: NetworkManager[132]: (usb0): device state change: failed -> disconnected (reason 'none') [120 30 0] [ 176.159118] NetworkManager[132]: (usb0): deactivating device (reason 'none') [0] [ 176.168151] NetworkManager[132]: NetworkManager[132]: (usb0): deactivating device (reason 'none') [0] [ 176.178894] avahi-daemon[143]: Withdrawing address record for 10.0.0.20 on usb0. [ 176.187103] avahi-daemon[143]: Leaving mDNS multicast group on interface usb0.IPv4 with address 10.0.0.20. [ 176.197692] avahi-daemon[143]: Interface usb0.IPv4 no longer relevant for mDNS. ping: sendto: Network is unreachable root@beagleboard:~# [ 178.687561] NetworkManager[132]: Auto-activating connection 'Wired connection 1'. [ 178.702331] NetworkManager[132]: Activation (usb0) starting connection 'Wired connection 1' [ 178.712951] NetworkManager[132]: (usb0): device state change: disconnected -> prepare (reason 'none') [30 40 0] [ 178.724975] NetworkManager[132]: NetworkManager[132]: Auto-activating connection 'Wired connection 1'. [ 178.736145] NetworkManager[132]: NetworkManager[132]: Activation (usb0) starting connection 'Wired connection 1' [ 178.750030] NetworkManager[132]: NetworkManager[132]: (usb0): device state change: disconnected -> prepare (reason 'none') [30 40 0] [ 178.764343] NetworkManager[132]: NetworkManager[132]: Activation (usb0) Stage 1 of 5 (Device Prepare) scheduled... [ 178.776824] NetworkManager[132]: Activation (usb0) Stage 1 of 5 (Device Prepare) scheduled... [ 178.787170] NetworkManager[132]: NetworkManager[132]: Activation (usb0) Stage 1 of 5 (Device Prepare) started... [ 178.799346] NetworkManager[132]: Activation (usb0) Stage 1 of 5 (Device Prepare) started... [ 178.809600] NetworkManager[132]: NetworkManager[132]: Activation (usb0) Stage 2 of 5 (Device Configure) scheduled... [ 178.823333] NetworkManager[132]: Activation (usb0) Stage 2 of 5 (Device Configure) scheduled... [ 178.833953] NetworkManager[132]: NetworkManager[132]: Activation (usb0) Stage 1 of 5 (Device Prepare) complete. [ 178.845977] NetworkManager[132]: Activation (usb0) Stage 1 of 5 (Device Prepare) complete. [ 178.856079] NetworkManager[132]: Activation (usb0) Stage 2 of 5 (Device Configure) starting... [ 178.868865] NetworkManager[132]: NetworkManager[132]: Activation (usb0) Stage 2 of 5 (Device Configure) starting... [ 178.881317] NetworkManager[132]: (usb0): device state change: prepare -> config (reason 'none') [40 50 0] [ 178.895477] NetworkManager[132]: NetworkManager[132]: (usb0): device state change: prepare -> config (reason 'none') [40 50 0] [ 178.923431] NetworkManager[132]: Activation (usb0) Stage 2 of 5 (Device Configure) successful. [ 178.943969] NetworkManager[132]: NetworkManager[132]: Activation (usb0) Stage 2 of 5 (Device Configure) successful. [ 178.973449] NetworkManager[132]: Activation (usb0) Stage 3 of 5 (IP Configure Start) scheduled. [ 178.990295] NetworkManager[132]: NetworkManager[132]: Activation (usb0) Stage 3 of 5 (IP Configure Start) scheduled. [ 179.002838] NetworkManager[132]: Activation (usb0) Stage 2 of 5 (Device Configure) complete. [ 179.013427] NetworkManager[132]: NetworkManager[132]: Activation (usb0) Stage 2 of 5 (Device Configure) complete. [ 179.025634] NetworkManager[132]: Activation (usb0) Stage 3 of 5 (IP Configure Start) started... [ 179.036224] NetworkManager[132]: NetworkManager[132]: Activation (usb0) Stage 3 of 5 (IP Configure Start) started... [ 179.048706] NetworkManager[132]: (usb0): device state change: config -> ip-config (reason 'none') [50 70 0] [ 179.060333] NetworkManager[132]: NetworkManager[132]: (usb0): device state change: config -> ip-config (reason 'none') [50 70 0] [ 179.073944] NetworkManager[132]: Activation (usb0) Beginning DHCPv4 transaction (timeout in 45 seconds) [ 179.085174] NetworkManager[132]: NetworkManager[132]: Activation (usb0) Beginning DHCPv4 transaction (timeout in 45 seconds) [ 179.100494] NetworkManager[132]: dhclient started with pid 348 [ 179.108001] NetworkManager[132]: NetworkManager[132]: dhclient started with pid 348 [ 179.118896] NetworkManager[132]: Activation (usb0) Stage 3 of 5 (IP Configure Start) complete. [ 179.140502] NetworkManager[132]: NetworkManager[132]: Activation (usb0) Stage 3 of 5 (IP Configure Start) complete. [ 179.189056] dhclient[348]: Internet Systems Consortium DHCP Client 4.2.0 [ 179.198425] dhclient[348]: Copyright 2004-2010 Internet Systems Consortium. [ 179.207031] NetworkManager[132]: Internet Systems Consortium DHCP Client 4.2.0 [ 179.215759] dhclient[348]: All rights reserved. [ 179.221405] NetworkManager[132]: Copyright 2004-2010 Internet Systems Consortium. [ 179.231109] dhclient[348]: For info, please visit https://www.isc.org/software/dhcp/ [ 179.240264] NetworkManager[132]: All rights reserved. [ 179.246887] NetworkManager[132]: For info, please visit https://www.isc.org/software/dhcp/ [ 179.256347] dhclient[348]: can't create /var/lib/dhcp/dhclient-0c0c5428-c126-43cf-8afe-4c6c853eff49-usb0.lease: No such file or directory [ 179.269897] NetworkManager[132]: can't create /var/lib/dhcp/dhclient-0c0c5428-c126-43cf-8afe-4c6c853eff49-usb0.lease: No such file or directory [ 179.283996] NetworkManager[132]: NetworkManager[132]: (usb0): DHCPv4 state changed nbi -> preinit [ 179.294647] NetworkManager[132]: (usb0): DHCPv4 state changed nbi -> preinit [ 179.303375] dhclient[348]: Listening on LPF/usb0/36:19:ca:a6:b0:b2 [ 179.310516] dhclient[348]: Sending on LPF/usb0/36:19:ca:a6:b0:b2 [ 179.317657] NetworkManager[132]: Listening on LPF/usb0/36:19:ca:a6:b0:b2 [ 179.325256] dhclient[348]: Sending on Socket/fallback [ 179.331268] NetworkManager[132]: Sending on LPF/usb0/36:19:ca:a6:b0:b2 [ 179.339019] dhclient[348]: DHCPDISCOVER on usb0 to 255.255.255.255 port 67 interval 4 [ 179.347930] NetworkManager[132]: Sending on Socket/fallback [ 179.354583] NetworkManager[132]: DHCPDISCOVER on usb0 to 255.255.255.255 port 67 interval 4 root@beagleboard:~# root@beagleboard:~# [ 183.251190] dhclient[348]: DHCPDISCOVER on usb0 to 255.255.255.255 port 67 interval 10 [ 183.260375] NetworkManager[132]: DHCPDISCOVER on usb0 to 255.255.255.255 port 67 interval 10 root@beagleboard:~# ifconfig lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:6 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:672 (672.0 B) TX bytes:672 (672.0 B) usb0 Link encap:Ethernet HWaddr 36:19:CA:A6:B0:B2 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:377 errors:0 dropped:13 overruns:0 frame:0 TX packets:58 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:30429 (29.7 KiB) TX bytes:13694 (13.3 KiB) Regards, Ran
↧