Search found 60 matches
- Mon Jun 03, 2019 10:16 am
- Forum: Projects
- Topic: DIY evaluation board with XE216-512-TQ512
- Replies: 24
- Views: 65154
Re: DIY evaluation board with XE216-512-TQ512
I don't know :) I didn't take into account DSD when was working on this evaluation board.
- Tue May 28, 2019 12:54 pm
- Forum: Projects
- Topic: DIY evaluation board with XE216-512-TQ512
- Replies: 24
- Views: 65154
Re: DIY evaluation board with XE216-512-TQ512
You can find the latest revision on the GitHub repo: https://github.com/eez-open/xmos-eval-board Please note that I've put this project on hold due to inability to get proper support regarding software part. At least I can say that USB connectivity worked on the first prototype and that I've added v...
- Wed Mar 07, 2018 11:02 pm
- Forum: Projects
- Topic: DIY evaluation board with XE216-512-TQ512
- Replies: 24
- Views: 65154
Re: DIY evaluation board with XE216-512-TQ512
No, that is something used in examples found on GitHub.
- Wed Mar 07, 2018 5:54 pm
- Forum: Development Tools and Programming
- Topic: Custom flash support in xTIMEcomposer
- Replies: 23
- Views: 19156
Re: Custom flash support in xTIMEcomposer
Argh, that's crazy! Yes, you are right, for some reason a wrong flash is ordered and soldered on two boards :(. Updated header and config files are attached for further reference.
- Wed Mar 07, 2018 5:33 pm
- Forum: Projects
- Topic: DIY evaluation board with XE216-512-TQ512
- Replies: 24
- Views: 65154
Re: DIY evaluation board with XE216-512-TQ512
So far I succeed to establish connection with custom (not natively supported) flash memory, get its ID, erase and upload code into it. Also I manage to run few USB examples. I stuck with SDRAM. Most of examples returns error in assembler like for app_sdram_demo : Test suite begin 8 threaded test sui...
- Wed Mar 07, 2018 3:02 pm
- Forum: Development Tools and Programming
- Topic: Custom flash support in xTIMEcomposer
- Replies: 23
- Views: 19156
Re: Custom flash support in xTIMEcomposer
After trying to establish communication for many hours, I find out the datasheet info for used flash memory include wrong Device ID number: 0x1f 84 01 instead of 0x1f 85 01. With proper config file (i.e. Adesto.txt) the xflash returns the following (Don't forget to first run source SetEnv on Linux!)...
- Mon Mar 05, 2018 1:04 pm
- Forum: Projects
- Topic: XS1-L1 TI DP83848 Ethernet PHY Prototype
- Replies: 6
- Views: 21689
Re: XS1-L1 TI DP83848 Ethernet PHY Prototype
Hi Bianco, I'd like to test Ethernet based on your design with DP83848C. I have a problem with finding out which GiHub branch to use for sc_ethernet (currently dozen of different branches exists in that repository).
Many thanks in advance.
Many thanks in advance.
- Fri Feb 23, 2018 1:51 pm
- Forum: Development Tools and Programming
- Topic: Custom flash support in xTIMEcomposer
- Replies: 23
- Views: 19156
Re: Custom flash support in xTIMEcomposer
Ok, I found that sending on 4-bit port is actually the same as to the 1-bit (only value is 4-bits :). I can say that all signals comes to flash as expected. Therefore flash (two of them on two boards) or XMOS QSPI routine doesn't work properly. We'll see what will happen with bit-banging and your co...
- Fri Feb 23, 2018 1:39 pm
- Forum: Development Tools and Programming
- Topic: Custom flash support in xTIMEcomposer
- Replies: 23
- Views: 19156
Re: Custom flash support in xTIMEcomposer
Great, I'll try what you sent, but for anything more on programming side I need assistance of my colleague who is not here today. But, I already managed to send 500 Hz signal to two 1-bit ports (CS and CLK) using the following code: #include <xs1.h> #include <timer.h> out port qspi_cs = XS1_PORT_1B;...
- Fri Feb 23, 2018 12:54 pm
- Forum: Development Tools and Programming
- Topic: Custom flash support in xTIMEcomposer
- Replies: 23
- Views: 19156
Re: Custom flash support in xTIMEcomposer
I think you are close. Time permitting, no promises but will see if we can simulate this at work. Considering for us to test as-is with the XCORE-200 Explorer kit and then repeat after replacing with some random QSPI flash device. If you are really ambitious - which you are :) You could apply some ...