Activity
From 04/01/2016 to 04/30/2016
04/26/2016
- BD 01:20 PM Software Development: RE: ifup / ifdown Equivalent for systemd
- Ben,
Your concern is valid and I don't have a direct answer now. The @ip@ command is the correct one to use to configure the network interfaces, but we haven't explored all of the new ways systemd is integrated with the rest of the sy... - EM 11:04 AM Software Development: RE: Linker memory layout.
- I think these errors have been over come. I'm using the 8000 tcf file. I am able to run the program and debug a little, but the emulator or something keeps resetting/crashing and I have to start from the beginning again. (See the other ...
- JC 10:59 AM Software Development: RE: Linker memory layout.
- Edwin, Did you figure this out?
Some comments from Dave here:
> Could it be trying to use two .cmd files?
> ...
> isn't how things get set up. The external memory for the DSP tends to be in 0xCxxxxxxx somewhere, determined in con... - We are trying to flash our firmware on the MityDSP-L138 to run code from the DDR. We are using the AISGen tool from TI, see the attached config file.
We assume that there is something wrong with the DDR register settings. What are the...
04/22/2016
- SP 10:59 AM Software Development: RE: WFI and Bluetoth support
- I am looking at the Redpine Signals RS9113-NZB.
We may be using it in anther product Using the TI arm file system that has the drivers built in.
The biggest problem is the interface to the Dbric3 and implementing the drivers.
The only... - BD 10:33 AM Software Development: RE: WFI and Bluetoth support
- Steven,
We've integrated multiple Wifi/BT chipsets with our products. In most cases we have to integrate an external driver into the kernel.
Did you have a particular implementation in mind? Did you plan to use an on-board solutio... - Does the Yocto file system support the TI or other vendors wifi and bluetooth on the DBric3?
what is the interface to the processor?
Regards
Steven Poffenbarger
04/21/2016
- I continually get these sort of messages while I try to step through the DSP code. Some times I can debug for a few minutes, other times it seems only a few instructions. I did figure out that all my breakpoints are being reset whenever ...
04/20/2016
- IS 04:58 PM Software Development: RE: No Prompt from Uboot
- Thanks. You got it.
Only way to be sure was to cut the i2c traces on the carrier. Biked over to my partners and got him to test it. Guess what? Cut the I2C and it worked.. I had thought that the "I2C: ready" was the eeprom read and th... - JC 09:02 AM Software Development: RE: No Prompt from Uboot (update)
- Ian St. John wrote:
> ALSO note that I am worried about the message "error reading I2C Configuration Block". Is this some carrier board peripheral it is expecting? I expect the message about no ethernet PHY. We haven't added that to t... - IS 12:37 AM Software Development: RE: No Prompt from Uboot
- I don't have either a second (working) module or a standard carrier board. We couldn't afford them when we started and our finances have not improved noticeably. That is why I am trying to eliminate debugger, host system, etc in diagnosi...
04/19/2016
- GG 05:39 PM Software Development: RE: Any special thing to get new ObjectXXX to work.
- Hi Edwin,
Your project should have a .tcf file. This should define how memory is configured and how large your heap is. Note that most likely you will need to edit this as a text file as CCSv5 does have GUI support for .tcf files.
... - AB 04:35 PM Software Development: RE: No Prompt from Uboot
- Ian,
Can you let us know if the behavior changes when this module is used in the Industrial IO Development Board (80-000268) assuming you have one? I believe all of your testing has been done with/in your own custom carrier board corr... - IS 03:34 PM Software Development: RE: No Prompt from Uboot (baahhh)
- Well, it worked for two or three runs. Now it hangs on the uart initialization? Thinks that the uart is busy with output. Got to be hardware? Too erratic to be software? Software generally goes wrong EVERY time if there is a problem. But...
- IS 12:46 PM Software Development: RE: No Prompt from Uboot (update)
- Imported and ran UBL to CCS 6.1.2. Changed only DEVICE_UART_PERIPHNUM to 1 from 2 in devices_uart.h to get UBL messages out. They do not show up on UART2 when I boot from SPI-NOR FLASH.
It apparently initializes ok, copying u-boot ima...
04/17/2016
- IS 12:51 PM Software Development: RE: No Prompt from Uboot
- Mike,
Thanks for the description. I think your confusion is more about not understanding why it doesn't work (like me), not my description. I probably should not have confused the issue by adding the issues from debugging. But that MI... - MW 08:17 AM Software Development: RE: No Prompt from Uboot
- Hello,
So I'm struggling a bit to get the full picture of what is going on.
Are you saying that you are running the sfh* program to put both the Critical Link supplied uBoot.bin (second stage) and the UBL_SPI_MEM.ais (first stage) ...
04/16/2016
- IS 06:21 PM Software Development: RE: No Prompt from Uboot
- Uboot won't load (SPI mem = 0, i.e. says file too big on load of UBL)
Backup code was NOT the solution. Recent code (blinking led on GPIO pin with simple loop delay) was loaded with newer code. Works SOMETIME. i.e didn't work, tried to ... - IS 02:09 PM Software Development: RE: No Prompt from Uboot (update)
- I found and old backup where SpiWriter still works. Got my application code loaded into SPI NOR flash. I will try to load u-boot with it and see if I get a prompt.
04/15/2016
- I am new'ing an object and stepping through the assembly I end up in SYS_error with an error of 1 and a message of "MEM". (I think that was the word...).
I tried some simple "new int" and they worked ok. Without more work, I'm not sure... - BA 03:08 PM Software Development: RE: ifup / ifdown Equivalent for systemd
- Well, I found something that works, but it doesn't seem very "clean" or symmetrical. I found the following to bring down eth0:
$ ip link set dev eth0 down
This succeeds in shutting down the eth0 device. However when it's time... - Hello,
In the new ALPHA Release 2016.01 filesytem, what is the "systemd way" of performing ifdown eth0 and ifup eth0?
- ifup and ifdown expect an /etc/network/interfaces file -- which doesn't exist in the systemd configuration.
- ... - Background:
I have a custom carrier board utilizing a 1808-FX-225-RC SOM (AM1808 only). Compiling using CCS 6.1.2. I have been trying to set up a 'to the metal' application which does not use Linux u-boot. I have gotten a standalone pro... - DS 10:04 AM Software Development: RE: Problem using XDS200 USB emulator.
- As I mentioned, you may be able to use the debugger to load the application. I believe you should load
some DSP code using the ARM first to initialize the DSP processor. Then after you connect the debugger you
can load your applicati...
04/13/2016
- EM 08:41 AM Software Development: RE: Problem using XDS200 USB emulator.
- Dave,
Thanks for the reply.
1. Easier said than done ;)... The project is very "integrated". I have pared it down to something basic.
2. For now I have only DSP code and no comms back to the ARM.
For what I have now, if I right cl...
04/12/2016
- DS 05:44 PM Software Development: RE: Problem using XDS200 USB emulator.
- Hello Edwin,
Those steps do appear correct.
All project I have done on the L138 have used dsplink to communicate between the ARM and DSP. To do this,
the ARM code must load the DSP code.
There may a couple ways to get past you... - EM 04:11 PM Software Development: RE: Problem using XDS200 USB emulator.
- Yes, I could step through the HelloWorld app. Is there anything else that might run before the main()?
I have changed all the objects from 'static' declarations to dynamic 'new's. Still no luck.
Well, all the ones in main.cpp. There a... - DS 02:20 PM Software Development: RE: Problem using XDS200 USB emulator.
- Hello Edwin,
I agree that since the debugger is looking for utl_halt.c something has gone wrong before main.
Obviously, try disabling those other things and then if it works, start putting them back.
When you did succesfully debug... - EM 01:50 PM Software Development: RE: Problem using XDS200 USB emulator.
- I have tried to debug our main application. I copied the "waiting" loop from the Hello World app to the main. Whenever I try to connect to the target I receive this error:
Can't find a source file at "/db/vtree/library/trees/cuda/cuda... - EM 10:16 AM Software Development: RE: Problem using XDS200 USB emulator.
- Well sort of debug. It hit the break point, I changed the waitForMe variable and stepped one line. But after stepping again, the screen goes "grey" and appears to lock. These messages appear:
C674X_0: Can't Single Step Target Program
... - JC 09:46 AM Software Development: RE: Problem using XDS200 USB emulator.
- Edwin McKay wrote:
> To get at least pass the "Test Connection" I installed the drivers. I must have missed that step when I installed CCS 5.
Gotcha, yeah thats an easy screen to miss.
> ...
Yes
> For "the debugger is set to load sym... - EM 09:44 AM Software Development: RE: Problem using XDS200 USB emulator.
- To get at least pass the "Test Connection" I installed the drivers. I must have missed that step when I installed CCS 5.
What are steps to debug a DSP application?
For instance how would I debug the "Hello World DSP" program? Do I r...
04/11/2016
- JC 03:29 PM Software Development: RE: Problem using XDS200 USB emulator.
- Edwin McKay wrote:
> I have gotten a little further. The "Test Connection" now seems to work. So I guess Ubuntu can talk to the XDS module.
Did you do anything to get this test to pass?
> ...
Makes sense. I'm pretty sure the DSP's clo... - EM 03:16 PM Software Development: RE: Problem using XDS200 USB emulator.
I have gotten a little further. The "Test Connection" now seems to work. So I guess Ubuntu can talk to the XDS module.
When I select my project for debugging I receive the following message:
C674X_0: Error connecting to the target:...- JC 11:00 AM Software Development: RE: Problem using XDS200 USB emulator.
- Edwin wrote:
> I will try searching the TI web site.
Good idea. Let us know if you find something that helps.
- JC 10:59 AM Software Development: RE: Problem using XDS200 USB emulator.
- Thanks for the update. I will see if we can get one in house. In the mean time try searching TI's e2e to see if anyone has reported having similar issues. Let us know if you find a solution.
- EM 10:34 AM Software Development: RE: Problem using XDS200 USB emulator.
- From TI's web site the XDS510 & XDS560 are both obsolete?
I will try searching the TI web site.
04/08/2016
- BD 02:13 PM Software Development: RE: gcc 4.8.4 l38F link can't resolve POOL_translateAddr
- Steve,
Thank you for posting the fix.
We haven't tested using the Yocto filesystem with earlier MDK. It is expected that you would use the Yocto based MDK (currently mitydsp-l138-MDK-base-2015-11-13.sh) along with the Yocto filesyt...
04/07/2016
- AB 03:46 PM Software Development: RE: Problem using XDS200 USB emulator.
- Edwin,
Unfortunately we have not used the XDS200 on any platform so we don't even have one to try and reproduce this issue. I'm sure this is just outdated information but section 7.1 of this wiki http://processors.wiki.ti.com/index.ph... - I am trying to debug my DSP project (actually just the HelloWorld program). I have a XDS200 debugger plugged into my board. The module has a green light. Under project properties, my connection is "Texas Instruments XDS2xx USB Emulator/...
- SP 09:04 AM Software Development: RE: gcc 4.8.4 l38F link can't resolve POOL_translateAddr
- Hi Bob
I think I found the problem.
DSPLINK.lib is in a different location than in the original setup.
Is MDK_2014-01-13 compatible with gcc 4.8.4 and yocto file system?
I had to kludge in the file in the linker command line.
...
04/06/2016
- BD 03:06 PM Software Development: RE: gcc 4.8.4 l38F link can't resolve POOL_translateAddr
- Steven, can you share the Makefile you are using?
- I using gcc 4.8.4 compiling a arm program for Dbric 3 yocto file system.
I get a link error "/home/mitydsp/workspace/NDCLaunchApp/NDCLaunchApp.cpp:310: undefined reference to `POOL_translateAddr'"
The only file I find with POOL_transla...
04/04/2016
- BD 04:31 PM Software Development: RE: How to Enable a systemd Unit Template for Boot Execution
- Ben,
Thank you for the follow-up on this bug. I'm glad you got it working. I can't find any reference to case-sensitivity in the docs, so I create an internal issue for us to test this with our final Yocto release.
-Bob
- BA 03:59 PM Software Development: RE: How to Enable a systemd Unit Template for Boot Execution
- Bob,
So I was able to home in on the issue. It centers on the parameter being passed to the unit file. As stated before, this one fails:
systemctl enable TDI_DataServer@-var-lib-ndc-DataServer.DB
However, if I change our d... - JC 08:51 AM Software Development: RE: How to Enable a systemd Unit Template for Boot Execution
- Yocto poky daisy (1.6.3)
- BA 08:34 AM Software Development: RE: How to Enable a systemd Unit Template for Boot Execution
- Bob,
We are looking at workarounds getting the enable to function. Do you have a Yocto version number associated with the ALPHA Release 2016.01 filesystem we are using?
Regards,
Ben