If I set the Program.stacksize to 768 everything works fine. If I change the stack size to 1024 whenever I plug in the USB cable I get the following error. ti.sysbios.family.arm.m3.Hwi: line 1087: E_hardFault: FORCED ti.sysbios.family.arm.m3.Hwi: line 1164: E_busFault: IMPRECISERR: Delayed Bus Fault, exact addr unknown, address: e000ed38 Exception occurred in ISR thread at PC = 0x000087de. Core 0: Exception occurred in ThreadType_Hwi. Hwi name: {unknown-instance-name}, handle: 0x20000bb8. Hwi stack base: 0x200031e8. Hwi stack size: 0x400. R0 = 0x00000000 R8 = 0x00000000 R1 = 0x00000041 R9 = 0x0000d768 R2 = 0x00000001 R10 = 0x0000d760 R3 = 0x200034e8 R11 = 0x0000d764 R4 = 0x20002f0c R12 = 0x00000000 R5 = 0xffffffff SP(R13) = 0x200034d8 R6 = 0x00000001 LR(R14) = 0x00005ffb R7 = 0xffffffff PC(R15) = 0x000087de PSR = 0x6100503a ICSR = 0x00423003 MMFSR = 0x00 BFSR = 0x04 UFSR = 0x0000 HFSR = 0x40000000 DFSR = 0x0000000a MMAR = 0xe000ed34 BFAR = 0xe000ed38 AFSR = 0x00000000 Terminating execution... ti.sysbios.family.arm.m3.Hwi: line 1087: E_hardFault: FORCED ti.sysbios.family.arm.m3.Hwi: line 1199: E_usageFault: INVSTATE: Invalid EPSR and instruction combination ti.sysbios.family.arm.m3.Hwi: line 1164: E_busFault: IMPRECISERR: Delayed Bus Fault, exact addr unknown, address: e000ed38 Exception occurred in ISR thread at PC = 0x0000d760. Core 0: Exception occurred in ThreadType_Main. Main name: main(), handle: 0x0. Main stack base: 0x200031e8. Main stack size: 0x400. R0 = 0x20002f0c R8 = 0x00000000 R1 = 0xffffffff R9 = 0x0000d768 R2 = 0x00000001 R10 = 0x0000d760 R3 = 0xffffffff R11 = 0x0000d764 R4 = 0x20002f0c R12 = 0x00000000 R5 = 0xffffffff SP(R13) = 0x200034b8 R6 = 0x00000001 LR(R14) = 0x0000d768 R7 = 0xffffffff PC(R15) = 0x0000d760 PSR = 0x0000d764 ICSR = 0x00423003 MMFSR = 0x00 BFSR = 0x04 UFSR = 0x0002 HFSR = 0x40000000 DFSR = 0x0000000b MMAR = 0xe000ed34 BFAR = 0xe000ed38 AFSR = 0x00000000 Terminating execution...
↧
Forum Post: RE: Task cannot be created in the USB example for Tiva EK-TM4C1294xl
↧
Forum Post: RE: ADC Drivers
Are the ADC drivers thread safe, because I have read in one of the documents (which one i have forgotten) that Tivaware is not thread safe and cannot be used in task context. correct me I am wrong Narendra
↧
↧
Forum Post: RE: am335x sdk 1.1.0.8 ethernet/IP ACD question
Hi Adrien, You need to get the ACD stack from Molex to get the ACD features working in Ethernetip example application. It does not come with Molex EIP stack i guess. Regards, Prajith
↧
Forum Post: XDS200 cannot connect to ARM core 1 in No Boot/DSP JTAG Little Endian Mode
Hi Team, I am working on EVMK2E V1.0.2.2 board I got this board and I found that by default this version of EVMK2E will boot U-boot from SPI NOR and Kernel, File system from NAND. ******************************************************************************************************** Now I want to boot U-boot and other kernel images which I build through Yocto Arago Project. I tried to Boot throug CCS software with XDS200 JTAG Emulator support I followed the instructions mentioned in the User Guide in the link http://processors.wiki.ti.com/index.php/MCSDK_User_Guide_for_KeyStone_II and in the link : http://processors.wiki.ti.com/index.php/MCSDK_UG_Chapter_Exploring#Installation_Guide to install CCS. I installed CCSv5(ccs_setup_5.5.0.00077) in Windows 7 64 bit PC successfully. Once after installtion is done i installed the "ti_emupack_keystone2_setup_1.1.1.0". ****************************************************************************************************** Once CCS installation is done, I powered on the EVM board, Once after BOOT COMPLETE message is displayed in EVM LCD I opened CCS appplication and followed the below steps from http://processors.wiki.ti.com/index.php/MCSDK_UG_Chapter_Exploring#Loading_and_Running_U-Boot_on_EVM_through_CCS and I loaded the U-boot and I verified the PC register also. But when I click "Resume" it got crashed and u-boot prompt didn't turn up. I attached the file "corruption.txt" for reference Then I realised I didnt set the DIP Switch to No boot mode/JTAG DSP Little endian and I did the above steps with SPI NOR ARM Master boot So I changed the DIP switch to No boot mode and I turned on EVM and CCS But when I tired to connect the Target this time. I got the below error message Error connecting to the target: Connect to PRSC failed And after this I couldn't able to connect to the Target(Texas Instruments XDS2xx USB Onboard Emulator_0/arm_A15_1) in No Boot Mode I can able to launch the Target configuration but i couldn't able to connect the target alone But in "SPI NOR ARM Master mode" I can able to connnect to the Target ( Texas Instruments XDS2xx USB Onboard Emulator_0/arm_A15_1 ) I need to to boot U-boot through CCS. So please help me with this. I installed CCSv6 and tried and it also gives the same issue. (Please visit the site to view this file)
↧
Forum Post: U-Boot Failure on Board: DRA7xx
Code hangs in u-boot after these messages OMAP SD/MMC: 0 reading u-boot.img reading u-boot.img U-Boot 2013.04 (Jun 25 2015 - 19:30:24) CPU : DRA752 ES1.1 Board: DRA7xx I2C: ready DRAM: 1.5 GiB WARNING: Caches not enabled MMOMAP SD/MMC: 0, OMAP SD/MMC: 1 Using default environment The same u-boot code is working fine with VAYU EVM. After debugging u-boot code i have found that after printing puts("Using default environment\n\n"); it hangs in the function himport_r(&env_htab, (char *)default_environment, sizeof(default_environment), '\0', flags, 0, NULL). Within the himport_r (/*hashtable.c*/) function hangs after if (!drop_var_from_set(name, nvars, localvars)) continue; What can be the possible reasons and soluions? We have designed prototype board similar to the VAYU EVM. We are using the GLSDK . Thanks & Regards, Subbaiah.N.V
↧
↧
Forum Post: RE: TIRTOS 2.10 to 2.12 SPI CHANGES CAUSING TASK TO FREEZE
Barry, Can you please provide us an example to reproduce the issue? Thanks.
↧
Forum Post: RE: TIRTOS 2.10 to 2.12 SPI CHANGES CAUSING TASK TO FREEZE
Hello Vikram I am not sure how much of the other tasks being active is required to cause the issue to occur. I haven't cut my code back to a minimum to see at what point it will operate correctly and at what point it will fail. Below is the function call that locks up and freezes waiting for the SPI_Transfer to complete. If I set the transferTimeout to say 1000 I will see intermittent 1000ms pauses in my animation. This task that is freezing is simply updating the LCD write buffer and writing that to the display. This gives me animated icons for the operator, so it is easy to see the freezing. If I leave transferTimeout at 0 the LCD task will just halt and the other tasks all run fine. I am not using the callback function for transfer complete. When the task halts it will be waiting for the transfer complete mutex. Below is how I initialise the SPI and how I call it and all my SPI initialisation tables in my board definition. Whilst I setup for 3 possible SSI only the serial flash and the LCD are used. The serial flash only runs a few times at start up to check the flash is present as I haven't finished the flash code yet. LCD runs continuously on a 50ms update. //***************************************************************************** // LCD SPI interface items //***************************************************************************** static SPI_Handle LCD_SPI; static SPI_Transaction lcdTransaction; static UChar lcdRxBuffer[MAX_LCD_WR]; UInt lcdTransferOK; #ifdef ST7565_DIRTY_PAGES uint8_t ST7565_dirty_pages; #endif //***************************************************************************** // Writes a data word to the LCD. //***************************************************************************** static void WriteBLock ( UChar * ui8Data, UChar Size) { // Address HIGH - DATA SetLCD_A0; // Limit to size of buffer if (Size > MAX_LCD_WR) Size = MAX_LCD_WR; // Initialise LCD SPI transaction structure lcdTransaction. count = Size; lcdTransaction. txBuf = ( Ptr )ui8Data; lcdTransaction. rxBuf = ( Ptr )lcdRxBuffer; // Initiate SPI transfer lcdTransferOK = SPI_transfer (LCD_SPI, &lcdTransaction); } //***************************************************************************** // Writes a command byte to the LCD. //***************************************************************************** static void WriteCommand ( uint8_t ui8Data) { // Address LOW - COMMAND ClrLCD_A0; // Initialise LCD SPI transaction structure lcdTransaction. count = 1; lcdTransaction. txBuf = ( Ptr )&ui8Data; lcdTransaction. rxBuf = ( Ptr )lcdRxBuffer; // Initiate SPI transfer lcdTransferOK = SPI_transfer (LCD_SPI, &lcdTransaction); } // =========================================================== // ST7565_init - Initialises the LCD interface using SPI3 // =========================================================== void ST7565_init ( char StartSpi) { uint32_t ui32ClockMS; SPI_Params lcdSpiParams; if (StartSpi) { // Initialise SPI handle with Master mode SPI_Params_init (&lcdSpiParams); lcdSpiParams. mode = SPI_MASTER ; lcdSpiParams. frameFormat = SPI_POL1_PHA1 ; // clock high in idle, clock on rising edge lcdSpiParams. transferMode = SPI_MODE_BLOCKING ; // lcdSpiParams.transferTimeout = 250; // BAZ: Sanity timer added in 2.12 because SPI was freezing lcdSpiParams. transferTimeout = 10; // BAZ: Sanity timer added in 2.12 because SPI was freezing lcdSpiParams. dataSize = 8; lcdSpiParams. bitRate = 1000000; // 1MHz clocking lcdSpiParams. transferCallbackFxn = NULL; LCD_SPI = SPI_open (Board_SPI3, &lcdSpiParams); if (LCD_SPI != NULL) { System_printf( "LCD SPI initialised\n" ); System_flush(); } } // Determine the number of system clock cycles in 1mS ui32ClockMS = CYCLES_FROM_TIME_US(ui32SysClock, 1000); // Divide by 3 to get the number of SysCtlDelay loops in 1mS. ui32ClockMS /= 3; SetLCD_A0; // Address line high SysCtlDelay (10 * ui32ClockMS); // Delay for 10ms. ClrLCD_RST; // Activate LCD RESET SysCtlDelay (250 * ui32ClockMS); // Delay for 250ms SetLCD_RST; // RESET OFF SysCtlDelay (250 * ui32ClockMS); // Delay for 250ms WriteCommand(ST7565_CMD_BIAS_9); // Set LCD Bias WriteCommand(ST7565_CMD_VERTICAL_REVERSE); // Common Direction Select, bit3=1,reverse direction=0,normal WriteCommand(ST7565_CMD_POWER_CONTROL | ST7565_PWR_INTERNAL_CONV); SysCtlDelay (20 * ui32ClockMS); // Delay for 20ms. WriteCommand(ST7565_CMD_POWER_CONTROL | ST7565_PWR_INTERNAL_CONV | ST7565_PWR_INTERNAL_REG); SysCtlDelay (20 * ui32ClockMS); // Delay for 20ms. WriteCommand(ST7565_CMD_POWER_CONTROL | ST7565_PWR_INTERNAL_CONV | ST7565_PWR_INTERNAL_REG | ST7565_PWR_INTERNAL_FOL); SysCtlDelay (20 * ui32ClockMS); // Delay for 20ms. WriteCommand(ST7565_CMD_RESISTOR | 0x04); // Set ra/rb 0x25 WriteCommand(ST7565_CMD_VOLUME_MODE); // Set Contrast WriteCommand(39); // Contrast = 39 (Range 0..63) WriteCommand(ST7565_CMD_DISPLAY_ON); // Display ON ST7565_blank(); // Blank the display ST7565_flip_screen(1); // set the screen orientation to suit standard ASE position SetLCD_BL; // turn on the LCD backlight } /* SPI objects */ SPITivaDMA_Object spiTivaDMAobjects[ A30307P26_SPICOUNT ]; #if defined(__TI_COMPILER_VERSION__) #pragma DATA_ALIGN(spiTivaDMAscratchBuf, 32) #elif defined(__IAR_SYSTEMS_ICC__) #pragma data_alignment=32 #elif defined(__GNUC__) __attribute__ ((aligned (32))) #endif uint32_t spiTivaDMAscratchBuf[ A30307P26_SPICOUNT ]; /* SPI configuration structure, describing which pins are to be used */ const SPITivaDMA_HWAttrs spiTivaDMAHWAttrs[ A30307P26_SPICOUNT ] = { { SSI0_BASE, INT_SSI0, (~0), &spiTivaDMAscratchBuf[0], 0xFFFFFFFF, UDMA_CHANNEL_SSI0RX, UDMA_CHANNEL_SSI0TX, uDMAChannelAssign , UDMA_CH10_SSI0RX, UDMA_CH11_SSI0TX }, { SSI1_BASE, INT_SSI1, (~0), &spiTivaDMAscratchBuf[1], 0, UDMA_CHANNEL_SSI1RX, UDMA_CHANNEL_SSI1TX, uDMAChannelAssign , UDMA_CH24_SSI1RX, UDMA_CH25_SSI1TX }, { SSI3_BASE, INT_SSI3, (~0), &spiTivaDMAscratchBuf[2], 0, UDMA_SEC_CHANNEL_TMR2A_14, UDMA_SEC_CHANNEL_TMR2B_15, uDMAChannelAssign , UDMA_CH14_SSI3RX, UDMA_CH15_SSI3TX } }; const SPI_Config SPI_config[] = { {&SPITivaDMA_fxnTable, &spiTivaDMAobjects[0], &spiTivaDMAHWAttrs[0]}, {&SPITivaDMA_fxnTable, &spiTivaDMAobjects[1], &spiTivaDMAHWAttrs[1]}, {&SPITivaDMA_fxnTable, &spiTivaDMAobjects[2], &spiTivaDMAHWAttrs[2]}, {NULL, NULL, NULL}, }; /* * ======== A30307P26_initSPI ======== */ Void A30307P26_initSPI (Void) { // SSI0 - MicroSD SysCtlPeripheralEnable (SYSCTL_PERIPH_SSI0); GPIOPinConfigure (GPIO_PA2_SSI0CLK); GPIOPinConfigure (GPIO_PA3_SSI0FSS); GPIOPinConfigure (GPIO_PA4_SSI0XDAT0); GPIOPinConfigure (GPIO_PA5_SSI0XDAT1); GPIOPinTypeSSI (GPIO_PORTA_BASE, GPIO_PIN_2 | GPIO_PIN_3 | GPIO_PIN_4 | GPIO_PIN_5); // SSI1 - Serial Flash SysCtlPeripheralEnable (SYSCTL_PERIPH_SSI1); GPIOPinConfigure (GPIO_PB5_SSI1CLK); GPIOPinConfigure (GPIO_PB4_SSI1FSS); GPIOPinConfigure (GPIO_PE4_SSI1XDAT0); GPIOPinConfigure (GPIO_PE5_SSI1XDAT1); GPIOPinTypeSSI (GPIO_PORTB_BASE, GPIO_PIN_4 | GPIO_PIN_5); GPIOPinTypeSSI (GPIO_PORTE_BASE, GPIO_PIN_4 | GPIO_PIN_5); // SPI3 - The Mono LCD SPI Port SysCtlPeripheralEnable (SYSCTL_PERIPH_SSI3); GPIOPinConfigure (GPIO_PQ0_SSI3CLK); GPIOPinConfigure (GPIO_PQ1_SSI3FSS); // Hardware control of CS GPIOPinConfigure (GPIO_PQ2_SSI3XDAT0); GPIOPinConfigure (GPIO_PQ3_SSI3XDAT1); GPIOPinTypeSSI (GPIO_PORTQ_BASE, GPIO_PIN_0 | GPIO_PIN_1 | GPIO_PIN_2 | GPIO_PIN_3); A30307P26_initDMA(); SPI_init (); }
↧
Forum Post: Port FreeRTOS proyect to TI-RTOS
Hi everybody, I've modified a SDK example proyect from Simplelink SDK in order to send photos over WiFi. The example application is tftp_client. The case is that the entire proyect consist in a camera taking photos and sending them over WiFi, and I've done the camera code using TI-RTOS because of the driver APIs. The example code was made using FreeRTOS and I want to change it to TI_RTOS. Is there any form that I can change it without rewriting the entire application? Thanks in advance!
↧
Forum Post: RE: where to find kernel.release file
Hi, Please refer to the following TI wiki page. processors.wiki.ti.com/.../MCSDK_OMAPL138_User_Guide_Chapter_Exploring You have to mention the compiled kernel path to build SYSLINK as module.
↧
↧
Forum Post: Change screen resolution Android 4.2.2 KitKat on Beaglebone black.
Hi I wanna change screen resolution 800x480 or similer value. How can i change screen resolution Android 4.2.2 KitKat on Beaglebone black?
↧
Forum Post: RE: where to find kernel.release file
Hi Lijo, Would you please attach your complete error logs?
↧
Forum Post: RE: U-Boot Hangs
Hello Prabhakar, Already CONFIG_ENV_IS_NOWHERE is enabled in config file. Earlier CONFIG_SYS_SPL_MALLOC_SIZE=0x100000, i have incresed the size to 0x100FFF. But still u-boot hangs after, reading u-boot.img reading u-boot.img . But why you suspect malloc size, as the same u-boot code is working fine with EVM. Thanks & Regards, Ganesh
↧
Forum Post: RE: XDS200 cannot connect to ARM core 1 in No Boot/DSP JTAG Little Endian Mode
Hi Mohamed, The following are the steps to get the u-boot prompt on K2H / K2E EVM through CCS which is the easiest method. I have attached the necessary screenshots for your reference. 1. Flashing and booting u-boot.bin ====================== The u-boot.bin can be flashed into the EVM through CCS method. 1.1 HW Set up on K2HK EVM: ================== In EVMK2hk, rev 3.0 board, you will find two FTDI -USB connectors. The top one is for the emulator (CCS) and the bottom one is for opening two channels ( one for displaying the u-boot messages and another one is for BMC commands) Connect the USB cables between your host PC where in the CCS is installed and the K2HK EVM. One for Emulation and the other one for receiving the u-boot messages and the BMC commands. To flash the u-boot.bin, EVM dip switches are to be set for no-boot mode SWITCH Pin1 Pin2 Pin3 Pin4 SW1 Off Off Off On 1.2 CCS set up and u-boot flashing Steps to get u-boot prompt. ================================================== In CCS, navigate to view--> Target configuration--> create new target configuration file --> and open the file. Select the XDS2xx USB emulator as "connection" and " 66AK2H12 " as board/device, save and test connection. Now, launch the target configuration file and open -->view scripting console, you will get a console prompt with "js:>" You might have already installed the MCSDK at windows and you will find the js file at C:/ti/mcsdk_linux_3_00_03_15/host-tools/loadlin/loadlin-evm-uboot.js Connect the coretexA15_1 to the target. In the scripting console, use loadJSfile command to load the "loadlin-evm-kern.js" file. Before loading, openup the js file in CCS and modify the paths of u-boot, kernel like below PATH_LOADLIN = /host-tools/loadlin var pathUboot = PATH_LOADLIN + "/u-boot-keystone-evm.bin"; var pathSKern = PATH_LOADLIN + "/skern-keystone-evm.bin"; loadJSFile C:\ti\mcsdk_linux_3_00_03_15\host-tools\loadlin\loadlin-evm-uboot.js ----> Observe a progress bar which will complete the loading of images given in the "loadlin-evm-uboot.js" ----> Hit the play button in CCS and in the tera term observe the output messages from "u-boot.bin" image ( flashed through CCS just now) and the u-boot prompt like below. -------
↧
↧
Forum Post: RE: TI RTOS with GSM/GPRS stack
Hi, Actually i have to sense the parameters at remote location where there is no internet connectivity means no WiFi and no Ethernet available. so the only option available is GSM/GPRS modem on which i can rely for the communocation so i decided to use QUECTEL M95 GSM Modem for communication now i have to finalize the MCU by which i can sense the parameters along with controlling appliances and can communicate with my server through GSM/GPRS technology (with HTTP Protocol) following parameter i have to sense Temperature, Humidity, current, voltage, motion detection, light etc.... so the idea that i want to implement is that In MCU i want to implement multiple thread on TO RTOS 1. in one thread i want to sense all the parameters 2. in another thread i want to store all the parameters on local SD/MMC 3.in another thread i want to control all the appliances. 4. in another thread i want to communicate with GSM/GPRS Modem wirh HTTP protocol. and i do not need Ethernet, WiFi because i have to communicate with modem through UART and with SD/MMC through SPI so for this idea suggest me any microcontroller.
↧
Forum Post: RE: malloc for c66 dsp
hello Steve I find the memory map... The start of dsp1 is 960a7400 But I edit the size in """""C:\VISION_SDK_02_05_00_00\ti_components\drivers\starterware_01_02_04_05\examples\sbl_multicore_mbx\tda2xx""" so... I guess I edited wrong file...
↧
Forum Post: on-the-fly change of kernel between USB host to USB device
Hello, I am using DM8148 USB. As I understand OTG is not supported with it. Therefore when we use USB device mode, we use the kernel which was build with the menuconfig in usb device mode, and when we use the device in host mode we use the kernel build for host usb. I would like to ask if there is a way that we can do this on-the-fly, i.e. when we need the device, we somehow work with kernel device mode, and when we need host, we work with kernel host mode. Thanks for any suggestions. Ran
↧
Forum Post: RE: DVR RDK 8168 DSP, Video and VPSS
Balaji, [quote user="Balaji Govindarajan"]I have bought CCSv6 from TI and also Blackhawk USB 560v2 system trace emulator. It is showing in CCS as disconnected when we connected between CCS and DVR RDK8168 by USB emulator. Is there any way to fix this problem?[/quote] Could you please let us know how this is related to the original question of this e2e subject? BR Pavel
↧
↧
Forum Post: RE: XDS200 cannot connect to ARM core 1 in No Boot/DSP JTAG Little Endian Mode
Hi Shankari, Thank you so much for your reply. I did as you asked me to do, But still I got this error message "arm_A15_1: Error connecting to the target: Connect to PRSC failed" Then I realized that I have been connecting the wrong target core ************************************************************************************************************* First of all, In the Code Composer Studio - Device Debugging menu, For 66AK2xx devices The core name I think I should connect is Texas Instruments XDS2xx USB Emulator_0/arm_15_0 instead of Texas Instruments XDS2xx USB Emulator_0/arm_15_1 Because I think there is a core name difference betweeen 66AK2xx devices and other devices(Ex: TCI6638K2K device) 66AK2E05 Device Debugging core options TCI6638K2K Device Debugging core options Note : 1st image is the core options for 66AK2E05 device and 2nd image is TCI6638K2K device As you can see, the TCI6638K2K device core name stands as coretexA15_1, coretexA15_3, coretexA15_5, coretexA15_7 whereas in 66AK2xx devices its arm_A15_0, arm_A15_1, arm_A15_2, arm_A15_3 So I should select arm_A15_0 core for 66AKExx devices ??? If I select that core I can able to load U-boot binary successfully from CCS :) Please clarify me whether the things I said regarding the core selection is correct and correct me if I am wrong. Cheers. Thank you sooo much for the steps. Regards Sarjoon.
↧
Forum Post: Can't run the vpif_test_mmap_loopback on my omapl138 board
I have config the CONFIG_VIDEO_DAVINCI_VPIF_CAPTURE and CONFIG_VIDEO_DAVINCI_VPIF_DISPLAY. And when I run the app , it will show follow message then exit. vpif_display: dma_alloc_coherent size 4149248 failed. I show my memory with free command, the result are: root@arago :~# free total used free shared buffers Mem: 92696 17528 75168 0 0 Swap: 0 0 0 Total: 92696 17528 75168 and the result of cat /proc/buddyinfo as follows: root@arago :~# cat /proc/buddyinfo Node 0, zone DMA 3 10 10 20 5 4 0 1 1 3 25 it's seem that the memory is enough. BTW, the DVSDK is ti-dvsdk_omapl138-evm_4_02_00_06.
↧
Forum Post: RE: DVR RDK 8168 DSP, Video and VPSS
This has been double posted and answered in the below e2e thread: e2e.ti.com/.../432078
↧