Activity
From 07/30/2014 to 08/28/2014
08/19/2014
- HK 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 module is not runing
Thank you.
- JC 08:50 AM Software Development: RE: How to probe the fpga_ctrl & fpga_gpio.ko module
- Did you mean
- HK 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) mdule.
> ...
- HK 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) mdule.
> ...
- I'm tryint to control FPGA of GPIO on the linux driver side with MityL138-DSP(L138-FI-236-RL) mdule.
and, loading the myFPGA.bin , fgpa_ctrlko, fpga_gpio.ko module is successfule.
also, test tool of fpgautil is work well.
modprob...
08/18/2014
- AD 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 diodes to the VCCO and GND rails that can withstand a max of 10mA per pin. Adding series resistors to the I/O pins that ... - 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 module connected to it (via FPGA) while the L138F module was off. I'm measuring 1.8V on some of the ADC output pins. Cans ...
08/11/2014
- JC 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 source the block size is already set to this max value. To accept fragmented packets the source says to enable CONFIG_IP_...
- JC 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 downloads.
08/08/2014
- DB 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-boot (U-Boot > setenv tftpblocksize 4096) and entire file transferred, no hangs or system crashes.
After reboot, serial... - JC 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.
One thing to try would be to setup a link directly between your computer and the device. No need for a cross over cabl... - DB 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.ais, u-boot-ubl.bin, and uImage to flash NOR).
However, in step 6, after many (>10) attempts to tftp the filesystem (m...
08/07/2014
- JC 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 latest MDK]]
08/06/2014
- I've recently completed the ARM HelloWorld example via the Starter Guide Wiki page and need help with the DSP HelloWorld example. My set up is as follows:
- MityDSPL138 Industrial I/O board w/ Angstrom GNU/Linux 20107-test-20110516 (...
08/05/2014
- JC 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.
- JC 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-davinci.git;a=commit;h=57c3f55e1dab523b1d26405b11579a6c91a60cc9
08/04/2014
- MA 07:53 AM Software Development: RE: I2C 0x8 Address
- Yes, works fine now. Thanks Jonathan.
08/01/2014
- JC 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. Let me know if that works now. - MA 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 cpufreq_notify_transition(&freqs, CPUFREQ_PRECHANGE);
When moving back down to the lower frequency, cpufreq_notify_tran... - JC 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 diff above.
- MA 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_i2c_wip' from Git and compiled both as-is (after running mrproper and industrialio_defconfig). After running mrproper on...
- JC 09:01 AM Software Development: RE: I2C 0x8 Address
- I'm not seeing this hang with or without i2c-2 enabled.
- MA 08:53 AM Software Development: RE: I2C 0x8 Address
- Yes, v3.2_i2c_wip checked out and compiled as-is.
- JC 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
- JC 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-platforms/wiki/Linux_Root_File_System#Flashing-Image-to-NAND - DB 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 run on the ARM.
I needed to set up the environment for the v4.3.3 toolchain:
Environment Setup for ToolChains 4.3.3... - MA 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.
- MA 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 modifications.
- MA 10:41 AM Software Development: RE: I2C 0x8 Address
- Yes, it is:
- JC 10:07 AM Software Development: RE: I2C 0x8 Address
- Just to verify this was with the newer mitydsp-linux-v3.2_i2c_wip branch?
- MA 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:
- JC 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
- JC 01:33 PM Software Development: RE: Start Guide : Cannot build helloworld application with eclipse
- > root@mityomapl138:/var/volatile/tmp# ./HelloWorldCC
> ...
It looks like your using the old filesystem with the new compiler. Which will cause these shared object errors. The latest filesystem can be found in the MDK. Or you can use... - DB 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. Issues w/ Virtual Box and the tool chain slowed me down a bit.
First time checking whether tool chain was installed ... - MA 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 while before we can fully port everything and test against the 3.2 kernel. However, I did try the I2C bits and your patc...