Part Number:CC2640

Tool/software: Code Composer Studio

We are using CC2640 in our project. We successfully compiled the BLE stack in CCS with "FlashROM" configuration. 
We have also successfully compiled the application code in CCS with "FlashOnly_OAD" configuration. 

We have programmed the target via JTAG port through XDS110 debug probe. The application is working fine as long as power is there and JTAG cable is plugged-in.
When we power-down and restart without JTAG cable, the application is NOT running with newly flashed binary. 

1) How to flash the binary permanently into internal flash of CC2640 via JTAG port through XDS110 debug probe?. 

2) Is "FlashOnly_OAD" compiling configuration for application used for one time programming of CC2640 in debug mode and not flashing the binary permanently into internal flash?.

3) There are some E2E links which talks about building OAD image-B with "FlashOnly_OAD_ImgB". We are only seeing "FlashOnly_OAD" in our CCS and NOT seeing "FlashOnly_OAD_ImgB". Is this the reason for not flashing permanently into flash?.

Please give us some directions to resolve this issue.

Best regards,
Prabhakar

Part Number:CC1352P

Tool/software: TI-RTOS

Hello,

I'm working with CC1352 PG2.1 assmembled into my own design.

I'm using simplelink_cc13x2_sdk_2_30_00_45.

I manage to apply CAP array tuning via smart RF studio, and observe the impact on the Radio frequency by transmitting CW.

When I try to apply CAP array tuning via ccfg.c,  and flash my codeI don't see any impact on Radio frequency.

For example I define:

#define SET_CCFG_MODE_CONF_XOSC_CAP_MOD 0x0
#define SET_CCFG_MODE_CONF_XOSC_CAPARRAY_DELTA  __MY_VALUE___

This code managed to apply CAP array tuning on CC1352P PG 1.1.

Could you please assist?

BR,

Amit

Part Number:CCSTUDIO

Tool/software: Code Composer Studio

I too see the installer hang on installing  ti_dspack_ibsetup_6.1.0.1449.bin and can't download it.

I had CCS v6.2 installed and running but it errored out on the Grace files and so I had to install 6.1.2 which is the last version which supports Grace.

Part Number:TMDSCNCD28335

I am using F28335 experimenters kit for motor control and programming it through Simulink. I am using module A of EPWM to switch all the upper devices of an inverter and module B for all the lower in a complementary fashion. I need to insert dead band for rising as well as the falling edge of the PWM signals, in addition, I require complete control on module A as well as module B using continuous software force input. To insert deadband I am using Active high complementary setting in Deadband submodule of EPWM module. As soon as I use this setting I cannot individually control the A&B modules using software force, If A is kept at low the B will remain at high even if its forced to low. How can I obtain this control?     

Part Number:BEAGLEBK

Tool/software: Linux

I want use ti-ads8688 iio driver as a kernel module. I am using Beaglebone Black.

I wrote below Makefile for this work.

obj-m+=ti-ads8688.o
all:
    make -C /lib/modules/$(shell uname -r)/build/ M=$(PWD) modules
clean:
    make -C /lib/modules/$(shell uname -r)/build/ M=$(PWD) clean

ti-ads8688.ko file correctly generated and i load it with insmod command. But there is not module in iio devices, as you can see in below:

debian@beaglebone:~/work/phase1$ ls /sys/bus/iio/devices/iio\:device0
buffer           in_voltage1_raw  in_voltage4_raw  in_voltage7_raw  power          uevent
dev              in_voltage2_raw  in_voltage5_raw  name             scan_elements
in_voltage0_raw  in_voltage3_raw  in_voltage6_raw  of_node          subsystem

am i miss something? I also add in my devicetree below unit:

adc@0 {
    compatible = "ti,ads8688";
    reg = <0>;
    spi-cpha;
    spi-max-frequency = <100000>;
};

Part Number:TMS570LS3137-EP

Hello,

in reference to TMS57LS3137 datasheet SPNS230D.OCTOBER 2013–REVISED FEBRUARY 2015 the section 6.10.5 and 6.10.6 list the "Flash Program and Erase Timings for Program Flash and Data Flash" respectively. in general the "data retention" specification  means the data retention of the device without a power cycle or unpowered duration. Is the spec "data retention" is unpowered for 5years? Is the data retention dependent on ambient (storage) temp? What is 125C in the datasheet? Isn't 125C and 250C in note 3 contradict each other? 

with regards

Rajeeva GK

Part Number:CC2640R2F

Hi,

I am performing a scan to detect the ibeacons and some ibeacons are detected twice. Note, the duplicate filtering is enabled by default, so I haven't done anything with regards to that. I am using the ibeacon simulator app (Android) to broadcast 5 ibeacons. I have slightly modified the SimpleObserver_addDeviceInfo( ) in the simple_peripheral_observer project to detect and display the ibeacons. The below is the result I get.

#000008 [ 0.206 ] INFO: (simple_peripheral_observer.c:517) Beacon0
#000009 [ 0.206 ] INFO: (simple_peripheral_observer.c:518) Byte 0: Length = 0x1a
#000010 [ 0.206 ] INFO: (simple_peripheral_observer.c:519) Byte 1: Type = 0xff(Custom Manufacture Packet)
#000011 [ 0.206 ] INFO: (simple_peripheral_observer.c:520) Byte 2-3: Manufacture Id = 0x4c 0x00(Apple)
#000012 [ 0.206 ] INFO: (simple_peripheral_observer.c:521) Byte 4: SubType = 0x02(iBeacon)
#000013 [ 0.206 ] INFO: (simple_peripheral_observer.c:522) Byte 5: SubType Length = 0x15
#000014 [ 0.206 ] INFO: (simple_peripheral_observer.c:523) Byte 6-21: Proximity UUID = 0xD4ED5DFDC82D4D03A719A608E94791F3
#000015 [ 0.206 ] INFO: (simple_peripheral_observer.c:524) Byte 22-23: Major = 0x0000
#000016 [ 0.206 ] INFO: (simple_peripheral_observer.c:525) Byte 24-25: Minor = 0x0000
#000017 [ 0.206 ] INFO: (simple_peripheral_observer.c:526) Byte 26: Signal Power = 0xbf
#000018 [ 0.222 ] INFO: (simple_peripheral_observer.c:516) dataLen = 27
#000019 [ 0.222 ] INFO: (simple_peripheral_observer.c:517) Beacon1
#000020 [ 0.222 ] INFO: (simple_peripheral_observer.c:518) Byte 0: Length = 0x1a
#000021 [ 0.222 ] INFO: (simple_peripheral_observer.c:519) Byte 1: Type = 0xff(Custom Manufacture Packet)
#000022 [ 0.222 ] INFO: (simple_peripheral_observer.c:520) Byte 2-3: Manufacture Id = 0x4c 0x00(Apple)
#000023 [ 0.222 ] INFO: (simple_peripheral_observer.c:521) Byte 4: SubType = 0x02(iBeacon)
#000024 [ 0.222 ] INFO: (simple_peripheral_observer.c:522) Byte 5: SubType Length = 0x15
#000025 [ 0.222 ] INFO: (simple_peripheral_observer.c:523) Byte 6-21: Proximity UUID = 0x4B795071D5A54617A89285AAB793D8EF
#000026 [ 0.222 ] INFO: (simple_peripheral_observer.c:524) Byte 22-23: Major = 0x0000
#000027 [ 0.222 ] INFO: (simple_peripheral_observer.c:525) Byte 24-25: Minor = 0x0000
#000028 [ 0.223 ] INFO: (simple_peripheral_observer.c:526) Byte 26: Signal Power = 0xbf
#000029 [ 0.316 ] INFO: (simple_peripheral_observer.c:516) dataLen = 27
#000030 [ 0.316 ] INFO: (simple_peripheral_observer.c:517) Beacon2
#000031 [ 0.316 ] INFO: (simple_peripheral_observer.c:518) Byte 0: Length = 0x1a
#000032 [ 0.316 ] INFO: (simple_peripheral_observer.c:519) Byte 1: Type = 0xff(Custom Manufacture Packet)
#000033 [ 0.316 ] INFO: (simple_peripheral_observer.c:520) Byte 2-3: Manufacture Id = 0x4c 0x00(Apple)
#000034 [ 0.316 ] INFO: (simple_peripheral_observer.c:521) Byte 4: SubType = 0x02(iBeacon)
#000035 [ 0.316 ] INFO: (simple_peripheral_observer.c:522) Byte 5: SubType Length = 0x15
#000036 [ 0.316 ] INFO: (simple_peripheral_observer.c:523) Byte 6-21: Proximity UUID = 0x4B795071D5A54617A89285AAB793D8EF
#000037 [ 0.316 ] INFO: (simple_peripheral_observer.c:524) Byte 22-23: Major = 0x0000
#000038 [ 0.316 ] INFO: (simple_peripheral_observer.c:525) Byte 24-25: Minor = 0x0000
#000039 [ 0.316 ] INFO: (simple_peripheral_observer.c:526) Byte 26: Signal Power = 0xbf
#000040 [ 0.321 ] INFO: (simple_peripheral_observer.c:516) dataLen = 27
#000041 [ 0.321 ] INFO: (simple_peripheral_observer.c:517) Beacon3
#000042 [ 0.321 ] INFO: (simple_peripheral_observer.c:518) Byte 0: Length = 0x1a
#000043 [ 0.321 ] INFO: (simple_peripheral_observer.c:519) Byte 1: Type = 0xff(Custom Manufacture Packet)
#000044 [ 0.321 ] INFO: (simple_peripheral_observer.c:520) Byte 2-3: Manufacture Id = 0x4c 0x00(Apple)
#000045 [ 0.321 ] INFO: (simple_peripheral_observer.c:521) Byte 4: SubType = 0x02(iBeacon)
#000046 [ 0.321 ] INFO: (simple_peripheral_observer.c:522) Byte 5: SubType Length = 0x15
#000047 [ 0.321 ] INFO: (simple_peripheral_observer.c:523) Byte 6-21: Proximity UUID = 0x4B795071D5A54617A89285AAB793D8EF
#000048 [ 0.321 ] INFO: (simple_peripheral_observer.c:524) Byte 22-23: Major = 0x0000
#000049 [ 0.321 ] INFO: (simple_peripheral_observer.c:525) Byte 24-25: Minor = 0x0000
#000050 [ 0.321 ] INFO: (simple_peripheral_observer.c:526) Byte 26: Signal Power = 0xbf
#000051 [ 0.702 ] INFO: (simple_peripheral_observer.c:516) dataLen = 27
#000052 [ 0.703 ] INFO: (simple_peripheral_observer.c:517) Beacon4
#000053 [ 0.703 ] INFO: (simple_peripheral_observer.c:518) Byte 0: Length = 0x1a
#000054 [ 0.703 ] INFO: (simple_peripheral_observer.c:519) Byte 1: Type = 0xff(Custom Manufacture Packet)
#000055 [ 0.703 ] INFO: (simple_peripheral_observer.c:520) Byte 2-3: Manufacture Id = 0x4c 0x00(Apple)
#000056 [ 0.703 ] INFO: (simple_peripheral_observer.c:521) Byte 4: SubType = 0x02(iBeacon)
#000057 [ 0.703 ] INFO: (simple_peripheral_observer.c:522) Byte 5: SubType Length = 0x15
#000058 [ 0.703 ] INFO: (simple_peripheral_observer.c:523) Byte 6-21: Proximity UUID = 0xC148398CB6DC43EEBCCA582A9995DCBA
#000059 [ 0.703 ] INFO: (simple_peripheral_observer.c:524) Byte 22-23: Major = 0x0000
#000060 [ 0.703 ] INFO: (simple_peripheral_observer.c:525) Byte 24-25: Minor = 0x0000
#000061 [ 0.703 ] INFO: (simple_peripheral_observer.c:526) Byte 26: Signal Power = 0xbf

In the above, you can see that ibeacon1, 2 and 3 are same packets. I want to filter out all duplicates and detect only unique packets. Any idea how to fix this and why this may be happening? Does it have anything to do with the Log_Info prints I am using to print them out?

Also, another issue I am facing similar is that, when I use system_printf( ) to print the above instead of Log_info as shown below. It doesn't work. Any idea why this dont work?

           System_printf("dataLen = %u", dataLen);
            System_printf("Beacon%u", deviceCnt);
            System_printf("Byte 0: Length = 0x%02x", data[point]);
            System_printf("Byte 1: Type = 0x%02x(Custom Manufacture Packet)", data[point + 1]);
            System_printf("Byte 2-3: Manufacture Id = 0x%02x 0x%02x(Apple)",data[point + 2], data[point + 3]);
            System_printf("Byte 4: SubType = 0x%02x(iBeacon)", data[point + 4]);
            System_printf("Byte 5: SubType Length = 0x%02x", data[point + 5]);
            System_printf("Byte 6-21: Proximity UUID = %s", Util_convertBdIntArray2Str(data + (point + 6), 16));
            System_printf("Byte 22-23: Major = 0x%04x", (data[point + 22] << 8) + data[point + 23]);
            System_printf("Byte 24-25: Minor = 0x%04x", (data[point + 24] << 8) + data[point + 25]);
            System_printf("Byte 26: Signal Power = 0x%02x", data[point + 26]);
            System_printf("\r\n");
            System_flush();

Part Number:CC3200

Tool/software: Code Composer Studio

Hi,

I am unable to reach the link  http://m2m.demos.ibm.com/mqttclient/ for mqtt connection. All the applications related to mqtt has same link.

Do you have another link to communicate with device through mqtt?

Thanks

Hi

According to EN 50131-5-3 standard , in order to meet Grade 3 Sub 1GHz security system it needs Transceiver with Dual band support (like 868 and 433 MHz).Right?

The questions about Dual band implementation in CC1310 is as follow:

1. Does CC1310 meet EN 50131-5-3 Grade 3? What needs for that?
2. Could CC1310  transmit & receiving in two separate bands such as 868 and 433  to  overcoming the interfering signals (Immunity to interference section 4.4 of EN 50131-5-3 ------> 10v/m)?
3. Which selectivity required from our line up receiver (external SAW filter) to meet immunity to interference requirement 10v/m?
   

Regards

Roni

Part Number:TPA2000D2

Tool/software:TINA-TI or Spice Models

TI Designs to solve design challenges across many types of networks. here we are developing Audio amplifier.so we need spice model of TPA2000D2 amplifier to stimulate design in TINA or LT-Spice software.

Part Number:SN75DP159

Hi Team,

I am using my design SN75DP159 part, attached my schematic.

Should I connect the HPD_SNK directly to DVI Connector?

Thanks,

Shlomi

(Please visit the site to view this file)

Part Number:MSP430F5529

Hi Team,

I am looking for a reference example for over the air firmware update of the MSP430F5529 via the CC3100.

Can you assist on that? 

Thanks,

Shlomi

Part Number:TIDM-BIDIR-400-12

Tool/software: Code Composer Studio

Hello, again.

Thanks to your help. I can keep following the TIDM-BIDIR-400-12 reference design. 

Today, I got a problem with ADC. 

As I can see the tiduai7.pdf, Page 36, figure 44, I'm testing the buck mode open loop. 

In figure 44, ADC for input voltage/current, output voltage/current is referred Gui_Vfbin, Gui_Vfbout, Gui_Ifb, Gui_Iout respectively. 

As you see that page, it said output power is 72[W](6A,12V)

I have a question about this power. In figure 44, input power is around 182.9[W] and output power is 72[W]. 

I think this input current for ADC doesn't make it sense.

The figure below is my result.

In my Hardware, Power supply for input indicates 390V/0.21A, Electric Load indicates 2ohm/5.448A. So it matches input current for ADC I think. 

Another question is In real hardware, 5.448A is correct, But in real time ADC indicates the double value of it. (I changed the phase, rechecked the value, it is almost the double)

I think my current to voltage circuit is the problem. In tidrhs9.pdf, 

This is the before filter circuit for output current(. 

If my ADC values are doubled compared with the real value, where and what can I fix the circuit? If is not the problem of my circuit, what can you recommend for my problem.

Thank you for your help. 

Part Number:LM5022

Tool/software: WEBENCH® Design Tools

Dear TI,

  I have created a design  using LM5022 for I/p 12-48VDC and O/p of 51V 3A. Now my question is if i just change the FET from 15A to some FET with 100A current can i use same design with some modification to get around 10A?

My design link is "

If not can you help me what components i need to change to get my desired outputs? Deeply awaiting your reply.

Regards,

  Vijay Gohil

Part Number:MSP432P4111

Tool/software: Code Composer Studio

My problem is almost identical to this link: 

Here is what I get when trying to flash any binary file, even after factory reset like described in

https://e2e.ti.com/support/microcontrollers/msp430/f/166/p/456120/1652269#1652269

:

CORTEX_M4_0: File Loader: Memory write failed: Flash Programmer: Mass erase failed

CORTEX_M4_0: GEL: File: /Users/dingtianzhang/Downloads/eraseMem.hex: Load failed.

Erase simply does not work.

Please advice.

Part Number:DCA1000EVM

I'm trying to get raw data from the IWR1443BOOST with the DCA1000EVM using the mmWave Studio. However, BSS and MSS firmware doesn't seem to load correctly. 

I'm following the steps in the quick start guide, ran into problems after running the script. BSS firmware will load and the correct version number will show. MSS firmware seems to load but will show up as version 0.0.0.0. The rest of the script will run into errors. This is a screenshot after running the script and encountering the errors. 

Is there anything that I've done wrong?

Part Number:AM5728

Hello.

Im working with idk AM5728. I want to use UART.3 to receive data. It worked successfully without interrupt. I tried to configure the RHR interrupt. I have used the main code in pdk_am57xx_1_0_11\packages\ti\csl\example\uart\uart_intr for enabling interrupt (I changed the parameters and addresses due to AM5728/IPU1/C0) and interrupt.h in pdk_am57xx_1_0_11\packages\ti\csl\arch\m4 for the interrupt functions.  but nothing happened.

I checked the registers through Memory browser. it seems that an interrupt is pending. The value in UART_IIR (0x4802 0008) shows that Rx_time out is pending. These are the values of my memory after receiving data.

Now i have some questions.

1. Some registers in datasheet have same addresses (like UART_IIR and UART_EFR). How is it possible, and how can i understand what register im checking in memory browser in CCS?

2. what is the difference of RHR interrupt and Rx time-out interrupt and when does Rx time-out interrupt happen?

3. Is it necessary to config interrupt priorities (because there is just one interrupt)? I didn't do anything in my code for this part and the function of  Intc_IntPrioritySet is empty.

4. The IPU can handle 80 interrupts Due to chapter 17 of datasheet (Interrupt controller): 16 internal and 64 external interrupts. How can I set the ISR for each of them.

5. What should i do to config NVIC in IPU?

5. Can I use CMSIS library for my purpose? If i can, how?

6. Is there any bare metal example for UART (with interrupt) or for using NVIC?

Here is my whole project. Could you please take a look at my code? 

(Please visit the site to view this file)

Any help regarding this issue would be greatly appreciated. Thank you

Part Number:MSP-TS430DA38

Tool/software: Code Composer Studio

helo sir,

     i have working in msp430f2252..i getting code and got output from your web site like //ti resoruce explorer/msp430f2252/software/msp430ware/device/msp430f2252/peripheral_Example/Register_level/USCI_B0 I2C Master TX multiple bytes to MSP430 Slave  -OK

//ti resoruce explorer/msp430f2252/software/msp430ware/device/msp430f2252/peripheral_Example/Register_level/USCI_B0 I2C Master RX multiple bytes from MSP430 Slave  -NOT WORKING

here i have dought for bpth address should be 0x48 so we write address 0x48(8th bit mode like write=0) and read address 0x49(8th bit mode like read=1).

so i confuse can you explain this details.

thanking you

siru

Part Number:BQ24650

Hi,

I need to charge a LiFePO4 battery pack.

The pack is a 16V 9Ah.

As I understand from the datasheet, it should be possible to charge this pack right?

Another thing, I saw that there is a possibility to set the charging current (via Rsr), I would like to set the charging current to 5A, are there any considerations That I need to take into account? (Like the solar panel types for example or anything else?)

One last thing, is it possible to connect the BQ24650 output to a load as well to the battery? What do I need to do to enable that if it is possible at all?

Thanks,

Tomer

Part Number:PROCESSOR-SDK-AM57X

Tool/software: Code Composer Studio

pdk_am57xx_1_0_12/packages,  cannot make i2c module

error message is as the below:

kevin@ubuntu:/opt/ti/pdk_am57xx_1_0_12/packages$ make i2c
make -C ./ti/drv/i2c all
make[1]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make libcores SOC=am574x
make[2]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make lib_allendians CORE=c66x BUILD_PROFILE_c66x=release
make[3]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make comp_libs ENDIAN=little
make[4]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make -C /opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c -f build/makefile.mk
make[5]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make[5]: Nothing to be done for 'all'.
make[5]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make -C /opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c -f build/makefile_indp.mk
make[5]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make[5]: Nothing to be done for 'all'.
make[5]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make -C /opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c -f build/makefile_profile.mk
make[5]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make[5]: Nothing to be done for 'all'.
make[5]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make -C /opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c -f build/makefile_profile_indp.mk
make[5]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make[5]: Nothing to be done for 'all'.
make[5]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
Nothing to be done for am574x i2c_icss0
make[4]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make[3]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make lib_allendians CORE=a15_0 BUILD_PROFILE_a15_0=release
make[3]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make comp_libs ENDIAN=little
make[4]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make -C /opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c -f build/makefile.mk
make[5]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make[5]: Nothing to be done for 'all'.
make[5]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make -C /opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c -f build/makefile_indp.mk
make[5]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make[5]: Nothing to be done for 'all'.
make[5]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make -C /opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c -f build/makefile_profile.mk
make[5]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make[5]: Nothing to be done for 'all'.
make[5]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make -C /opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c -f build/makefile_profile_indp.mk
make[5]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make[5]: Nothing to be done for 'all'.
make[5]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
Nothing to be done for am574x i2c_icss0
make[4]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make[3]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make lib_allendians CORE=ipu1_0 BUILD_PROFILE_ipu1_0=release
make[3]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make comp_libs ENDIAN=little
make[4]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make -C /opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c -f build/makefile.mk
make[5]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make[5]: Nothing to be done for 'all'.
make[5]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make -C /opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c -f build/makefile_indp.mk
make[5]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make[5]: Nothing to be done for 'all'.
make[5]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make -C /opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c -f build/makefile_profile.mk
make[5]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make[5]: Nothing to be done for 'all'.
make[5]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make -C /opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c -f build/makefile_profile_indp.mk
make[5]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make[5]: Nothing to be done for 'all'.
make[5]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
Nothing to be done for am574x i2c_icss0
make[4]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make[3]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make[2]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make libcores SOC=am572x
make[2]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make lib_allendians CORE=c66x BUILD_PROFILE_c66x=release
make[3]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make comp_libs ENDIAN=little
make[4]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make -C /opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c -f build/makefile.mk
make[5]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make[5]: Nothing to be done for 'all'.
make[5]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make -C /opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c -f build/makefile_indp.mk
make[5]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make[5]: Nothing to be done for 'all'.
make[5]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make -C /opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c -f build/makefile_profile.mk
make[5]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make[5]: Nothing to be done for 'all'.
make[5]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make -C /opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c -f build/makefile_profile_indp.mk
make[5]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make[5]: Nothing to be done for 'all'.
make[5]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
Nothing to be done for am572x i2c_icss0
make[4]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make[3]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make lib_allendians CORE=a15_0 BUILD_PROFILE_a15_0=release
make[3]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make comp_libs ENDIAN=little
make[4]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make -C /opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c -f build/makefile.mk
make[5]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make[5]: Nothing to be done for 'all'.
make[5]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make -C /opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c -f build/makefile_indp.mk
make[5]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make[5]: Nothing to be done for 'all'.
make[5]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make -C /opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c -f build/makefile_profile.mk
make[5]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make[5]: Nothing to be done for 'all'.
make[5]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make -C /opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c -f build/makefile_profile_indp.mk
make[5]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make[5]: Nothing to be done for 'all'.
make[5]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
Nothing to be done for am572x i2c_icss0
make[4]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make[3]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make lib_allendians CORE=ipu1_0 BUILD_PROFILE_ipu1_0=release
make[3]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make comp_libs ENDIAN=little
make[4]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make -C /opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c -f build/makefile.mk
make[5]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make[5]: Nothing to be done for 'all'.
make[5]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make -C /opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c -f build/makefile_indp.mk
make[5]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make[5]: Nothing to be done for 'all'.
make[5]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make -C /opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c -f build/makefile_profile.mk
make[5]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make[5]: Nothing to be done for 'all'.
make[5]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make -C /opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c -f build/makefile_profile_indp.mk
make[5]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make[5]: Nothing to be done for 'all'.
make[5]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
Nothing to be done for am572x i2c_icss0
make[4]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make[3]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make[2]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make libcores SOC=am571x
make[2]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make lib_allendians CORE=c66x BUILD_PROFILE_c66x=release
make[3]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make comp_libs ENDIAN=little
make[4]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make -C /opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c -f build/makefile.mk
make[5]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make[5]: Nothing to be done for 'all'.
make[5]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make -C /opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c -f build/makefile_indp.mk
make[5]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make[5]: Nothing to be done for 'all'.
make[5]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make -C /opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c -f build/makefile_profile.mk
make[5]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make[5]: Nothing to be done for 'all'.
make[5]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make -C /opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c -f build/makefile_profile_indp.mk
make[5]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make[5]: Nothing to be done for 'all'.
make[5]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
Nothing to be done for am571x i2c_icss0
make[4]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make[3]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make lib_allendians CORE=a15_0 BUILD_PROFILE_a15_0=release
make[3]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make comp_libs ENDIAN=little
make[4]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make -C /opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c -f build/makefile.mk
make[5]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make[5]: Nothing to be done for 'all'.
make[5]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make -C /opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c -f build/makefile_indp.mk
make[5]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make[5]: Nothing to be done for 'all'.
make[5]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make -C /opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c -f build/makefile_profile.mk
make[5]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make[5]: Nothing to be done for 'all'.
make[5]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make -C /opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c -f build/makefile_profile_indp.mk
make[5]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make[5]: Nothing to be done for 'all'.
make[5]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
Nothing to be done for am571x i2c_icss0
make[4]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make[3]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make lib_allendians CORE=ipu1_0 BUILD_PROFILE_ipu1_0=release
make[3]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make comp_libs ENDIAN=little
make[4]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make -C /opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c -f build/makefile.mk
make[5]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make[5]: Nothing to be done for 'all'.
make[5]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make -C /opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c -f build/makefile_indp.mk
make[5]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make[5]: Nothing to be done for 'all'.
make[5]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make -C /opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c -f build/makefile_profile.mk
make[5]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make[5]: Nothing to be done for 'all'.
make[5]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make -C /opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c -f build/makefile_profile_indp.mk
make[5]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make[5]: Nothing to be done for 'all'.
make[5]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
Nothing to be done for am571x i2c_icss0
make[4]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make[3]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make[2]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make firmcores SOC=am574x
make[2]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make firm_allhostcores CORE=pru_0
make[3]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make firm_allversion HOSTCORE=c66x
make[4]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make comp_firm PRUVERSION=REV2
make[5]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
make -C /opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c/firmware/icss_i2c -f ../../build/makefile_icss_i2c.mk
make[6]: Entering directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c/firmware/icss_i2c'
#
# Linking into am574x:pru_0:icss_i2c into /opt/ti/pdk_am57xx_1_0_12/packages/ti/binary/icss_i2c/obj/am574x/c66x/REV2/pru_0/icss_i2c_PRU0/icss_i2c_PRU0.out...
#
/opt/ti/ti-cgt-pru_2.2.1/bin/clpru -v3 -g --endian=little --define=am574x --diag_wrap=off --diag_warning=225 --display_error_number --hardware_mac=on -z --stack_size=0 --heap_size=0 --reread_libs --warn_sections -I/opt/ti/ti-cgt-pru_2.2.1/include -I/opt/ti/ti-cgt-pru_2.2.1/lib --define=PRU0 --define=pru0 --entry_point=I2C_scheduler /opt/ti/pdk_am57xx_1_0_12/packages/ti/binary/icss_i2c/obj/am574x/c66x/REV2/pru_0/I2C_scheduler.opru /opt/ti/pdk_am57xx_1_0_12/packages/ti/binary/icss_i2c/obj/am574x/c66x/REV2/pru_0/I2C_protocol.opru /opt/ti/pdk_am57xx_1_0_12/packages/ti/binary/icss_i2c/obj/am574x/c66x/REV2/pru_0/I2C_smbus.opru /opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c/firmware/icss_i2c/src/pru.cmd -o /opt/ti/pdk_am57xx_1_0_12/packages/ti/binary/icss_i2c/obj/am574x/c66x/REV2/pru_0/icss_i2c_PRU0.out -m /opt/ti/pdk_am57xx_1_0_12/packages/ti/binary/icss_i2c/obj/am574x/c66x/REV2/pru_0/icss_i2c_PRU0.map --xml_link_info="/opt/ti/pdk_am57xx_1_0_12/packages/ti/binary/icss_i2c/obj/am574x/c66x/REV2/pru_0/icss_i2c_PRU0_linkInfo.xml" -l/opt/ti/ti-cgt-pru_2.2.1/lib/libc.a
<Linking>
fatal error #10296: cannot open output file "/opt/ti/pdk_am57xx_1_0_12/packages/ti/binary/icss_i2c/obj/am574x/c66x/REV2/pru_0/icss_i2c_PRU0.out" for writing

>> Compilation failure
/opt/ti/pdk_am57xx_1_0_12/packages/ti/build/makerules/rules_pru.mk:118: recipe for target '/opt/ti/pdk_am57xx_1_0_12/packages/ti/binary/icss_i2c/obj/am574x/c66x/REV2/pru_0/icss_i2c_PRU0' failed
make[6]: *** [/opt/ti/pdk_am57xx_1_0_12/packages/ti/binary/icss_i2c/obj/am574x/c66x/REV2/pru_0/icss_i2c_PRU0] Error 1
make[6]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c/firmware/icss_i2c'
/opt/ti/pdk_am57xx_1_0_12/packages/ti/build/comp_top.mk:377: recipe for target 'icss_i2c' failed
make[5]: *** [icss_i2c] Error 2
make[5]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
/opt/ti/pdk_am57xx_1_0_12/packages/ti/build/comp_top.mk:193: recipe for target 'REV2_firm' failed
make[4]: *** [REV2_firm] Error 2
make[4]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
/opt/ti/pdk_am57xx_1_0_12/packages/ti/build/comp_top.mk:190: recipe for target 'c66x_firm' failed
make[3]: *** [c66x_firm] Error 2
make[3]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
/opt/ti/pdk_am57xx_1_0_12/packages/ti/build/comp_top.mk:187: recipe for target 'pru_0_firm' failed
make[2]: *** [pru_0_firm] Error 2
make[2]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
/opt/ti/pdk_am57xx_1_0_12/packages/ti/build/comp_top.mk:184: recipe for target 'am574x_firm' failed
make[1]: *** [am574x_firm] Error 2
make[1]: Leaving directory '/opt/ti/pdk_am57xx_1_0_12/packages/ti/drv/i2c'
makefile:89: recipe for target 'i2c' failed
make: *** [i2c] Error 2
kevin@ubuntu:/opt/ti/pdk_am57xx_1_0_12/packages$