Activity
From 02/29/2012 to 03/29/2012
03/28/2012
- SP 11:15 AM Software Development: RE: Dead board
- Hi Mike,
Thank you for your hints.
The good news first: Using the gel files (which is extended with the 150MHz for mDDR), resolves the mDDR problem such as I can load and run application over JTAG.
The bad thing is, that I've ma... - MW 09:32 AM Software Development: RE: Dead board
- Well.
The Address 0xFFFD5684 is ARM local ROM code, so it's not surprising that you can't set a breakpoint at that location.
Is the UPL_SPI_MEM.ais your custom application, or the "UBL_SPI_MEM.ais" image provided by Critical Link f...
03/27/2012
- MW 08:18 AM Software Development: RE: Write UART2 RS-485 API
- Hi Joe,
I am attaching some sample code (a transmit program, and a receive program) that we used to test the RS-485 patches made at Critical Link for another customer.
This code will work with the 2.6.34-rc1 kernel code (the "maste... - JH 01:50 AM Software Development: RE: Write UART2 RS-485 API
- Sorry I forgot the file.
- Hi,
I want to use RS-485 to control other device.
Now I can control uart2 from mitydsp-l138 (not FPGA module), but I don't know how to control RS-485 TXE signal on linux.
The TXE de-assert is too late if I control it by linux gpio e... - (posted on behalf of a customer)
- I tried to flash a new application to my module. Therefor I performed: sfh_OMAP-L138.exe –flash –v –p COM1 UPL_SPI_MEM.ais myApp.out.
- After a reset, the serial connection remai... - KF 12:51 AM Software Development: RE: Access to the PHY Registers
- Hi Tim,
Thanks for your quick reply - Register 18 is the LED direct control register. I did a few quick tests with the u-Boot commands you suggested and it seems to work as advertised.
Thanks again for help,
keith
03/26/2012
- TI 09:58 PM Software Development: RE: Access to the PHY Registers
- u-boot has the mii commands that let you twiddle the registers, or you can always write a driver :D
I'm not sure without looking what register 18 is, but linux does provide quite a lot of control
over a lot of the params using the /pr... - Hi,
This is perhaps a long shot, but I am using a MityARM1808 with development kit, and would like to know if there is any way to access and change the Ethernet PHY registers (particularly 18H) through the ARM software (either u-boot or... - AJ 05:00 AM PCB Development: RE: FPGA no-connects for 45 size FPGA on MityDSP-L138F
- I've tried out the "hack" and it works fine; so yes indeed they are floating.
-anders
03/22/2012
- RB 08:42 PM Software Development: RE: Kernel Hang Anomaly
- Hi Mike,
No need to dig into the file I sent.
I downloaded the 12-05-2011 MDK and rebuilt the kernel
using that configuration after running menuconfig to
check that the mmc drivers were enabled. I didn't make
any changes to the co... - RB 07:13 PM Software Development: RE: Kernel Hang Anomaly
- HI Mike,
I'm attaching a file that contains the results of the check of the config.gz file filtering by MMC
both your and our configuration report the same info.
THere is a difference at the point in the boot sequences where udev st... - RB 06:23 PM Software Development: RE: Kernel Hang Anomaly
- Ok, I'll go check the config.gz settings and let you know what I find out.
- MW 06:16 PM Software Development: RE: Kernel Hang Anomaly
- Hi Rich,
So in the u-Boot, the config block is read on start-up in order to tell u-Boot whether or not it should configure the MMC pins and enable the device.
Right now, we only support MMC0 configuration, and the prompts for the d... - RB 04:58 PM Software Development: RE: Kernel Hang Anomaly
- Mike,
Can you elaborate on the significance of the lines in the config response that read:
MMC0 Config : 0
MMC1 Config : 0
I just brought up a couple of our carrier boards with mity-omapl138s using the 08-01-11 kernel
and once the...
03/21/2012
- TC 08:01 PM Software Development: RE: StarterWare question ...
- Hi Stephane -
Unfortunately we believe you are executing the low level initialization code for the TI EVM which is different than what needs to execute for our module. We believe this is why you are having difficulty.
We need to ... - SW 02:06 PM Software Development: RE: console redirection
- Mike,
So then I just need to change the bootargs to use ttyS2 instead of ttyS1 and the linux kernel console will be directed out uart2? At this point I will leave uboot output on uart1. It is good to know it shouldn't be too hard to f...
03/20/2012
- MW 05:13 PM Software Development: RE: console redirection
- Hi Scott,
For the kernel, you should only need to change the console argument in the bootargs (assuming the pinmux settings are ok for the other serial port) to point at ttyS2.
For u-boot, if you mess it up, you can recover using t... - MW 05:13 PM Software Development: RE: console redirection
- Hi Scott,
For the kernel, you should only need to change the console argument in the bootargs (assuming the pinmux settings are ok for the other serial port) to point at ttyS2.
For u-boot, if you mess it up, you can recover using t... - Hello,
We are using a MItyDSDPL138 with the MityDSP baseboard. We want to use uart1 on the baseboard to interface with a serial device and redirect console output through uart2. I will need to change the console in both uBoot and in t... - SP 07:34 AM Software Development: RE: StarterWare question ...
- Hello,
Thank you for starting this thraed, because I'm facing the same problem as Tim had 2 weeks ago - *and unfortunatelly, I didn't succeed so far*...
Following the steps I made (most of it according to the chapter _Flashing an A...
03/19/2012
- MW 10:30 AM Software Development: RE: 'Fast Boot' DSP
- Is the DSP going to be communicating to the ARM via DSPLINK? If so, this may be a challenge as the ARM and DSP need to do some handshaking on startup after the linux kernel is loaded and initialized. You'll need to look closely at opti...
03/15/2012
- SW 10:49 PM Software Development: RE: OMAP GPIO
- Hi Mike,
It turns out I didn't enable the Industrial Board I/O option in the kernel. After I enabled it (and enabled MUX debug output to verify the GPIO pins are configured correctly), I can toggle the GPIO pins.
Thanks,
- Simon - MW 08:10 PM Software Development: RE: OMAP GPIO
- Hi Simon,
I don't see anything wrong here, but you might want to ensure that the pin-mux configuration is setup for this particular GPIO. I thought that the stock ARM linux kernel provided by Critical Link did this for you, but if yo... - Hi,
I'm having trouble accessing the OMAP GPIO pins as detailed in the "MityARM-1810 PROFIBUS Dev Kit" documentation from the DSP.
I am assuming the OMAP_GP0_xx pins means bank 0, and xx means the offset. I'm using the core library... - (Posted on behalf of a customer):
We need to boot the DSP fast (up and running code in less than 2 secs. ) and then continue with ARM/Linux boot?
03/13/2012
- SW 04:25 PM Software Development: RE: ftdi usb to serial drivers
- Thanks Mike that worked.
- MW 12:07 PM Software Development: RE: ftdi usb to serial drivers
- You need to install mkimage on your linux machine.
- SW 12:02 PM Software Development: RE: ftdi usb to serial drivers
- Tim,
Thanks for the help. I see the source in the code tree and also see why I couldn't see it in menuconfig. My problem now is when I try to compile. I think I am missing a step in my setup. I get this error:
Kernel: arch/ar...
03/12/2012
- TI 05:25 PM Software Development: RE: ftdi usb to serial drivers
- Scott
The FTDI serial drivers should be in the kernel source tree (as of kernel v 2.6.31)
Its the "USB FTDI Single Port Serial Driver"
See <http://ftdi-usb-sio.sourceforge.net/> for more
In Menu Config:
Device Drivers --... - Hello,
I want to access a device across the host USB that uses a FTDI chip to transmit serial data across the usb. When I plug the usb device into the MityDSP the usb device is recognized correctly, but the FTDI usb to serial driver is...
03/06/2012
- TE 04:10 PM Software Development: RE: StarterWare question ...
- Also, as a followup question, the StarterWare examples are setting up the system for the evmOMAPL138. For instance, the UARTecho example tries to configure UART2 while the MityDSP is setup for UART1. Are there examples setup like the s...
- (posted on behalf of a customer)
For the starterware non-os method, I have built some of the starterware examples using code composer. I have converted those to bin files with the out2rprc executable. I am at the point that I need t... - MW 10:16 AM Software Development: RE: Critical Link Package locations?
- At the moment, we don't provide customized packages. The mityomapl138 location was generated during the bitbake build as part of the configuration scripts. We didn't catch it when we built the filesystem up.
You can safely ignore th... - (posted on behalf of a customer)
What are the updated feed addresses for the critical link packages?
(these are the errors I get from opkg update)
Downloading http://www.angstrom-distribution.org/feeds/unstable/ipk/glibc/armv5...
03/04/2012
- SG 06:11 PM Software Development: RE: about boot
- Mike,
Thank you very much. I understand. - MW 04:51 PM Software Development: RE: about boot
- The EXT_BOOT# signal drives a small mux circuit on the SOM that changes the boot strap pull-up/pull-down options on the OMAP-L138 such that it will use UART0 instead of SPI1_CS0 as the primary boot device. If you need details about this...
- MW 04:56 PM PCB Development: RE: FPGA no-connects for 45 size FPGA on MityDSP-L138F
- The bare board PCB for the two variants of the SOM are identical, the only difference is the BOM used for assembly. Pins 170 and 172 are still routed to the balls on the FPGA (E7/E8). However, I'm fairly certain that these pins are not...
03/01/2012
- I wonder how the boot mode switch from SPI1 to UART1 using EXT_BOOT# signal? Thank very much.