Part Number: TMS320DM6435
Hi Team,
May I ask for your confirmation? Our customer wants to know if he can use the XDS510 USB Probe to debug an old TMS320DM6435 DSP?
I already check other USB debug probe like XDS200 in the product folder of TMS320DM6435. But also wants to confirm the concern of our customer as stated above.
We hope to received your response. Thank you so much.
Kind regards,
Gerald
Part Number: TMS320DM6435
Hi Team,
The customer uses DM6435 as the CPU and NDK for the TCP/IP stack.
They developed their application with the Ethernet/IP communication.
According to them, It has been necessary to determine whether a destination IP address is broadcast or unicast in UDP broadcast reception from ODVA Conformance Test CT18 latest version.
Example: Your IP address is 192.168.0.10
Source (test tool) IP address as 192.168.0.50.
① Send (a) and (B) in UDP broadcasts from 192.168.0.50.
(A) Source IP: 192.168.50 → Destination IP: 192.168.0.255
(B) Source IP: 192.168.50 → Destination IP: 192.168.0.10
② 192.168.0.10 has to judge the difference of a destination IP (receive IP) between 192.168.0.255 and 192.168.0.10.
Is it possible to get a destination IP address when a UDP broadcast packet was received in the NDK?
Currently, when a packet received with recvfrom() is read, the source IP address, Receive data can be retrieved, but not the receive IP address.
Do you have any idea or solution for this requirement?
Thanks and Best regards,
Kuerbis
Part Number: TMS320DM6435
Hi everybody ,
does this CPU supports watchpoint , I mean to stop when writing/reading in selected memory area ?
I need to debug a code and this will help a lot .
any suggestion ?
thank you
bets regards
Carlo
Part Number: TMS320DM6435
Hi all,
we're having some problems with a new pcb design for the TMS320DM6435. When connecting through JTAG all seems fine until loading the binary file due to an endianness mismatch.
C64XP_0: GEL: File: C:\test.out Does not match the target endianness, not loaded. Check project build options and target configuration file (ccxml).
CCS shows that the device is in BE mode, which doesn't seem right after reading that the processor only supports little endian. I've already read on the forum that the DM6437 actually has the hardware capability to support big endian, and somehow we managed to activate the big endian mode and don't know how to disable it. Is there any pin configuration which activates the big endian mode, but isn't documented? For debugging purposes we tried to interact with the DRAM and NOR flash, and both seems fine (DRAM write operations in 32-bit mode are in BE).
We already use the DM6435 in some products and it works fine with a very similar hardware design.
Part Number: TMS320DM6435
Tool/software: Code Composer Studio
Hi, All!
The problem with the UART: speed 115200, after some time, the data ceases to be transmitted, although the sending function returns that in ok
To start the transfer, you need to restart the chip, re-initializing the driver does not help.
UART stops working after about 7-8 hours when sending data 800-1000 kb at summ , while there were 500 transactions TX-RX
================
uart0DevParams.inputFreq = PSP_UART_MODULE_CLOCK;
uart0DevParams.fifoEnable = TRUE;
uart0DevParams.opMode = PSP_OPMODE_INTERRUPT; uart0DevParams.loopbackEnabled = FALSE;
uart0DevParams.baudRate = PSP_UART_BAUD_RATE_115_2K;
uart0DevParams.stopBits = PSP_UART_NUM_STOP_BITS_1;
uart0DevParams.charLen = PSP_UART_CHARLEN_8;
uart0DevParams.parity = PSP_UART_PARITY_NONE;
uart0DevParams.rxThreshold = PSP_UART_RX_TRIG14;
uart0DevParams.fc.fcType = PSP_UART_FC_TYPE_NONE;
uart0DevParams.fc.fcParam = PSP_UART_FC_NONE;
Sys/Bios: 6.41.0.26
DSP/BIOS UART Device Driver
Release 1.10.03
================
Part Number: TMS320DM6435
Good afternoon.
We use DM6435 + NDK_2.24.3.35 + BIOS_6.41.4.54 + PSPDRIVERS_1_10_03
In some networks, the NDK stops receiving requests, the device becomes unavailable over the network, but it does work.
It helps only reboot the device.
How can I track the failure and restart the NDK without restarting the device?
Part Number: TMS320DM6435
Tool/software: Code Composer Studio
Hello
I try to import a static library project in CCS7 which works fine under CCS6, but the import fails (see dialog) and I get an empty project file in project explorer.
Problem are the following entry:
<listOptionValue builtIn="false" value="OUTPUT_TYPE=bios5Application:rtscApplication:staticLibrary"/>
If I remove it, or I change it to:
<listOptionValue builtIn="false" value="OUTPUT_TYPE=staticLibrary"/>
I can import the project.
Problem here is, if I import this project against under CCS6 and I change the compiler version, it will create the "bios5Application:rtscApplication:staticLibrary"
again and I can't reimport it under CCS7.
Can you fix the import problem under CCS7?
Thanks and regards
Thomas
