Activity
From 10/14/2014 to 11/12/2014
11/10/2014
- DG 01:52 PM Software Development: RE: Real time SATA writes
- Hi Mary,
As you suspected in your original post, it is likely that when you are calling fwrite, in some cases the write cache is full and is causing full flush down to storage (NAND). In this case it will take longer than just writing... - MF 01:04 PM Software Development: RE: Real time SATA writes
- After further testing and setting optimization, I have narrowed down the delay:
The call to fwrite() normally takes about 2.5 msec, but occasionally (on the order of minutes) this call can take 20 msec, 40 msec, 150 msec, or even 300...
10/31/2014
- Hi.
I'm using MityDSP-L138F Board. As will ensure that the generated clock signal to FPGA?
Thanks
10/24/2014
- MW 10:41 AM PCB Development: RE: L138 SOM LEDs
- Sorry,
On Non-FPGA modules:
D1 is connected to R16 (GP6_12) of the OMAP-L138.
D2 is connected to R17 (GP6_13) of the OMAP-L138.
-Mike
- AK 10:05 AM PCB Development: RE: L138 SOM LEDs
- Hi Mike,
The SOM we are using is the non-FPGA version. What do D1 and D2 connect to?
Thanks,
Anton - MW 07:22 AM PCB Development: RE: L138 SOM LEDs
- D1 is connected to the FPGA_DONE pin on the FPGA configuration block.
D2 is connected to P15 of the FPGA IO_L74P_AWAKE_1
D3 is connected to P16 of the FPGA IO_L74N_DOUT_BUSY_1
-Mike
- AK 10:03 AM PCB Development: RE: MityDSP-L138 Boot Problem
- This issue has been resolved - we had left an uterminated SPI1_CLK signal trace on our base board at an unpopulated device.
Anton
10/22/2014
- Please can you provide information for D1 and D2 LEDs on the L138-FX-225-RC module. What are they connected to?
Thanks,
Anton - We are using the L138-FX-225-RC on a new custom baseboard and are having trouble with boot:
- no UART activity in normal SPI boot
- UART boot mode sends "BOOTME"
We attempted to erase and flash the bootloader using the WinCE boot pa...