Activity
From 03/27/2012 to 04/25/2012
04/25/2012
- MW 12:57 PM Software Development: RE: Starterware EMIFA to FPGA example code
- Hi Emmett,
Are you using linux or starterware? On starterware, if you are launching from u-Boot (which configures the EMIFA to have some nominal timings for CS5 space), then all you need to do is perform memory read or writes to 0x66... - Hello,
I have used your "EMIFA_iface" VHDL example to make a simple FPGA to test by reading/writing to registers routed to the expansion I/O on the base board.
I need example C code to make the EMIFA transfers.
In the Starterware, I...
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