Activity
From 07/18/2014 to 08/16/2014
08/15/2014
- AB 01:44 PM MitySOM-5CSX Altera Cyclone V Software Development: RE: How to add aditional HPS GPIO's
- In the case described of wanting to add GPIO's to drive/control an LED (output from the HPS) you do not need to alter the DTS file. The DTS additions were for Switch based GPIO's which are a special case in which their is a Linux driver ...
08/14/2014
- Posting on behalf of a customer:
On the MitySom .dts file, you specify some GPIOS like this: - AB 10:49 AM MitySOM-5CSX Altera Cyclone V Software Development: RE: PCI-e Device Driver - munmap related error
- Reporting that the customer solved their problem:
I've solved the problem.
Thread A which was signaling Thread B to terminate was doing a pthread_join after doing so.
I commented out the pthread_join and it worked perfectly fine...
08/13/2014
- PB 04:21 PM MitySOM-5CSX Altera Cyclone V Software Development: RE: Standard USB peripheral connection on MitySOM eval Board
- Hi Mike,
Happy to hear that a procedure is needed because I tried many things to make it work (I noticed that in the 09/13 delivered image, my USB key was powered on, but not accessible).
I'll wait for your instructions.
Kind rega...
08/11/2014
- JC 09:21 AM MityDSP-L138 (ARM9 Based Platforms) 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 MityDSP-L138 (ARM9 Based Platforms) 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.
- MW 07:23 AM MitySOM-5CSX Altera Cyclone V Software Development: RE: Miscellaneous questions
- Note:
you need to add "meta-openembedded/meta-oe" as the layer, not just "meta-openembedded".
-Mike
- MW 07:21 AM MitySOM-5CSX Altera Cyclone V Software Development: RE: Miscellaneous questions
- Hi,
Sorry. The i2c-tools recipe is part of the meta-openembedded layer that you don't get by default from the basic yocto process.
You need to download that layer (git clone) and add it to your build/conf/bblayers.conf file. - PB 07:14 AM MitySOM-5CSX Altera Cyclone V Software Development: RE: Miscellaneous questions
- Hi Mike,
adding "i2c-tools" to IMAGE_INSTALL_append gives me this error while executing "bitbake core-image-basic" :
ERROR: Nothing RPROVIDES 'i2c-tools' (but /home/user/yocto/poky/meta/recipes-extended/images/core-image-basic.bb RDE...
08/08/2014
- DB 03:20 PM MityDSP-L138 (ARM9 Based Platforms) 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 MityDSP-L138 (ARM9 Based Platforms) 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 MityDSP-L138 (ARM9 Based Platforms) 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 MityDSP-L138 (ARM9 Based Platforms) 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 MityDSP-L138 (ARM9 Based Platforms) 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 MityDSP-L138 (ARM9 Based Platforms) 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
- MW 10:06 AM MitySOM-5CSX Altera Cyclone V Software Development: RE: Standard USB peripheral connection on MitySOM eval Board
- Hello Mr. Bretecher,
We will try to get a procedure posted for this. Sorry for the delay.
-Mike
- MW 10:05 AM MitySOM-5CSX Altera Cyclone V Software Development: RE: Miscellaneous questions
- Memtool and the i2c-utils aren't added to our reference filesystem image, but you could add it by modifying the IMAGE_INSTALL_append variable in your local.conf file to include "i2c-tools" as well as "memtool".
We will push an update ... - MW 09:51 AM MitySOM-5CSX Altera Cyclone V Software Development: RE: Performance problem with baremetal code
- Hello Mr. Kempter,
We don't normally run / support bare-metal applications here (we find most folks get into more trouble using bare-metal with this class of processor).
It looks like the linux application is running at the correct... - MA 07:53 AM MityDSP-L138 (ARM9 Based Platforms) Software Development: RE: I2C 0x8 Address
- Yes, works fine now. Thanks Jonathan.
08/01/2014
- JC 01:47 PM MityDSP-L138 (ARM9 Based Platforms) 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 MityDSP-L138 (ARM9 Based Platforms) 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 MityDSP-L138 (ARM9 Based Platforms) 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 MityDSP-L138 (ARM9 Based Platforms) 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 MityDSP-L138 (ARM9 Based Platforms) Software Development: RE: I2C 0x8 Address
- I'm not seeing this hang with or without i2c-2 enabled.
- MA 08:53 AM MityDSP-L138 (ARM9 Based Platforms) Software Development: RE: I2C 0x8 Address
- Yes, v3.2_i2c_wip checked out and compiled as-is.
- JC 08:32 AM MityDSP-L138 (ARM9 Based Platforms) Software Development: RE: I2C 0x8 Address
- Are you saying you run into the hang when only i2c-1 is enabled?
- I tried to do some performance analysis of ARM on MitySOM-5CSX regarding floating point performance in baremetal code. Therefore I wrote the two modules performance.c and mul.c.
*performace.c:*
07/31/2014
- JC 03:36 PM MityDSP-L138 (ARM9 Based Platforms) 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 MityDSP-L138 (ARM9 Based Platforms) 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 MityDSP-L138 (ARM9 Based Platforms) 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 MityDSP-L138 (ARM9 Based Platforms) 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 MityDSP-L138 (ARM9 Based Platforms) Software Development: RE: I2C 0x8 Address
- Yes, it is:
- JC 10:07 AM MityDSP-L138 (ARM9 Based Platforms) 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 MityDSP-L138 (ARM9 Based Platforms) 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 MityDSP-L138 (ARM9 Based Platforms) 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 MityDSP-L138 (ARM9 Based Platforms) 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 MityDSP-L138 (ARM9 Based Platforms) 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 MityDSP-L138 (ARM9 Based Platforms) 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...
07/29/2014
- JC 02:25 PM MityDSP-L138 (ARM9 Based Platforms) 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 would need i2c1 enabled.
Branch: mitydsp-linux-v3.2_i2c_wip
http://support.criticallink.com/gitweb/?p=linux-davinci.... - JC 10:24 AM MityDSP-L138 (ARM9 Based Platforms) 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. Waiting to see what they have to contribute.
- MA 10:12 AM MityDSP-L138 (ARM9 Based Platforms) 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 not yet accessed).
- JC 09:56 AM MityDSP-L138 (ARM9 Based Platforms) 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 long as there has been a transfer over the i2c bus. It probably intended to make sure that an ongoing transfer completes...
- JC 08:56 AM MityDSP-L138 (ARM9 Based Platforms) 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 seen in your stack trace.
- JC 08:50 AM MityDSP-L138 (ARM9 Based Platforms) 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 don't access the i2c bus first.
- MA 08:33 AM MityDSP-L138 (ARM9 Based Platforms) 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), correct???
Correct, no such issues with the stock kernel config.
??Also, are you configuring the pin mux in the ... - MW 07:42 AM MityDSP-L138 (ARM9 Based Platforms) 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 not quite the same as using I2C0 from the command line via i2c-utils or some other driver access (e.g., the EEPROM). Are ...
- MA 05:44 AM MityDSP-L138 (ARM9 Based Platforms) 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 after reboot, attempt to use I2C0 by setting the processor clock: "echo 456000 > /sys/devices/system/cpu/cpu0/cpufreq/sc... - JC 09:09 AM MityDSP-L138 (ARM9 Based Platforms) 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-platforms/wiki/Starter_Guide
07/28/2014
- DB 03:13 PM MityDSP-L138 (ARM9 Based Platforms) 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 MityDSP VM with VB 4.3.14 to load on Win7 laptop without errors)
- MityDSP-L138-SDK.ova installed from DVD
- Ubuntu ... - MW 11:55 AM MityDSP-L138 (ARM9 Based Platforms) 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 the TRM).
As the comments and the TRM suggest, it doesn't look like you can disable slave response mode in the OMAP-L1... - AS 11:33 AM MityDSP-L138 (ARM9 Based Platforms) 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 provision for this. It just writes to all the addresses and see what comes back.
I think the transition of the 0x8 i... - MW 11:29 AM MityDSP-L138 (ARM9 Based Platforms) 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 at 0x08. We note that the u-Boot utility does not detected at address 0x08 and only sees the PMIC at 0x48 and the EEPRO...
- AS 10:49 AM MityDSP-L138 (ARM9 Based Platforms) Software Development: RE: I2C 0x8 Address
- Source : System Management Bus (SMBus) Specification Version 2.0 August 3, 2000 :Appendix C – SMBus device address assignments:
0001 000 SMBus Host System Management Bus Specification v 1.1 December 1998
Does this mean that it is a... - AS 10:20 AM MityDSP-L138 (ARM9 Based Platforms) 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?
- JC 09:54 AM MityDSP-L138 (ARM9 Based Platforms) Software Development: RE: I2C 0x8 Address
- Also on a devkit where the dvi chip was removed the 0x08 address still appears.
- JC 09:52 AM MityDSP-L138 (ARM9 Based Platforms) 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. When I try to read from the 0x08 address I get all sorts of i2c error messages.
- AS 09:31 AM MityDSP-L138 (ARM9 Based Platforms) 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:~# i2cdetect -y 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- 08 -- -- -- -- -- -- ... - MW 08:06 AM MityDSP-L138 (ARM9 Based Platforms) 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 baseboard, they are set to UART2_TXD and RXD to support the RS485 port on J504.
Both the I2C0 and I2C1 ports are exposed o... - AS 07:59 AM MityDSP-L138 (ARM9 Based Platforms) 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 at the "arch/arm/mach-davinci/board-mityomapl138.c"
ret = da8xx_register_i2c(1, &mityomap_i2c_1_pdata);
... - MW 07:55 AM MityDSP-L138 (ARM9 Based Platforms) Software Development: RE: I2C 0x8 Address
- What are you using for your baseboard?
- AS 07:46 AM MityDSP-L138 (ARM9 Based Platforms) 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 f
00: -- -- -- -- -- 08 -- -- -- UU -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -...
07/25/2014
- MW 02:42 PM MitySOM-5CSX Altera Cyclone V Software Development: RE: PCI-e Device Driver - munmap related error
- Can you post your code? Are you getting user space faults and not kernel oops, right?
Are you unmapping with the same size as with your mmap() call?
-Mike
- Posting on behalf of a customer:
I'm having some sporadic problems with the device driver I made for our pci-e device.
It works great in general but it seems like every other run, I get a segfault when trying to
close() the device...
07/24/2014
- AD 09:05 AM MitySOM-5CSX Altera Cyclone V FPGA Development: RE: FPGA DDR3 on 5CSX-H6-42A-RC-X (DDR)
- Hi Nigel,
I don't believe there is a way to do it directly in QSYS. You may be able to patch your generated outputs to get over that hurdle. As you would expect, Altera has the normal minimum frequency requirement programmed in so u... - ND 07:59 AM MitySOM-5CSX Altera Cyclone V FPGA Development: RE: FPGA DDR3 on 5CSX-H6-42A-RC-X (DDR)
- Hi Adam,
Thanks for the insights.
Do you know how to persuade qsys to run the DDR at a slower speed? In normal use it will not allow anything less than 300MHz.
Thanks,
Nigel.
07/23/2014
- PS 11:06 PM MityDSP-L138 (ARM9 Based Platforms) FPGA Development: RE: fpgautil read Issue
- Hi Mike,
I found the issue. I was updating the edo_out signals only when rd was going high.
From the waveform i found rd signal going high after edo_out is driven on the interface.
It really make sense when updated register v... - MW 08:42 PM MityDSP-L138 (ARM9 Based Platforms) FPGA Development: RE: fpgautil read Issue
- Can you post (or email me) you VHDL source related to the loopback register?
Do you have Chipscope? It might be worth using chipscope to track the address / register data through the transfer cycle.
-Mike - I'm using MityDSP-L138 Board. I have implemented a Custom IP in the FPGA board.
I'm using the CS5 ARM Chipselect and using the frame work available in fpga/vhdl directory.
Also, i'm using the fpgautil program in examples dir to read... - AD 04:19 PM MitySOM-5CSX Altera Cyclone V FPGA Development: RE: FPGA DDR3 on 5CSX-H6-42A-RC-X (DDR)
- Hi Nigel,
You are correct, the C8ES devices do not meet timing with the FPGA DDR according to Quartus. The ES silicon was not qualified to any faster speed grades than C8, though it does work according to our tests. We designed the ... - Although your reference design using FPGA DDR compiles as supplied, when I select the correct device (5CSXFC6C6U23C8ES) for my hardware I get timing violations on the FPGA DDR that I have been unable to fix.
I cannot create extra marg...
07/22/2014
- GG 11:42 AM MityDSP-L138 (ARM9 Based Platforms) Software Development: RE: uPP receiving problem
- Hello Silvano,
No, the MDK uPP libraries are not setup to work with the debugger. In your code you can try setting the necessary debug bits, as you pointed out in your last post, after calling the initialize() routine. I remember hav... - SB 08:54 AM MityDSP-L138 (ARM9 Based Platforms) Software Development: RE: uPP receiving problem
- The strange behaviour still continue.
When we do not send data to uPP using the FPGA the program does not have the strange stepping.
Whne we send data to uPP the stepping behaviour still remains even if the optimizations are turned off... - SB 03:10 AM MityDSP-L138 (ARM9 Based Platforms) Software Development: RE: uPP receiving problem
- Thanks a lot for the suggestion.
I will check with my colleague the VHDL connection.
I also had a check at the optimitations but they are all turned off. It is very strange because it is a very simple program.
Any other suggestion, m...
07/21/2014
- Hi,
I'm using the pre-dev MitySOM eval board and I'm trying to rebuild a complete working environment with the current yocto poky distro (linux 3.12) as instructed in the wiki.
Most stuff is working but I have some open question :... - JC 12:41 PM MityDSP-L138 (ARM9 Based Platforms) Software Development: RE: uPP receiving problem
- The strange stepping sounds exactly like when optimizations are turned on.
- DR 11:46 AM MityDSP-L138 (ARM9 Based Platforms) Software Development: RE: uPP receiving problem
- I'm not a VHDL guy, so I can't say whether this will work as you have it. It sounds like you and your VHDL guy should sit together and verify that it is correct. It's best to do this using ChipScope.
I'm not sure why the code is ste... - SB 11:34 AM MityDSP-L138 (ARM9 Based Platforms) Software Development: RE: uPP receiving problem
- Here you can find the VHDL sources.
I cannot help you a lot with VHDL becuse it is developed by a colleague of mine.
Thanks in advance another time to help me.
Silvano - SB 11:19 AM MityDSP-L138 (ARM9 Based Platforms) Software Development: RE: uPP receiving problem
- Thanks a lot.
Now the working principles are clearer.
The problem now is that the software has a strange behaviour.
During the debug operations and the step by step execution, sometimes, after the receive() call, it steps itself back ... - DR 11:09 AM MityDSP-L138 (ARM9 Based Platforms) Software Development: RE: uPP receiving problem
- Each time you call receive, a DMA is set up to fill the buffer you pass. Once that DMA completes, no data will be transferred into memory until another DMA is queued up.
Typically, you will queue up 2 DMA's and as each completes, ano... - SB 10:08 AM MityDSP-L138 (ARM9 Based Platforms) Software Development: RE: uPP receiving problem
- Ok thank you.
I will try to change all the interrupt levels.
Another question is: but once the buffer is filled? What happens? It stops to receive?
Thanks. - DR 10:05 AM MityDSP-L138 (ARM9 Based Platforms) Software Development: RE: uPP receiving problem
- I don't see any reason that it wouldn't work, but I have seen issues with some interrupt levels not working. I strongly recommend that you try some different ones.
The receive command is the start from the software point of view.
... - SB 09:59 AM MityDSP-L138 (ARM9 Based Platforms) Software Development: RE: uPP receiving problem
- Thanks to have a look.
I have the signal enable and start always active.
I think that therefore is right to set bChanAUseStart to true.
I can check all the interrupt level... but i do not think that is a problem.
But supposing the co... - DR 09:49 AM MityDSP-L138 (ARM9 Based Platforms) Software Development: RE: uPP receiving problem
- A couple of things that I see are different from some code that I have working here:
I use nHWInterruptLevel = 7. Perhaps level 4 is already in use...
I use nTskPriorityChanA = 11.
I don't use bChanAUseStart = true. I set this to ... - Dear all,
I am trying to use to uPP to receive data coming from the FPGA.
Attached you can find the code I wrote. Aim of the code should be:
- receive only on the channel A.
- the receiver buffer is 4096 lines and each lines is m...
07/20/2014
- Hi,
I originally wanted to connect to the board either usb storage peripherals or webcams-like peripherals. I bought a MiniUSB-B to Standard-A receptacle adapter. When I try to connect a simple USB stick, it is neither recognized nor...