Hi,

I'm working on an application based on SimpleBLEPeripheral example. I need to optimize memory usage, then I would like to use static task instead of dynamic ones (the application creates the tasks at boot and they are never deleted).

Is it possible to do so while using the ble stack?

My idea is to create the static tasks (the GAPRole task and two other application tasks) then copy and paste the code from the already tested version to the new created static tasks (removing the parts related to the dynamic creation of the task). Is this sufficient? Do the other things like message queues, semaphores, ecc work as with dynamic tasks?

Davide.

Hi All,

I want to connect my hardware DSPC8681E Card to CCS.

I don't want to connect it into the emulation environment.

So please guide me to do this.

Regards,

Rohit

Hello to all!
I need some help about my project. My project is a thrust stand data acquisition shield that i made to characterize the actuator group of a quadcopter. In particular, this shield give me the measure of the following quantities: the current absorbed by the motor, the voltage across the battery, the thrust generated by the propeller, and the speed of the motor.
For doing this, i have used this components:

• ACS712 - 30A, to measure the current
• INA125P and a load cell, to measure the thrust
• Resistor Divider, to measure the voltage
• Diy optical encoder, to measure the speed of the motor

I'm using Arduino to acquire the datas, so i can process them using Matlab.
Following the datashees of the components, I have done a circuit. I have tested a part of this circuit on the breadboard. This ciruit is compose of the INA125P, load cell, battery and ESC. The others circuits (current, voltage and speed measures) are of another project and it work well. To test the full circuit i have done a pcb, but the problem is that on the pcb, the circuit don't work well.

In particular, the scales and the voltage measure systems works well, but the others no. I can't arming the ESC, so the motor don't spins and i'm not able to test the other circuits.

Someone can suggest me some solution on how to resolve this problem? 
I think that are some problems with the GND, the INA125P and the other components, but i ignore the cause because i'm not an EE, and is very difficult to me to find where i'm wrong.

Here, there is the circuit that i have done

Hi,

If i making use of CC3200 , then is it necessary to have external clock for it?

If i use external clock source it may consume space on PCB,So can i make use of internal clock oscillator and RTC?

Or is it required to use external clock also?

Thanks and Regards

Sagar

Hello,

I have a bq20z60 and bq29330 based board to protect a 4series LiFePo battery.

The problem is that when I connect  the SMBD, SMBC and GND wires to PC in order to read the parameters (voltage, SOC) there is a 0,6V drop between Vbattery and Vpack.

In the picture below an example of Vpack is shown. Normally is not conected, but each 15 minutes the board connects to the PC (see voltaqge drops in picture).

Why can this happend?

Thank you in advance,

Ekiuser

I spent a long time getting the MT41K256M16 DDR3 working with an AM4376 on a custom board and I'd like to share my experience. As a disclaimer, I'm a firmware guy and know some but not a lot about hardware in general and very little about DDR3.

I started modifying U-Boot from the Eval board software development kit to create a new MLO and U-Boot. The code contains some #defines starting with MT41K256M16HA125E, which looked promising. I also had the GEL file AM43xx_EMIFconfig_HWlvl.gel. Both of these turned out to be misleading. Eventually, I found the configuration structure for the Starter kit board, which uses MT41K256M16, though in a 32-bit mode while my custom board uses it in 16-bit mode.

The bottom line is that the key register that only the Starter kit's ddr3_sk_emif_regs_440Mhz structure configured correctly for my board is the EMIF4D_DDR_PHY_CTRL_1 register (p 1408 in the TRM SPRUHL7D revised August 2015). The fields in this mysterious register are described by "see phy spec for description", without any indication as to what "phy spec" it's talking about, so I still don't know how the values for this were determined for the Starter kit.

In any case, if you're trying to get MT41K256M16 DDR3 to work, start with the Starter kit configuration in am43xx/board.c and not the GEL file.

Hi,

I have the following problem with CLA math. converting a positive float to int value works correctly. But converting a negative floating value to int is incorrect.

This is the code:

    int i;
    if (float_value <= -1) {
        i=(int)float_value;
        long_value+=(long)i;
        float_value+= (float)i;
    }

So  how do I solve this?

 Thanks!

In the relocation entries (.rela.text section in ELF file) we see a negative addend: rodata - 2. The symbol .rodata is located at 0x4000. Thus the relocation address results in 0x3FFE. Contrarily to this the code uses the correct address 0x400c. The relocation information seems to be wrong.

Using gcc_msp430_4.9.14r1_167 : msp430-elf-gcc  -mmcu=msp430f1611 main.c

msp430-elf-objdump -sD:

00005560 <__do_global_ctors_aux>:
    5560:	0a 12       	push	r10		;
    5562:	1c 42 0c 40 	mov	&0x400c,r12	;0x400c
    5566:	3c 93       	cmp	#-1,	r12	;r3 As==11
    5568:	08 24       	jz	$+18     	;abs 0x557a

msp430-elf-readelf -a:

.rela.text
 Offset     Info    Type            Sym.Value  Sym. Name + Addend
...
00005564  00000203 R_MSP430_16       00004000   .rodata - 2
...

(Please visit the site to view this file)

Hi! I'm trying to setup OSD Window 0 in the Video Back End of the DM369 processor. But I don't see any presense of the window on the display. Video windows 0 and 1 are configured and displayed normally. Here is my settings for the OSD window 0:

OSDWIN0XP = 384;  // window start position
OSDWIN0YP = 384;  // window start position
OSDWIN0XL = 256;  // window width
OSDWIN0YL = 256;  // window height
OSDWIN0OFST = 256 / 16;

// BMPMDE = 1, input mode = YCbCr data, blending ratio = 7, frame mode, window is active (displayed):
OSDWIN0MD = ((0x01 << 15) | (0x03 << 13) | (0x07 << 3) | (0x01 << 1) | (0x01 << 0));

Also the address of buffer with picture is configured in OSDWIN0OFST, OSDWINADH and OSDWIN0ADL registers.

Hi,

I'm having difficulty in configuring the PCM line on the BT unit cc2564b and this is my configuration:

----

HCI_VS_Write_CODEC_Config (0xFD06):

88 00 - 136 KHz - 00 88 - PCM Clk Rate
01 - PCM Clk direction : Input
50 05 00 00 - Frame Syn Freq - 1360 Hz - 00 00 05 50
46 00 - Frame Sync Duty Cycle - 70 - 00 46
01 - Frame Sync Edge - falling edge
00 - Frame Sync Polarity - Active High
00 - Reserved
10 00 - Channel 1 data out size - 16 - 00 10
00 00 - Channel 1 data out offset - 0
01 - Channel 1 data out edge - falling - 01
10 00 - Channel 1 data in size - 16 - 00 10
00 00 - Channel 1 data in offset - 0
00 - Channel 1 data in edge - rising - 00
00 - Reserved
00 00 - Channel 2 data out size - 16
00 00 - Channel 2 data out offset - 0
00 - Channel 2 data out edge - falling - 01
00 00 - Channel 2 data in size - 16
00 00 - Channel 2 data in offset - 0
00 - Channel 2 data in edge - rising - 00
00 - Reserved

ret = bt_run_command("hcitool -i hci0 cmd 3F 106 88 00 01 50 05 00 00 46 00 01 00 00 10 00 00 00 01 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00", "Setup PCM Link: ", &ret_str, &cmd_ret);

----

After I've done the above configuration I unpair, pair, connect, play with a BT headset device and can hear a channel open with background noise active.
Then I proceed with configuring the Telit Modem with the DVI voice setup as described in their doc: Telit_GE910_Family_Digital_Voice_Interface_Application_Note_r2.pdf, i.e.:

----

Configure the module in Master-Burst (PCM) Mode

AT#DVI=1,1,1
OK

1 enable DVI interface
1 use DVI port 1 (mandatory)
1 set the module DVI as Master (factory setting)

AT#DVIEXT=0,0,0,0,1
OK

0 Burst Mode (PCM)
0 sample rate 8 KHz (mandatory)
0 16 bits per sample
0 Mono Mode
1 the rising edge of the clock is used to shift out the next data to transmit. The received data bit is captured
on the falling edge of the clock (0 has the same behavior).

----

And the BitClockFrequency is set to 136KHz.

So both the BT unit and Modem is configured with the "correct" or "matching" setup requirements, i.e. samplerate = 8KHz, 16bits PCM data frame size, Clock freq = 136KHz, but still can't get a voice call over to the BT headset.
I've verified with a Oscilloscope the PCM lines IN, OUT, SYNC, CLK, and as soon as a phone call is setup on the Telit Modem, I can see the correct frequencies on the scope for the PCM lines CLK of 136KHz and SYNC=8KHz and the IN line with datastream and frequency of 15KHz.
When I speak on the BT headset side the PCM OUT line is always set to 0V or low-level on the scope, whereas I expect a voice datastream, but nothing.

The Modem does configure the PCM lines and work as expected but not the CC2564B unit, Please tell me what I am doing wrong. I am on a very tight schedule to get this working, please do escalate this to higher prio ASAP.

-----

This is the console output, you will see that the BT module is being initialized, device MAC address is set, PCM Link setup is done, unpair, pair, connect, play, Telit Modem config is done (which is setting the above mentioned AT-commands). Right at where it says "Agent has been released" I can hear the channel noise on the BT device headset. 

Then, right after time "700101 00:01:54.0690" I make a phone call and it is answered at the Modem and I can see the PCM lines CLK, SYNC, IN have "data" with expected frequency as described in the DVI Telit manual as mentioned earlier. But no voice is relayed from the PCM IN port on the CC2564B to the BT headset device.


[700101 00:01:02.0898 Note] ptbt.c:1412: handle_bt_test, new_state: 0, bt_state: 0
[700101 00:01:06.3053 Note] ptbt.c:1379: - handle_bt_test: 0
[700101 00:01:06.3056 Note] ptbt.c:715: - handle_idle_state
[700101 00:01:06.3059 Note] ptbt.c:1412: handle_bt_test, new_state: 6, bt_state: 0
[700101 00:01:10.0070 Note] ptbt.c:1379: - handle_bt_test: 6
[700101 00:01:10.0079 Note] ptbt.c:1250: - handle_normal_state: 11
[700101 00:01:10.0083 Note] ptbt.c:1265: - SET Device MAC frame : 0
[700101 00:01:10.0086 Note] ptbt.c:1286: - SET Device MAC ret_val : 0
[700101 00:01:10.0088 Note] ptbt.c:1287: - SET Device MAC new_state : 6
[700101 00:01:10.0091 Note] ptbt.c:1365: ret_val: 0
[700101 00:01:10.0094 Note] ptbt.c:1412: handle_bt_test, new_state: 6, bt_state: 6
Error: Invalid signal id
Can't get device info: No such device
killall: hciattach: no process killed
Found a Texas Instruments' chip!
Firmware file : /lib/firmware/TIInit_6.7.16.bts
Loaded BTS script version 1
texas: changing baud rate to 115200, flow control to 0
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: SCO (Voice Link) ver 0.6
Bluetooth: SCO socket layer initialized
Bluetooth: HCI UART driver ver 2.2
Bluetooth: HCI H4 protocol initialized
Bluetooth: HCI BCSP protocol initialized
Bluetooth: HCILL protocol initialized
Warning: unknown command - "scan"
[700101 00:01:10.9071 Note] ptbt.c:1379: - handle_bt_test: 6
[700101 00:01:10.9074 Note] ptbt.c:1250: - handle_normal_state: 11
[700101 00:01:10.9077 Note] ptbt.c:1265: - SET Device MAC frame : 1
[700101 00:01:10.9087 Note] ptbt.c:295: - startup_bluetooth_normal
[700101 00:01:10.9095 Note] ptbt.c:1856: - bt_init_chip
[700101 00:01:10.9104 Note] ptbt.c:1821: - bt_find_hw_type
[700101 00:01:10.9107 Note] ptbt.c:1822: Find out which bt chip we have
[700101 00:01:10.9111 Note] ptbt.c:216: - bt_run_any_command
[700101 00:01:10.9161 Note] ptbt.c:221: ioctrl BT_RST_N
[700101 00:01:10.9238 Note] ptbt.c:234: Probing for BT_RST_N: child exit status 1
[700101 00:01:10.9241 Note] ptbt.c:216: - bt_run_any_command
[700101 00:01:10.9252 Note] ptbt.c:221: ioctrl BT_NSHUTD_EN
[700101 00:01:10.9358 Note] ptbt.c:225: Probing for BT_SHUTDOWN_N 0
[700101 00:01:10.9378 Note] ptbt.c:234: Probing for BT_SHUTDOWN_N: child exit status 0
[700101 00:01:10.9381 Note] ptbt.c:1837: TI CC2564B chip
[700101 00:01:10.9384 Note] ptbt.c:1766: - bt_init_cc2564b_chip
[700101 00:01:10.9387 Note] ptbt.c:1767: Initialize bluetooth,
[700101 00:01:10.9500 Note] ptbt.c:1775: nSHUTD to low: 0
[700101 00:01:11.1144 Note] ptbt.c:1787: nSHUTD to high: 0
[700101 00:01:11.1163 Note] ptbt.c:132: - bt_check_cts
[700101 00:01:11.1240 Note] ptbt.c:132: - bt_check_cts
[700101 00:01:11.1320 Note] ptbt.c:132: - bt_check_cts
[700101 00:01:11.1400 Note] ptbt.c:132: - bt_check_cts
[700101 00:01:11.1480 Note] ptbt.c:132: - bt_check_cts
[700101 00:01:11.1560 Note] ptbt.c:132: - bt_check_cts
[700101 00:01:11.1640 Note] ptbt.c:132: - bt_check_cts
[700101 00:01:11.1720 Note] ptbt.c:132: - bt_check_cts
[700101 00:01:11.1800 Note] ptbt.c:132: - bt_check_cts
[700101 00:01:11.1880 Note] ptbt.c:132: - bt_check_cts
[700101 00:01:11.1960 Note] ptbt.c:132: - bt_check_cts
[700101 00:01:11.2040 Note] ptbt.c:132: - bt_check_cts
[700101 00:01:11.2120 Note] ptbt.c:132: - bt_check_cts
[700101 00:01:11.2200 Note] ptbt.c:1802: CTS res = 0
[700101 00:01:11.2203 Note] ptbt.c:170: - bt_run_command
[700101 00:01:11.2214 Note] ptbt.c:175: /etc/init.d/dbus-1 start
[700101 00:01:11.3564 Note] ptbt.c:179: Start dbus: Starting system message bus: dbus.
[700101 00:01:11.3578 Note] ptbt.c:188: Start dbus: : child exit status 0
[700101 00:01:11.3581 Note] ptbt.c:303: - bluetoothd
[700101 00:01:11.3584 Note] ptbt.c:170: - bt_run_command
[700101 00:01:11.3595 Note] ptbt.c:175: bluetoothd
[700101 00:01:11.4166 Note] ptbt.c:188: Bring up bluetoothd: : child exit status 0
[700101 00:01:11.4169 Note] ptbt.c:170: - bt_run_command
[700101 00:01:11.4180 Note] ptbt.c:175: hciconfig hci0 down
[700101 00:01:11.4569 Note] ptbt.c:188: Bring down hci: : child exit status 1
[700101 00:01:11.4572 Note] ptbt.c:170: - bt_run_command
[700101 00:01:11.4583 Note] ptbt.c:175: killall hciattach
[700101 00:01:11.5300 Note] ptbt.c:188: Bring down hciattach: : child exit status 1
[700101 00:01:11.5303 Note] ptbt.c:170: - bt_run_command
[700101 00:01:11.5314 Note] ptbt.c:175: hciattach ttyPSC3 texas
[700101 00:01:13.1853 Note] ptbt.c:179: Attach to hci: Device setup complete
[700101 00:01:13.1877 Note] ptbt.c:188: Attach to hci: : child exit status 0
[700101 00:01:13.6920 Note] ptbt.c:170: - bt_run_command
[700101 00:01:13.6931 Note] ptbt.c:175: hciconfig hci0 up
[700101 00:01:13.7066 Note] ptbt.c:188: Bring up hci: : child exit status 0
[700101 00:01:13.7601 Note] ptbt.c:170: - bt_run_command
[700101 00:01:13.7612 Note] ptbt.c:175: hciconfig hci0 scan
[700101 00:01:13.7742 Note] ptbt.c:179: Set hci discoverable: hci0: Type: BR/EDR Bus: UART
[700101 00:01:13.7745 Note] ptbt.c:179: Set hci discoverable: BD Address: A0:E6:F8:15:9C:9E ACL MTU: 1021:4 SCO MTU: 180:4
[700101 00:01:13.7749 Note] ptbt.c:179: Set hci discoverable: UP RUNNING PSCAN
[700101 00:01:13.7752 Note] ptbt.c:179: Set hci discoverable: RX bytes:797 acl:0 sco:0 events:37 errors:0
[700101 00:01:13.7755 Note] ptbt.c:179: Set hci discoverable: TX bytes:811 acl:0 sco:0 commands:37 errors:0
[700101 00:01:13.7758 Note] ptbt.c:179: Set hci discoverable:
[700101 00:01:13.7804 Note] ptbt.c:188: Set hci discoverable: : child exit status 0
[700101 00:01:13.8320 Note] ptbt.c:1286: - SET Device MAC ret_val : 0
[700101 00:01:13.8323 Note] ptbt.c:1287: - SET Device MAC new_state : 6
[700101 00:01:13.8326 Note] ptbt.c:1365: ret_val: 0
[700101 00:01:13.8329 Note] ptbt.c:1412: handle_bt_test, new_state: 6, bt_state: 6
Agent has been released
sh: can't kill pid 1226: No such process
[700101 00:01:14.1043 Note] ptbt.c:1379: - handle_bt_test: 6
[700101 00:01:14.1046 Note] ptbt.c:1250: - handle_normal_state: 16
[700101 00:01:14.1054 Note] ptbt.c:1068: - handle_texas_bt_play_test_state
[700101 00:01:14.1057 Note] ptbt.c:170: - bt_run_command
[700101 00:01:14.1068 Note] ptbt.c:175: hcitool -i hci0 cmd 3F 106 88 00 01 50 05 00 00 46 00 01 00 00 10 00 00 00 01 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[700101 00:01:14.1244 Note] ptbt.c:179: Setup PCM Link: < HCI Command: ogf 0x3f, ocf 0x0106, plen 34
[700101 00:01:14.1248 Note] ptbt.c:179: Setup PCM Link: 88 00 01 50 05 00 00 46 00 01 00 00 10 00 00 00 01 10 00 00
[700101 00:01:14.1251 Note] ptbt.c:179: Setup PCM Link: 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[700101 00:01:14.1445 Note] ptbt.c:179: Setup PCM Link: > HCI Event: 0x0e plen 4
[700101 00:01:14.1448 Note] ptbt.c:179: Setup PCM Link: 01 06 FD 00
[700101 00:01:14.1469 Note] ptbt.c:188: Setup PCM Link: : child exit status 0
[700101 00:01:19.2040 Note] ptbt.c:170: - bt_run_command
[700101 00:01:19.2051 Note] ptbt.c:175: ./bluetooth.sh unpair 30:17:C8:8D:35:7F
[700101 00:01:19.3711 Note] ptbt.c:179: BT Unpair: method return sender=:1.0 -> dest=:1.5 reply_serial=2
[700101 00:01:19.3748 Note] ptbt.c:188: BT Unpair:: child exit status 0
[700101 00:01:24.4320 Note] ptbt.c:170: - bt_run_command
[700101 00:01:24.4331 Note] ptbt.c:175: ./bluetooth.sh pair 30:17:C8:8D:35:7F
[700101 00:01:34.5752 Note] ptbt.c:188: BT pair:: child exit status 0
[700101 00:01:39.6320 Note] ptbt.c:170: - bt_run_command
[700101 00:01:39.6331 Note] ptbt.c:175: ./bluetooth.sh connect 30:17:C8:8D:35:7F
[700101 00:01:43.6647 Note] ptbt.c:179: BT connect: method return sender=:1.0 -> dest=:1.12 reply_serial=2
[700101 00:01:43.6676 Note] ptbt.c:188: BT connect:: child exit status 0
[700101 00:01:48.7240 Note] ptbt.c:170: - bt_run_command
[700101 00:01:48.7251 Note] ptbt.c:175: ./bluetooth.sh play 30:17:C8:8D:35:7F
[700101 00:01:48.8681 Note] ptbt.c:179: BT play: method return sender=:1.0 -> dest=:1.15 reply_serial=2
[700101 00:01:48.8729 Note] ptbt.c:188: BT play:: child exit status 0
[700101 00:01:54.0690 Note] ptbt.c:1183: - BT configuring PCM on modem success!!
[700101 00:02:01.0760 Note] ptbt.c:1365: ret_val: 0
[700101 00:02:01.0763 Note] ptbt.c:1412: handle_bt_test, new_state: 7, bt_state: 6
[700101 00:02:01.1029 Note] ptbt.c:1379: - handle_bt_test: 7
[700101 00:02:01.1032 Note] ptbt.c:1412: handle_bt_test, new_state: 7, bt_state: 7
[700101 00:02:01.1275 Note] ptbt.c:1379: - handle_bt_test: 7

Regards,
Nasser

Respected Sir/Madam,

                                         Recently I bought  C2000 Piccolo F28027 and F28027F want to use it in offline mode ( without GUI ), I'm unable to do, so could you help me out by giving the procedure to run it offline. ( I mean especially in code modifications )

Regards,

Anuroop

Hi, all:
  I'm developing an OSD application under DVRRDK 3.0 on 8168.
I reference the demo use case vcap+venc+vdis. Now I have
one doubt about this demo: the chain is composed of several
links which includes the algLink on the dsp. I can find every
link in the chain is started by the function "System_linkStart"
except the link algLink which does OSD.
  Can anyone tell me why this happens? Does this link need not
to be started? or I failed to find the place where the alg link
is started?

  Thanks!

I am using the LM5113 in a Class S Modulator/Envelope tracker application whereby I am varying the duty cycle/pulse width provided to the 5113 in order to achieve an output from 0V to ~Vdd at the output of the Modulator. This means the duty cycle provided to the Modulator varies from 0 to 95% -- 95% in order to allow recharge time for the top gate driver bootstrap capacitor. The Modulator operates at a 500kHz frequency and the bootstrap capacitance value is 1uF. The 5V power supply is bypassed with 1uF in parallel with 0.1uF. All the capacitors are on the reverse side of the PCB from the 5113 with the shortest connecting traces possible. The circuit works just fine with pulse inputs greater than ~15ns...however, the 5113 output rogue pulses for pulse inputs from approximately 0+ns to 14ns. These rogue pulses are approximately 115-120ns in duration, and they are "statistical" in nature. They are very infrequent coming into and leaving the previously-mentioned band of input pulse widths and occur with the greatest prevalence in the center of that band.

I adjusted the duty cycle to give me the minimum pulse width required by the 5113 to yield an output change. It was approximately 12ns, accounting for noise. It was just before (~4ns) and just after (~14ns) this supposed threshold that the extraordinarily long rogue pulses appear at the top gate drive signal of the LM5113. With some patience, I was able to capture a picture of this rogue pulse as a single shot trace:



The yellow trace is the input to the high side driver on the LM5113 and the blue trace is the output gate drive signal for the top GaN device. Notice that the input pulse is ~4ns wide...and the LM5113 shouldn't even output a signal according to their minimum input pulse width requirement of 10 ns, typical. Yet here we see an output pulse width that is ~115ns long!!! An extraordinary and unexpected value to say the least.

This is better put in perspective by observing the top drive pulse with both the top AND bottom gate drive signals:



In this picture the yellow is the top driver input pulse, the blue is the bottom gate drive signal and the purple is the top gate drive signal. You can see that there is 90ns of solid cross-conduction drive overlap provided in this situation...and this is what is immolating our GaN devices!!! And, according to the operation of the 5113, this shouldn't be happening!

Also, to illustrate the random nature of these rogue pulses, I captured this scope shot of one rogue pulse in a sequence:



In this scope shot you can see the single purple pulse (the top gate drive signal) occurring in the pulse sequence, where none are supposed to occur. This trace represents a 2.6% duty cycle, which again is just below TI's minimum specified pulse width. All it takes is one or two of these long duration pulses to destroy the GaN switches, given the robust cross conduction time provided by the phenomenon.


The funny thing is as soon as the top switch input pulse width exceeds ~12ns, the rogue pulses at the top gate drive signal disappear, and the gate pulse width increases monotonically as they should. There is no obvious or intuitive reason for this VERY elongated pulse to be occurring given the dearth of information about the innards of the LM5113 provided by TI.

These long rogue pulses are destroying the EPC2016 devices being driven in this application by the LM5113. If the input pulse width is kept above the "danger zone" where this rogue pulse phenomenon is observed, the Modulator works reliably, In fact the prototype has been running successfully with a ramping duty cycle of 5 to 95% for more than 100 hours now. I should be able to ramp the duty cycle/pulse width monotonically from 0% or 0ns to the maximum value without destroying the GaN devices being driven. Any insights that you might have into this problem/issue would be GREATLY appreciated. I can brute force implement a means of avoiding this small pulse width band, but the solution is complicated and I think unnecessary, as the LM5113 shouldn't output such long, rogue pulses.

Hi there!

According to the data sheet, one has to Options to supply the VIO rail:

1. use SMPS9
2. use an external 3.3V supply controlled by REGEN1

For my design, I chose the second approach. Therefore, SMPS9 output ist not used in the design.

Which is the proper way to treat SMPS9?

1. as in the EVM: supply SMPS9_IN, leave SMPS9_SW and _FBK open and connect SMPS9_GND to GND
2. as in the TPS659037 Design Checklist: supply SMPS9_IN, leave SMPS9_SW open and connect SMPS9_FBK and _GND to GND
3. probably something completely different like not supplying SMPS9_IN

Thanks in advance

  Wolfram Stumpf

In the kernel configuration file, what is the difference between:

CONFIG_MMC_OMAP

and

CONFIG_MMC_OMAP_HS

Are they mutually exclusive? What happens if you select both? Why are they listed as if they were 2 different types of controllers?

Hi,

I would like to know if it is possible to add a component (by that, I mean the SDK for the specific component) to a project? I've created a MSP432 project, and it runs perfectly. I would like to add some of the CC1120 functionalities in my code, but I don't really know how I could do that.

I tried to look for "CC1120" in the TI resource explorer, but I've found nothing.

Is there a way to import a component SDK using CCS? If not, what would be the "usual" steps to do so?

Regards

On 66AK2L06 datasheet, page 212 (recommended operating conditions) states that CVDD1 supply nominal value is 1.0V (min 0.952, max 1.047). Then on page 215, table 11-1 CVDD1 supply voltage is 0.95V.

What is the correct supply voltage (nominal) for CVDD1?

Hello

I have a question.

device:TPS7A3501
Please see datasheet P11.

8.2.2.5 Start-up time
Equation (3)
T_startup = 250,000 × CNR (s) 

The calculation value is wrong with the actual, but why is it?

Details are attached documents.

Thank you。

(Please visit the site to view this file)