Activity
From 07/24/2014 to 08/22/2014
08/19/2014
- 11:31 AM Software Development: RE: How to probe the fpga_ctrl & fpga_gpio.ko module
yes,
echo "146" > /sys/class/gpio/export --> sh: write error: Invalid argument
it may be that fpga_gpio...- 08:50 AM Software Development: RE: How to probe the fpga_ctrl & fpga_gpio.ko module
- Did you mean ...
- 08:26 AM Software Development: RE: How to probe the fpga_ctrl & fpga_gpio.ko module
- HYUNG KI KIM wrote:
> I'm tryint to control FPGA of GPIO on the linux driver side with MityL138-DSP(L138-FI-236-RL)... - 08:24 AM Software Development: RE: How to probe the fpga_ctrl & fpga_gpio.ko module
- HYUNG KI KIM wrote:
> I'm tryint to control FPGA of GPIO on the linux driver side with MityL138-DSP(L138-FI-236-RL)... - I'm tryint to control FPGA of GPIO on the linux driver side with MityL138-DSP(L138-FI-236-RL) mdule.
and, loading t...
08/18/2014
- 04:31 PM PCB Development: RE: Protecting MityDSP module during development
- Hi Udi,
Yes the FPGA I/Os can be damaged by sinking too much current - powered or off. The I/Os have protection d... - We just fried a MityDSP L138F module, and I'm not sure why. I'm suspecting that the problem was that we had an ADC mo...
08/11/2014
- 09:21 AM Software Development: RE: DSP HelloWorld Compile with gcc 4.3.3
- tftp stalls when I set the block size larger than the standard MTU size (1500 - overhead = 1468). According to the so...
- 09:06 AM Software Development: RE: DSP HelloWorld Compile with gcc 4.3.3
- Glad that you got it working. I've never used the block size feature. I'll check out what affect it has on my tftp d...
08/08/2014
- 03:20 PM Software Development: RE: DSP HelloWorld Compile with gcc 4.3.3
- Successful tftp transfer of mityomap-full.jffs2 from VM to L138 ARM core! Tried setting the blocksize to 4096 in u-bo...
- 12:58 PM Software Development: RE: DSP HelloWorld Compile with gcc 4.3.3
- Occasionally I see timeouts during the transfer but I haven't seen windows or the vm crash during a tftp transfer.
... - 10:52 AM Software Development: RE: DSP HelloWorld Compile with gcc 4.3.3
- Thank you for the filesystem update procedures. I was able to successfully complete steps 1-5 (writing UBL_SPI_MEM.a...
08/07/2014
- 08:54 AM Software Development: RE: DSP HelloWorld Compile with gcc 4.3.3
- I created a how to for updating an L138 devkit. Let me know if theres any confusing parts.
[[Updating devkit to lat...
08/06/2014
- I've recently completed the ARM HelloWorld example via the Starter Guide Wiki page and need help with the DSP HelloWo...
08/05/2014
- 09:30 AM Software Development: RE: How to enable PRU Subsystem on MityDSP-L138F SOM ???
- Patches have been merged into linux-mityarm-v3.2 branch.
- 09:16 AM Software Development: RE: I2C 0x8 Address
- Cleaned up and merged changes into mitydsp-linux-v3.2 branch.
http://support.criticallink.com/gitweb/?p=linux-davi...
08/04/2014
- 07:53 AM Software Development: RE: I2C 0x8 Address
- Yes, works fine now. Thanks Jonathan.
08/01/2014
- 01:47 PM Software Development: RE: I2C 0x8 Address
- I see now. Odd that i'm not encountering this lockup.
I moved the other cpufreq_notify and pushed it to the branch... - 11:16 AM Software Development: RE: I2C 0x8 Address
- Yes, that only works when moving to a higher frequency because the voltage adjustments are made before the call to cp...
- 11:12 AM Software Development: RE: I2C 0x8 Address
- And thats why i moved the cpufreq_notify_transition(&freqs, CPUFREQ_PRECHANGE); to below that line as seen in your di...
- 11:10 AM Software Development: RE: I2C 0x8 Address
- Really don't know why we're seeing different things. I checked out both 'mitydsp-linux-v3.2' and 'mitydsp-linux-v3.2_...
- 09:01 AM Software Development: RE: I2C 0x8 Address
- I'm not seeing this hang with or without i2c-2 enabled.
- 08:53 AM Software Development: RE: I2C 0x8 Address
- Yes, v3.2_i2c_wip checked out and compiled as-is.
- 08:32 AM Software Development: RE: I2C 0x8 Address
- Are you saying you run into the hang when only i2c-1 is enabled?
07/31/2014
- 03:36 PM Software Development: RE: Start Guide : Cannot build helloworld application with eclipse
- Instructions for flashing a new filesystem can be found here:
https://support.criticallink.com/redmine/projects/arm9... - 11:57 AM Software Development: RE: Start Guide : Cannot build helloworld application with eclipse
- After using the older toolchain v4.3.3 and existing ARM filesystem, I was able to get the HelloWorld executable to ru...
- 12:24 PM Software Development: RE: I2C 0x8 Address
- I've just tried the latest mitydsp-linux-v3.2 from git (without the i2c patches) and that works fine.
- 11:04 AM Software Development: RE: I2C 0x8 Address
- Just for clarification, I had reverted all changes to the branch (enabling i2c-2) so 'git status' shows no local modi...
- 10:41 AM Software Development: RE: I2C 0x8 Address
- Yes, it is:...
- 10:07 AM Software Development: RE: I2C 0x8 Address
- Just to verify this was with the newer mitydsp-linux-v3.2_i2c_wip branch?
- 09:55 AM Software Development: RE: I2C 0x8 Address
- That's really strange. The only modifications I made were to baseboard-industrialio.c in order to enable i2c-2:
<p... - 08:24 AM Software Development: RE: I2C 0x8 Address
- I tried your steps on the mitydsp-linux-v3.2_i2c_wip with i2c-2 enabled but didn't encounter a hang.
07/30/2014
- 01:33 PM Software Development: RE: Start Guide : Cannot build helloworld application with eclipse
- > root@mityomapl138:/var/volatile/tmp# ./HelloWorldCC
> ./HelloWorldCC: /usr/lib/libstdc++.so.6: version `CXXABI_ARM... - 12:48 PM Software Development: RE: Start Guide : Cannot build helloworld application with eclipse
- Jonathan,
Thanks for the reply.
Yes, I’ve followed the Starter Guide. Spent most of last week working through it.... - 08:18 AM Software Development: RE: I2C 0x8 Address
- Hi Jonathan, thanks for the testing branch. As our code is still based around the old 2.6.34-rc1 release, it will be ...
07/29/2014
- 02:25 PM Software Development: RE: I2C 0x8 Address
- I've created a test branch with my patches for this problem. Could you verify it works for you? Note that branch wo...
- 10:24 AM Software Development: RE: I2C 0x8 Address
- Okay I have submitted a bug report to the linux davinci mailing list using some of your procedures and stack trace. ...
- 10:12 AM Software Development: RE: I2C 0x8 Address
- Thanks Jonathan, I can confirm that the workaround allows the CPU frequency scaling to work with I2C1 enabled (but no...
- 09:56 AM Software Development: RE: I2C 0x8 Address
- It appears that the wait_for_completion is the wrong type of synchronization as it currently will always be true as l...
- 08:56 AM Software Development: RE: I2C 0x8 Address
- The transition function looks like following. The wait_for_completion call then calls wait_for_common which can be s...
- 08:50 AM Software Development: RE: I2C 0x8 Address
- I can confirm. Made the following changes to the 3.2 kernel and tried changing the frequency. It locks up if you do...
- 08:33 AM Software Development: RE: I2C 0x8 Address
- Hi Mike,
??To confirm, you don't see this issue with I2C1 not enabled in you kernel (the "stock" dev kit kernel), ... - 07:42 AM Software Development: RE: I2C 0x8 Address
- Ok, you didn't mention you are trying to adjust the CPU speed (or I missed it) as your I2C0 access method. That's no...
- 05:44 AM Software Development: RE: I2C 0x8 Address
- Hi Mike, actually our experience is the opposite:
1. Enable I2C1, flash the new kernel and reboot
2. Immediately ... - 09:09 AM Software Development: RE: Start Guide : Cannot build helloworld application with eclipse
- Have you followed the instructions located on the wiki? https://support.criticallink.com/redmine/projects/arm9-platf...
07/28/2014
- 03:13 PM Software Development: RE: Start Guide : Cannot build helloworld application with eclipse
- I'm working through the Starter Guide for the MityDSP-L138 configured with
- VirtualBox 4.3.0 (could not get Mity... - 11:55 AM Software Development: RE: I2C 0x8 Address
- Looks like the kernel is configuring the OMAP-L138 I2C slave address as 0x08 (by default, it is 0x00 - illegal - in t...
- 11:33 AM Software Development: RE: I2C 0x8 Address
- No worries. I don't think i2c-detect does anything strange with this address. By looking at the code, I don't see any...
- 11:29 AM Software Development: RE: I2C 0x8 Address
- We're looking at it now. I think that the i2c-tools may be emulating SMBus and trying to run the arbitration scheme ...
- 10:49 AM Software Development: RE: I2C 0x8 Address
- Source : System Management Bus (SMBus) Specification Version 2.0 August 3, 2000 :Appendix C – SMBus device address as...
- 10:20 AM Software Development: RE: I2C 0x8 Address
- OK. So is it a defect on the MityDSP-L138F board, or is it the address of the OMAP I2C bus?
- 09:54 AM Software Development: RE: I2C 0x8 Address
- Also on a devkit where the dvi chip was removed the 0x08 address still appears....
- 09:52 AM Software Development: RE: I2C 0x8 Address
- Well at the least I can identify the others. 0x38 is the dvi chip, 0x48 is the pmic, and 0x50-58 is the eeprom. Whe...
- 09:31 AM Software Development: RE: I2C 0x8 Address
- We use a custom baseboard, but the address 0x8 is at the the industrial IO development kit as well:
root@PureVLC:~... - 08:06 AM Software Development: RE: I2C 0x8 Address
- Did you set the pin-mux settings for the I2C1 lines on the second device in the kernel as well? For the devkit baseb...
- 07:59 AM Software Development: RE: I2C 0x8 Address
- The problem is that if we enable both I2C interfaces by changing the linux source code by adding the following lines ...
- 07:55 AM Software Development: RE: I2C 0x8 Address
- What are you using for your baseboard?
- 07:46 AM Software Development: RE: I2C 0x8 Address
- I am using MityDSP-L138F board.
- Hi All,
When I run i2cdetect -y 1 I get the following output:
0 1 2 3 4 5 6 7 8 9 a b c d e ...
Also available in: Atom
Go to top
