Activity
From 10/13/2017 to 11/11/2017
11/09/2017
- OÇ 04:52 AM Software Development: RE: SysLink Configuration
- Thanks, Mike,
That clarified things.
Regarding my earlier question, "this forum thread":https://e2e.ti.com/support/embedded/tirtos/f/355/t/440203 has the answer, in case someone else needs it.
> The SysLink examples are provided t...
11/08/2017
- MW 12:18 PM Software Development: RE: SysLink Configuration
- We added minimal support for Starterware for a couple of specific customers that insisted on using it. In those cases, they were not really running multicore. They wanted to either run bare-metal ARM or bare-metal DSP code (not both). ...
- OÇ 04:59 AM Software Development: RE: SysLink Configuration
- Hi, Jonathan,
I understand that you do not support SysLink, and using your MDK for ARM-DSP communication is very easy for me, too, given the complexity of SysLink examples and the E2E forum's reluctance to respond to my questions.
...
11/07/2017
- JC 07:45 PM Software Development: RE: SysLink Configuration
- Hi Okan,
We currently do not support SysLink in the capacity needed to answer your most recent questions. We recommend pursuing your project using our MDK (which utilizes DSPLink instead of SysLink), as we are more able to provide sup... - OÇ 01:34 PM Software Development: RE: SysLink Configuration
- Hi,
Since I managed to run the example executables in MityDsp last week, I've been trying to modify the codes and understand how it works, but I couldn't even compile any of them yet.
The TI wiki has a "Creating CCS Project for Sys...
10/31/2017
- JC 01:27 PM Software Development: RE: SysLink Configuration
- Thanks for the update. Glad you found the problem.
- OÇ 05:59 AM Software Development: RE: SysLink Configuration
- Hi,
I was just about to build a new kernel to set @earlyprintk@, then I realized my @bootargs@ were missing @0x@ prefixes. I fixed it and the kernel now boots. _(Oddly, I never used @0x@ in my other U-Boot commands and I never ran int...
10/30/2017
- JC 01:48 PM Software Development: RE: SysLink Configuration
- Okan Çalış wrote:
> "This TI wiki page":http://processors.wiki.ti.com/index.php/Kernel_-_Common_Problems_Booting_Linux says that the boot parameter must be incorrect, but I don't know how to fix it. What's the difference between the m... - Hi,
I'm working on a MityDsp-L138F SoM, with the ARM running Linux. So far, I've managed to make the ARM and DSP cores communicate through Critical Link's wrapper functions for DspLink. But my problem is that DspLink does not support ...
10/26/2017
- OÇ 05:39 AM Software Development: RE: Setting the ARM as a USB bulk device
- Michael Williamson wrote:
> That is reasonable. Using large transfers and Async IO, we were able to get up to 14 MB/sec with the camera application. But 5 MB/sec sounds OK for a nominal transfer scenario.
> ...
Actually, the project ... - OÇ 04:58 AM Software Development: RE: Setting the ARM as a USB bulk device
- Thank you.
10/25/2017
- TR 06:49 PM Software Development: RE: Using SigProc Example
- Hi, So we're in the process of integrating an external audio codec. We would like to get to the point of running FFTs on those acquired signals. I've reviewed the SDR uPP application and the FFT performance analysis papers but there are ...
- MW 04:57 PM Software Development: RE: Using SigProc Example
- What are you trying to do?
- Hi,
So I was able to import and rebuild the SigProc lib example in the MDK-2014 /sw/DSP/lib/SigProc using CCS v5 on windows, plan to move that over to CCS in Linux.
Are there any simple examples available or documentation for how ... - MW 01:17 PM Software Development: RE: Setting the ARM as a USB bulk device
- That is reasonable. Using large transfers and Async IO, we were able to get up to 14 MB/sec with the camera application. But 5 MB/sec sounds OK for a nominal transfer scenario.
I guess the question is if that is acceptable for your ... - JC 01:00 PM Software Development: RE: Setting the ARM as a USB bulk device
- Looking at some of the speed tests we ran with RNDIS, we were seeing about 10Mb/s or ~1.25 MB/s. So you results seem pretty good in comparison.
- OÇ 05:22 AM Software Development: RE: Setting the ARM as a USB bulk device
- Hi, Jonathan and Mike,
Thanks for your help.
With the @usb.c@ code in "Linux-USB.org,":http://www.linux-usb.org/gadget/ I managed to send and receive bulk data using @GadgetFS@ last week. I modified the code to solve some minor pro...
10/24/2017
- JC 03:30 PM Software Development: RE: Updating devkit to latest MDK tfpt issue
- Jorden Luke wrote:
> I figured it out by doing the config. The VM has two eth interfaces. I was using eth1 when I switch to eth0 it worked fine.
Awesome thanks for the update. - JL 03:30 PM Software Development: RE: Updating devkit to latest MDK tfpt issue
- I figured it out by doing the config. The VM has two eth interfaces. I was using eth1 when I switch to eth0 it worked fine.
- JC 03:13 PM Software Development: RE: Updating devkit to latest MDK tfpt issue
- Certainly seems like the transfer is somehow being interrupted.
How is the L138 connected to your computer's network?
Direct cross-over cable or through a network switch? How much traffic on the network switch if applicable?
Do... - Hello I am new to the embedded linux world. I don't have too much experience with loading kernels using Uboot and tfpt. I was working on updating a MityDSP L138F to latest kernel. I followed the instructions in the wiki but once I ran th...
10/23/2017
- TR 09:50 PM Software Development: RE: Configuring MityDSP for 256MB DRAM
- Hi, Just a FYI, since 32MB was allocated for the DSP, passing mem=224MB in bootargs seems to work now. Thanks, Tom
- JC 05:01 PM Software Development: RE: MityDSP L138, using UART1 from the DSP
- You can probably modify the enabled_uarts line in the board-mityomapl138.c file to not initialize UART1.
board-mityomapl138.c
10/22/2017
- Hi,
I am trying to communicate using the UART1 from the DSP directly. Currently the ARM core uses the UART1, and I don't have access to the other UART pins. Is there a procedure that I need to follow to shutdown the UART on the ARM, s...
10/20/2017
- JC 01:50 PM Software Development: RE: Blackhawk XDS560v2-USB Debugger gel file
- Hi Andri, Sorry for the late reply.
Are you trying to run a bare bones application on the ARM or are you running a application under linux?
10/18/2017
- MW 06:38 PM Software Development: RE: Configuring MityDSP for 256MB DRAM
- UBoot reports 128 MB,but you should be able to address 256 MB in uboot as well as the kernel. You may need to pass it a mem=256M for it to address it.
-Mike
- TR 06:22 PM Software Development: RE: Configuring MityDSP for 256MB DRAM
- Oh wait I see 256MB from UBL... sorry its u-boot that is reporting 128MB, my bad
- TR 06:20 PM Software Development: RE: Configuring MityDSP for 256MB DRAM
- Hi,
So I used the files in the /images dir of the MDK 2014 and successfully programmed the board. However UBL continues to detect 128MB DRAM, the UBL version does list Jul 11, 2011.
Well I honestly can't recall what the board origi... - MW 05:00 PM Software Development: RE: Configuring MityDSP for 256MB DRAM
- So the patch to support 256 MB modules was introduced in our codebase 7/14/2011. We need to update the UBL wiki page to refer to the AIS images and code in the later MDKs for 256 MB modules.
I am sorry for the confusion.
If you pr... - TR 03:00 PM Software Development: RE: Configuring MityDSP for 256MB DRAM
- Hi Jonathan,
Thanks, I'll give it a try, however I did brick the board early on and had to reflash UBL and u-boot. Dunno maybe I grabbed the older 2010 UBL version at that time.
Regs, Tom - JC 01:13 PM Software Development: RE: Configuring MityDSP for 256MB DRAM
- I would expect that the precompiled UBL_SPI_MEM.ais file in MDK/images would have the 256MB DRAM support.
[[Updating_devkit_to_latest_MDK]] - TR 12:59 AM Software Development: RE: Configuring MityDSP for 256MB DRAM
- Hi,
I went as far as I could and ran into this problem. Imported the project file UBL_SPI_MEM.pjt with the CCS6.2 tool, which I'm not a total expert on. Everything compiled but it's failing as follows: Not sure what to do next... any ... - MW 11:30 AM Software Development: RE: Setting the ARM as a USB bulk device
- Looking further, I think most of that code was based on the usb.c example you already looked at, so maybe this won't help very much. You sort of need example code on both ends. libusb might be a good start for the PC side of things.
... - MW 11:21 AM Software Development: RE: Setting the ARM as a USB bulk device
- So a long time ago, I implemented a bulk transfer protocol on the MityDSP-L138 using gadgetfs in order to emulate a legacy camera protocol.
I am attaching the relevant code files used for interfacing to gadgetfs that were used for the... - OÇ 08:26 AM Software Development: RE: Setting the ARM as a USB bulk device
- > However, when I try getting data from the device, I end up with 64 Bytes of zeros every time, which is not what I expect.
Actually, I thought the @char* serial@ string in @usb.c@ was the message to be sent to the host, but it turned... - OÇ 07:16 AM Software Development: RE: Setting the ARM as a USB bulk device
- Hi, Jonathan,
I managed to rebuild a kernel and boot the OS. Thanks for helping me out.
I was also able to use the serial gadget module @g_serial.ko@, send and receive terminal messages using TeraTerm on my Windows host. The proble...
10/17/2017
- TR 11:04 PM Software Development: RE: Configuring MityDSP for 256MB DRAM
- Hi Michael,
So now I do see in the UBL device.c, in the 2014 MDK, support for 256MB sizes. I assume I'll have to built and install that
per the instructions on
https://support.criticallink.com/redmine/projects/arm9-platforms/wik... - MW 10:49 PM Software Development: RE: Configuring MityDSP for 256MB DRAM
- There is a custom version of the UBL that queries the local I2C factory PROM to get the part number and sets up the DRAM accordingly. I believe the source code for that UBL is provided in the MDK. Is that what you are using?
- Hi,
We have a L138-FI-236-RL, which should have 256MB of DRAM. U-boot is reporting DRAM : 128MB. The bootargs pass mem=96M which makes sense since all of the MDK examples (using 2014-01-03) have the DSP configured with 32MB. My guess ...
10/16/2017
- AB 03:13 PM PCB Development: RE: MightyDspL138 Factory Test and labeling
- Fred,
Thank you for reaching out to us about this question.
During production test the FPGA IO pins at the edge connector are tested as well as those between the OMAP and FPGA. Prior to having you return/RMA the module can you prov...
10/13/2017
- JC 05:18 PM Software Development: RE: TCF/TCI file questions
- Tom Riddle wrote:
> Hi,
> ...
I don't know hopefully someone else can answer this.
>
> ...
The memory allocated for linux is configured in the bootargs passed to the kernel. The @mem=@ paramter controls how much ram the kernel is a... - Hi,
I'm on the DSP development learning curve and have been merging source from the dsplink examples from the TI DVSDK into the 2014 MDK. So when comparing tci files from the DVSDK message.tci to the Critical Link supplied /sw/DSP/tem... - JC 01:26 PM Software Development: RE: Setting the ARM as a USB bulk device
- Note if you do break the unit you can reprogram it from scratch. [[Reprogramming_a_Dead_Board]]
- JC 01:09 PM Software Development: RE: Setting the ARM as a USB bulk device
- Okan Çalış wrote:
> The author of the blog "advises":http://blog.soutade.fr/post/2016/07/create-your-own-usb-gadget-with-gadgetfs.html#comment_5 me to flash the kernel again as the peripheral controller could be included built-in (thoug... - OÇ 12:01 PM Software Development: RE: Setting the ARM as a USB bulk device
- The author of the blog "advises":http://blog.soutade.fr/post/2016/07/create-your-own-usb-gadget-with-gadgetfs.html#comment_5 me to flash the kernel again as the peripheral controller could be included built-in (though I can't imagine why...