Activity
From 03/18/2012 to 04/16/2012
04/13/2012
- MW 06:31 PM PCB Development: RE: RTC Battery Drain
- Hi,
Wanted to follow up on this. We have seen RTC battery drainage, but at the time we looked at it we were using Revision A silicon OMAP-L138 parts, which had some errata about power leakage that was fixed in the Revision B (standar... - MW 06:28 PM Software Development: RE: FS Corruption due to dropping power
- Hi Keith,
I have seen these symptoms before, and I'm pretty sure it's filesystem corruption related (I suspect udev related, not installing the /dev/ttyS* files due to a corrupted cached tarball of /dev which is by default stored off ...
04/12/2012
- Hi, We are developing a system where the user is unlikely to power down gracefully, even if asked to do so and ultimately intend to use a read only file system. However in testing we have not done this and have been dropping power to swi...
04/07/2012
- MW 09:46 PM PCB Development: RE: SODIMM Pin 53 ...
- SPI1_SCS0 is indeed connected to that pin on the module. It is also connected to the chip-select on the on-board SPI NOR FLASH, which is used for loading the first stage bootloader (UBL) as well as u-Boot. The pin was brought out to th...
- (Posted on behalf of a customer)
The datasheet for the MITYDSP-L138F shows Pin 53 as reserved, however the Industrial IO board uses it for SPI1_SCS0. Why does the datasheet show it as reserved?
04/06/2012
- MW 07:40 AM Software Development: RE: StarterWare question ...
- Quick note. The new u-Boot command to load up the Starterware image was "bootelf" not "loadelf". I've corrected the wiki page. Sorry for the confusion (I was trying to post that before having to climb on an airplane!). The u-Boot im...
04/05/2012
- SP 02:56 AM Software Development: RE: StarterWare question ...
- see [[StarterWare]]
04/04/2012
- MW 02:33 PM Software Development: RE: StarterWare question ...
- Hi guys,
Just wanted to give you a heads up that we've been able to get the EVM UART echo example in the TI startware up and running here at Critical Link. We've been able to load with with the debugger/emulator as well as load the E...
03/30/2012
- SP 09:19 AM Software Development: RE: Dead board
- All clear.
Today, I received a second Base Board - And with this new hardware, the CPU Board runs normally. --> So, a hardware defect on the Base Board is causing our problems.
Thanks for your time and help.
Best regards
Stépha... - JH 06:11 AM Software Development: RE: Write UART2 RS-485 API
- Hi Mike:
Thanks for your response. It is working with the 2.6.34-rc1.
It is good timing to assert/de-assert TXE.
I am not sure that we need linux-v3.2 or not. I will try to patch it if we need.
Thanks,
Joe
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...