Hi Sergio,
I could get the ADC7606 interfaced with SPI 1 to work. I was just calling spi_registration & using SPI api's just like in arduino without configuring the GPIO mux [42,43,54,55] for selecting the SPI 1.
To interface to SPI 1, GPIO mux selectors 42,43,54,55 need to be set to 0.
- Regards
Simba
Well, I finally bricked one of my Edison's. That was the bad news, but the good news is I found your post. Since I had a spare 32bit machine with Ubuntu 14.04 installed, I didn't go the pendrive route. I did have to install xFSTK and dfu-util. After extracting the latest image, I ran flashall.sh -b. The flash process seems to work OK, but I'm still not ending up with a working Edison.
Maybe I should backup and confess I bricked it by installing ubilinux. I'm not sure I got a good install of ubilinux for one thing. It basically worked, but I was never able to get a Virtual Com Port to show up nor was I able to get WiFi working. The fact that I lost my Virtual Com Port during that process might be at the heart of why now I can't get reflash this Edison. Since it has no Virtual Com Port, it also has no Edison drive. Now I can't seem to get it back.
Anyway, when I use your process to try unbricking it, I get the following messages:
marv@marv-AOA150:~$ ./flashall.sh -b
Starting Recovery mode
Please plug and reboot the board
Flashing IFWI
XFSTK Downloader Solo 0.0.0
Copyright (c) 2014 Intel Corporation
Build date and time: Oct 18 2014 10:10:36
Intel SoC Device Detection Failed: Attempt #0
Intel SoC Device Detection Failed: Attempt #1
Intel SoC Device Detection Failed: Attempt #2
Intel SoC Device Detection Failed: Attempt #3
Intel SoC Device Detection Failed: Attempt #4
Intel SoC Device Detection Failed: Attempt #5
Intel SoC Device Detection Failed: Attempt #6
Intel SoC Device Detection Failed: Attempt #7
.Intel SoC Device Detection Found
Parsing Commandline....
Registering Status Callback....
.Initiating Download Process....
.....................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................XFSTK-STATUS--Reconnecting to device - Attempt #1
................................................................................................................................Recovery Success...
You can now try a regular flash
Using U-Boot target: edison-blank
Now waiting for dfu device 8087:0a99
Please plug and reboot the board
Flashing IFWI
Flashing U-Boot
Flashing U-Boot Environment
Flashing U-Boot Environment Backup
Flashing boot partition (kernel)
Flashing rootfs, (it can take up to 5 minutes... Please be patient)
Rebooting
U-boot & Kernel System Flash Success...
Your board needs to reboot twice to complete the flashing procedure, please do not unplug it for 2 minutes.
marv@marv-AOA150:~$
As far as I can tell, it never reboots once let alone twice. In any case, if I eventually power cycle it, I get the following:
marv@marv-AOA150:~$ sudo minicom -D /dev/ttyUSB0 -b 115200
Welcome to minicom 2.7
OPTIONS: I18n
Compiled on Jan 1 2014, 17:13:22.
Port /dev/ttyUSB0, 17:32:33
Press CTRL-A Z for help on special keys
******************************
PSH KERNEL VERSION: b0182727
WR: 20104000
******************************
SCU IPC: 0x800000d0 0xfffce92c
PSH miaHOB version: TNG.B0.VVBD.0000000c
microkernel built 23:15:13 Apr 24 2014
******* PSH loader *******
PCM page cache size = 192 KB
Cache Constraint = 0 Pages
Arming IPC driver ..
Adding page store pool ..
PagestoreAddr(IMR Start Address) = 0x04899000
pageStoreSize(IMR Size) = 0x00080000
*** Ready to receive application ***
U-Boot 2014.04 (Oct 14 2014 - 15:19:04)
Watchdog enabled
DRAM: 980.6 MiB
MMC: tangier_sdhci: 0
In: serial
Out: serial
Err: serial
Hit any key to stop autoboot: 0
Target:ifwi
Partitioning already done...
Partitioning already done...
Saving Environment to MMC...
Writing to redundant MMC(0)... done
GADGET DRIVER: usb_dnl_dfu
It always stops at this point.
If I try bringing it up on my Windows machine, I can never connect.
Any thoughts as to what else I can try?
BTW, I have both Arduino and Mini breakout boards. I also backed up my working Yocto image to a SD card before reflashing to ubilinux but can't find a way to use my backup in this situation.
Sergio,
Thanks for the reply, but this will not work as the Edison module will not respond at all when I plug it into Arduino breakout board. This is same method I used to flash current image into Edison that came with Arduino breakout board and for Edison that came with mini breakout board using USB for power. But now for second time Edison I powered through mini breakout board with separate power supply and battery will not respond on com port and does not respond as storage device. Guess I'll again return to Fry's but this time get one with Arduino breakout board as I can get it to work ok.
Hi Sergio,
Initially I had trouble with SPI communications so couldn't verify this problem. Now I have my SPI transfers working.
I am trying to set up sysfs triggers on the gpio for doing adc sampling, & it's giving trouble because the Cypress GPIO expander is built enabling sleep mode. Please let me know how to disable this sleep mode for the gpio expander.
I checked the Driver code in following path, Cy8c9540a.c (drivers\mfd)
I verified with BSP 1.0.1 + 1.0.4 patches, uclibc & eglibc packages it's the same result.
I even tired clearing the flag [can_sleep] as I had mentioned earlier, it still causes a crash and converted result is not available. If I try with out triggers I am able to get the results, but for large scale / continuous data capture in buffers I need trigger option please help me out in trying to disabling sleep option.
Cy8c9540a is registered as a I2C device right, where is the code of this i2c driver, what is the file name of it?
I have attached the log that shows the error for using triggers.
Thanks Dave. Hopefully I won't brick it, but very nice to have in case. Thanks again.
Thanks AlexT_Intel, just saying thanks, your repo is quiet handy.
The sign bit is always the most significant bit in unsigned Integers, whether it is 8, 16, 32, 64 or higher (Bytes, words, integers, int64's).
The external antennae cables might be nice. Standoffs.
I agree with mikemoy, it would be nice to have an image for those that use the edison with breakout board and non arduino/sketch users.
Awesome, looking forward to any further developments.
You said: " I got temperatures in mid 60Cs with a high of 71C with (stock cooler) ". May I ask you a few questions if you don't mind?
1- What is the stress test type you have done to get that temp (FPU stress or CPU stress)? And with what program? Test duration?
2- What is your Vcore and CPU frequency during that stress test?
3- What is your room temperature?
4- Is the air flow inside the case good or not?
5- Your motherboard model?
Note: I get below mid 70Cs @4.2Ghz (Vcore 1.109v) during the normal stress test only using XTU, AIDA64 Extreme, @4.4Ghz (Vcore 1.150v) I get 79c using XTU and steady 73c using AIDA64 Extreme except when I use torturing test using prime95 28.5, AIDA64 Extreme (FPU test) I get ~97c but as I understand those tests (FPU stress test for example) are not a real-life scenario, for the normal usage in the worst case when the CPU is fully utilized I get max peak of 81c (for a short time returning to 79c or 69c-75c dependent on what apps/games are running) @4.4Ghz all using stock cooler, room temp 26c.
Update: using IntelThermalTest v0.2 (c) 2014 by Karwos I get 79c and passed the test.
Do you have the displays configured in clone or extended desktop? Does it make a difference if you change it?
Let me show to you how the option for “Wireless Software Extensions” appear.
UST, thanks for your interest in my problem.
I am real new to c and c++ and arduino so I won't be much help.
I have been using Time.h and time.h for some time and they seem to work some time and then on the next build it will crash and I can't get it to work anymore. I don't know what the variable it that causes the issue.
I have been trying for weeks to simply get a datetime string YYYYMMDD:HHmmSS and am still struggling with this simple request. Funny no one else seems to need this functionality using Arduino and Edison.
Let me know if I can help further.
I was able to RMA my I7 4790k because of a CPU Frequency fail. Got the new chip today no overheating issue, but I STILL FAIL CPU Frequency Test! I submitted a ticket to Gigabyte for the motherboard for this issue now.
Alpha, I am having the same compile error.
joe_intel wrote:
You may get the newer version 17.12 from your system manufacturer’s website.
Ummm, no. I followed your link and then clicked through to Lenovo's downloads page for the Yoga 2 Pro. Their most recent version for the 7260 adapter is 17.0.3. The most recent driver Intel's drivers page shows for Dual Band Wireless-AC 7260 is 17.1.1406.01!
In several Yoga 2 Pros, I replaced the flaky, factory-installed Intel 7260 Wireless-N 7260 (single-band) adapter with its Dual Band Wireless-AC sibling and simultaneously installed the latest drivers available from Intel (17.1.0.19) at the time. For one of the Yogas, I started experiencing the problem the OP and lancia12 reported (same behavior and event logs). Today, on the problem laptop, I downgraded the driver to 17.0.6 as suggested by the OP. Very basic tests suggest the problem has at least diminished. I'll wait to hear from the user...
I have downgraded RST to 12.9.0.1001 and I still cannot mirror my drive but the behaviour is is slightly different now.
I have attached screenshots illustrating the three states.
By the way, I followed the link from this RST support page to this compatibility sheet to determine chipset compatibility for RST, but it is somewhat old and doesn't have a version-to-version compatibility matrix. Is there some way to look up the latest version of RST for a specific chipset (or family)?
Terrence_, the format you are looking for is a string being return by a function in the format YYYYMMDD:HHMMSS ?
Are you programming in C/C++ via the Eclipse IDE provided by the iotdk ?
Hi MyNameIsNathan;
This is Galileo Gen1
This is Galileo Gen2
Check that you are using the correct one in the IDE.
If you were using the correct one, verify that you have all the files that you need in the SDCard, you must have in there:
bzImage
core-image-minimal-initramfs-clanton.cpio.gz
grub.efi
image-full-galileo-clanton.ext3
boot
Also, did you try using another sketch? If it's the same result for all the sketches, do again the Getting Started Guide without the SDcard and the other cables that you were using (just to discard some reasons) . After you finished that, try again with the SDcard in the board and upload again the Blink sketch. Let me know about the results.
Regards.
CMata