Featured Discussions
text.format{('custom.tabs.no.results')}
Hello,
We are developing the bootloader for the Infineon TC377 board. For that, we need the preserved RAM (The memory that shouldn't be initialized with zero during the controller reset) to hold the flag. So, we tried the keywords below for No-initialization and location, but AURIX is not supporting these keywords. Instead of the below keywords, what can be used to create the memory in the RAM, so that it shouldn't be modified after reset of the microcontroller.
#pragma NOINIT(BootMode_InPreservedRAM)
#pragma LOCATION(BootMode_InPreservedRAM,0x50000000)
/*Here first we are creating the variable BootMode_InPreservedRAM as no initialization and giving the address as 0x50000000 for LOCATION*/
Thanks in advance.
Show LessHi,
I would like to test the bluetooth connection for cyw43439.
Currently the wifi sdio is working as expected as both STA and AP.
However, I could not get it recognized as a bluetooth device on my host.
I'm using and arm-32 based soc which is Ambarella s3lm board as my host. Currently, I've connected the UART pin to the host (CTS, RTS, Tx, Rx).
These are my output of the hci dev, no bluetooth device was listed.
# hcitool dev
Devices:
[ 51.908670] Bluetooth: Core ver 2.22
[ 51.914488] NET: Registered PF_BLUETOOTH protocol family
[ 51.919833] Bluetooth: HCI device and connection manager initialized
[ 51.926305] Bluetooth: HCI socket layer initialized
[ 51.931197] Bluetooth: L2CAP socket layer initialized
[ 51.936332] Bluetooth: SCO socket layer initialized
Nothing on my device list as well.
# ls /dev/
amb_gadget mem random tty3 tty57
amb_iris mtd0 rfkill tty30 tty58
amb_lens mtd0ro rtc0 tty31 tty59
ambac mtd1 shm tty32 tty6
ambad mtd1ro snapshot tty33 tty60
block mtd2 snd tty34 tty61
bus mtd2ro tty tty35 tty62
char mtd3 tty0 tty36 tty63
console mtd3ro tty1 tty37 tty7
dsplog mtd4 tty10 tty38 tty8
eis mtd4ro tty11 tty39 tty9
fdet mtd5 tty12 tty4 ttyS0
full mtd5ro tty13 tty40 ubi0
gpiochip0 mtd6 tty14 tty41 ubi0_0
gpiochip1 mtd6ro tty15 tty42 ubi_ctrl
i2c-0 mtd7 tty16 tty43 ucode
i2c-1 mtd7ro tty17 tty44 urandom
i2c-2 mtdblock0 tty18 tty45 vcs
iav mtdblock1 tty19 tty46 vcs1
input mtdblock2 tty2 tty47 vcsa
kmsg mtdblock3 tty20 tty48 vcsa1
loop-control mtdblock4 tty21 tty49 vcsu
loop0 mtdblock5 tty22 tty5 vcsu1
loop1 mtdblock6 tty23 tty50 watchdog
loop2 mtdblock7 tty24 tty51 watchdog0
loop3 null tty25 tty52 zero
loop4 overlay tty26 tty53
loop5 ptmx tty27 tty54
loop6 pts tty28 tty55
loop7 ram0 tty29 tty56
I'm currently using the cywfmac backport driver for linux kernel 6.1 (murata hedorah branch)
Note that my host is using the BlueZ stack.
Any other configuration is required to enable this?
Please advise.
Show Less大家好,
最近想用keil调试cyt2bt73cae这个芯片的程序,使用mtb导出的工程只有单核应用,然后device这里显示
,这种导出的工程直接是CM4的,编译过后能够达到使用CM0启动CM4的效果?如果不能,我应该怎么做?
当我配置了cm0plus以后,cy_m0p_image[]这个数据的含义是什么,需要我手动调用吗?
当我使用导出的keil工程的GPIO中断时,无法进入终端服务函数,这和我没有CM0有关系吗?
希望有人能够帮到我,感谢~
Show LessThere is said that this bright feet + logo a bit unlike is IR Mexico factory production, I can not judge, please gods look at, this is not authentic, thank you!
Show LessHi,
I would like to know of a sample code to write few bytes to an ISSI 128 MBits of nor flash memory and also basic communication pin andsetup for XMC71000D.
When i setup the memory with xmc7100D at P13 (SCB-SPI) the spi_initialization returns an error. how do i check the device id for this flash memory (ISSI;25LP128- jedec id : [9D6018])
best,
PA
Show LessHi everyone, I am trying to read the battery data from TLE9012DQU without using the default hex file. I have written the following function to send commands and receive data based on UART hello world program. But I am not receiving any data. What am I missing? I am not even able to print anything.
void send_receive_ASCLIN_UART_message(void){
Ifx_SizeT r_count=5;
uint8 transmitData0[1] = {0xaa};
Ifx_SizeT g_count0 = sizeof(transmitData0);
IfxAsclin_Asc_write(&g_ascHandle, transmitData0, &g_count0, TIME_INFINITE); /* Transmit data via TX */
IfxAsclin_Asc_read(&g_ascHandle, g_rxData, &r_count, TIME_INFINITE);
//printf("%x",g_rxData[0]);
uint8 transmitData01[6] = {0x1e, 0x80, 0x3d, 0x00, 0x7f};
Ifx_SizeT g_count01 = sizeof(transmitData01);
IfxAsclin_Asc_write(&g_ascHandle, transmitData01, &g_count01, TIME_INFINITE); /* Transmit data via TX */
IfxAsclin_Asc_read(&g_ascHandle, g_rxData, &r_count, TIME_INFINITE);
//printf("%x",g_rxData[0]);
uint8 transmitData1[5] = {0x1e, 0x80, 0x36, 0x00, 0x01};
Ifx_SizeT g_count1 = sizeof(transmitData1);
//printf("%x\n",transmitData1[0]);
IfxAsclin_Asc_write(&g_ascHandle, transmitData1, &g_count1, TIME_INFINITE); /* Transmit data via TX */
IfxAsclin_Asc_read(&g_ascHandle, g_rxData, &r_count, TIME_INFINITE);
printf("%x %x\n",g_rxData[0],g_rxData[1]);
uint8 transmitData3[5] = {0x1e, 0x81, 0x01, 0x0f, 0xff};
Ifx_SizeT g_count3 = sizeof(transmitData3);
IfxAsclin_Asc_write(&g_ascHandle, transmitData3, &g_count3, TIME_INFINITE); /* Transmit data via TX */
IfxAsclin_Asc_read(&g_ascHandle, g_rxData, &r_count, TIME_INFINITE);
printf("%x %x",g_rxData[0],g_rxData[1]);
uint8 transmitData4[5] = {0x1e, 0x81, 0x0b,0x00,0x00};
Ifx_SizeT g_count4 = sizeof(transmitData4);
IfxAsclin_Asc_write(&g_ascHandle, transmitData4, &g_count4, TIME_INFINITE); /* Transmit data via TX */
IfxAsclin_Asc_read(&g_ascHandle, g_rxData, &r_count, TIME_INFINITE);
printf("%x %x",g_rxData[0],g_rxData[1]);
uint8 transmitData5[3] = {0x1e, 0x01, 0x0b};
Ifx_SizeT g_count5 = sizeof(transmitData5);
IfxAsclin_Asc_write(&g_ascHandle, transmitData5, &g_count5, TIME_INFINITE); /* Transmit data via TX */
IfxAsclin_Asc_read(&g_ascHandle, g_rxData, &r_count, TIME_INFINITE);
printf("%x %x",g_rxData[0],g_rxData[1]);
uint8 transmitData6[5] = {0x1e, 0x81, 0x18,0xee,0x21};
Ifx_SizeT g_count6 = sizeof(transmitData6);
IfxAsclin_Asc_write(&g_ascHandle, transmitData6, &g_count6, TIME_INFINITE); /* Transmit data via TX */
IfxAsclin_Asc_read(&g_ascHandle, g_rxData, &r_count, TIME_INFINITE);
printf("%x %x",g_rxData[0],g_rxData[1]);
uint8 transmitData7[3] = {0x1e, 0x01, 0x24};
Ifx_SizeT g_count7 = sizeof(transmitData7);
IfxAsclin_Asc_write(&g_ascHandle, transmitData7, &g_count7, TIME_INFINITE); /* Transmit data via TX */
IfxAsclin_Asc_read(&g_ascHandle, g_rxData, &r_count, TIME_INFINITE);
printf("%x %x",g_rxData[0],g_rxData[1]);
uint8 transmitData8[3] = {0x1e, 0x01, 0x23};
Ifx_SizeT g_count8 = sizeof(transmitData8);
IfxAsclin_Asc_write(&g_ascHandle, transmitData8, &g_count8, TIME_INFINITE); /* Transmit data via TX */
IfxAsclin_Asc_read(&g_ascHandle, g_rxData, &r_count, TIME_INFINITE);
printf("%x %x",g_rxData[0],g_rxData[1]);
uint8 transmitData9[3] = {0x1e, 0x01, 0x22};
Ifx_SizeT g_count9 = sizeof(transmitData9);
IfxAsclin_Asc_write(&g_ascHandle, transmitData9, &g_count9, TIME_INFINITE); /* Transmit data via TX */
IfxAsclin_Asc_read(&g_ascHandle, g_rxData, &r_count, TIME_INFINITE);
printf("%x %x",g_rxData[0],g_rxData[1]);
}
Show Lesshi, while building the project am getting following error.
make[1]: *** [../mtb_shared/core-make/release-v3.0.3/make/core/build.mk:435: C:/DemoProject/build/CY8C6245LQI/Release/AIController-Psoc6.elf] Error 1
make: *** [../mtb_shared/core-make/release-v3.0.3/make/core/main.mk:376: secondstage_build] Error 2
I tried reinstalling the Modustoolbox, also corrected the path of Environment variable, but nothing seems to be working.
Show LessHi
Is there anywhere I can find S-Parameter models for the the BGSA14GN10 RF switch?
Best regards
您好,各位工程师,我们在测试3KW功率板的时候出现炸机问题,我们猜测是过电压或过电流导致,如何导致的还未确定,请大家能帮忙分析一下。这是什么原因导致的,求解答。
测试环境: 进行电机对拖实验,测试3KW功率板。当测试电机测试到转矩值为95%,NTC温度为100度时,测试电机的功率板发生爆炸。IGBT使用的开关频率是16KHz,母线电压为530V,IGBT是FS35R12W1T7,驱动芯片是IR2214SS,参考的是EVAL-M1-IR2214电路。
下图是损坏的IGBT,六个IGBT都已经损坏变黑,U-H的IGBT中间炸开一个洞,除了V-H的续流二极管损坏,其他续流二极管还是正常的。IGBT的C极与G极未短路。
下图的红色圈子中的是U相的IR2214V,V相的IR2214和W相的IR2214,
黄色圈子中的是下臂的开通、关断、软关断电阻和地上的1R电阻,
绿色圈子中的是上臂的开通、关断、软关断电阻,
蓝色圈子中的是地上打的火光。
下图的红色圈子中的是两个BAT54S-E3-08二极管,
黄色圈子中的是四个BAS16J,115二极管,
绿色圈子中的是U-H、V-H、W-H地上的1R电阻(从右到左)
U相的IR2214的壳体炸开,对应上下臂的BAT54S-E3-08二极管的Pin1出现较为明显的炸开溅射,上下臂地上的1R电阻未损坏。
U-L地下方出现火光,引脚上的锡出现熔化的迹象。
大部分的开通、关断和软关断的电阻损坏阻值变大,Vge之间的10K电阻损坏阻值变小。
四个BAS16J,115二极管都出现损坏,自举电路的二极管也出现损坏。
V相的IR2214的Pin20 HON炸飞,Pin19 Vs烧的发黑,Pin19附近芯片壳体翘起,V-H的220R(软关断电阻)和10R(关断电阻)的电阻表面烧的暗淡变色。
V-H的BAT54S-E3-08二极管的三脚的锡出现熔化,Pin3的壳体出现炸开,V-H地下方出现火光,V-H地上的1R电阻损坏(有灼烧变色的痕迹)。
V-L的BAT54S-E3-08二极管的三脚的锡出现熔化,Pin1翘起,V-L地上的1R电阻未损坏。
V-H的开通、关断和软关断的电阻损坏阻值变大,V-L的开通、关断和软关断的电阻未损坏。
Vge之间的10K电阻损坏阻值变小。
四个BAS16J,115二极管都出现损坏,自举电路的二极管也出现损坏。
W相的IR2214的Pin19 Vs炸飞。
W-H的BAT54S-E3-08二极管的Pin3的壳体被炸开,W-H地上的1R电阻损坏(有灼烧变色的痕迹)。
W-L的BAT54S-E3-08二极管的外壳无明显问题,但是已经损坏,直通,W-L地上的1R电阻未损坏。
大部分的开通、关断和软关断的电阻损坏阻值变大,W-L的Vge之间的10K电阻损坏阻值变小,W-H的Vge之间的10K电阻未损坏。
四个BAS16J,115二极管都出现损坏,自举电路的二极管也出现损坏。
Show Less