I upgraded to the latest version and the behaviour is the same. I'll be honest I am a novice to hardware and Edison in general, so you'll have to go slow with me. How would I go about diagnosing the issue using a gpio pin?
thanks
↧
Re: Addressable LEDs and Edison
↧
Re: storyboard Pro vs ig7icd64.dll
Hi Allan,
the problem stills occur.
Damn !
Here is the log
Thx
| StoryboardPro.exe |
| 10.2.2.9744 |
| 546c05e4 |
| ig7icd64.dll |
| 10.18.10.4061 |
| 548e650a |
| c0000005 |
| 00000000003f77c2 |
| 1e60 |
| 01d06873cbfe0fb0 |
| C:\Program Files (x86)\Toon Boom Animation\Toon Boom Storyboard Pro 4.1\win64\bin\StoryboardPro.exe |
| C:\WINDOWS\SYSTEM32\ig7icd64.dll |
| 17581f1c-d467-11e4-be9f-681729eacb2f |
And a screencast
↧
↧
Re: Problems bitbaking ww05-15 edison-image
if you download it manually you should change the URL to file:// - e.g. as described in my blog in another context: Some hints on Yocto builds for IoT devkit - example: adding Java JRE | Intel® Developer Zone
↧
Re: I'm having Intel(r) HD Graphics 2500 compatibility issues with Empire Earth I.
I attempted to install that driver, however, it informed me that my computer was incompatible with that driver. Something to the effect of 'does not meet the minimum requirement of this software'.
Adjusting gamesettings have had no visual effect on the issue.
↧
BOSD when trying to install drivers for Intel HD Graphics 4600
I have a Hasee Shenzhou Ares K710C-i5 D1
Relevant Specs:
CPU: Intel Core i5 4200M with HD 4600M Graphics
Graphics: Nvidia GForce GT 750M
Unsure of type of Mobo
Boot disk: Samsung HN-500MBB / Seagate ST500LM012
OS: Windows 8 Pro 64-bit
The BSOD occurs during the installation of the new update. Has even caused my laptop to BSOD when trying to restart from the previous ones.
The BSOD code was: VIDEO_DXGKRNL_FATAL_ERROR
↧
↧
Re: 7260 ac, missing Microsoft Bluetooth Enumerator device, code 10 & 43 [pic] [updated]
Running busy lately
Until intel gives words, here I offer my UNOFFICIAL confirmation that TA G86254-001 is faulty.
Basically, I got myself a newer one with TA# H42623－002, all problems zap away: bluetooth works properly, weird antenna issues gone * (not stated in OP).
I also found out these TA numbers are faulty with various problems:
G86254-00x, G86255-00x, G86603-00x
After further research, I can speculate that If your TA# is "below" G94295-003, there is a high possibility that you've got a faulty one, especially when your card is shipped from China, Hongkong and South Korea.
The things still bug me are that I dont have Bluetooth "4.0" displayed anywhere (missing bluetooth version number). And, i got "Microsoft Bluetooth Enumerator" but no "Microsoft Bluetooth LE Enumerator".
Intel, is this intended?
My current bluetooth driver is : WP-BT_17.1.1411.01_s64
*the antenna issue with G86254-001: [on desktop machine]. 1. If no antenna attached, 60%-strength wifi signal can still be received; but after connecting to a wifi, internet connection is not available (big yellow triangle exclamation mark on wifi icon). 2. if the antenna is attached, internet connection only works when the antenna points at certain direction, despite the fact the received signal strength is always 100% .
When I use H4263-002, no such problems.
↧
Re: Is there any m.2 500GB HDD that will work in the new 5i5 and 5i7 NUC's?
Thank you Sylvia, I have reviewed the list but do not see any 500GB SSD products tested.
↧
Edison I2C Problem With Grove RGB LCD...
I'm using an Edison on a Arduino breakout board. Recently i reflashed the board because of a corrupted image, and now all seems ok during boot. The version I flashed was 16. I uploaded the blink sketch: It worked. The grove lcd hello world sketch worked too. Then i upgraded the image to version 120. Then again after setup and all i uploaded the lcd test sketch. I could see the lcd was receiving power, but no text was displayed, nor did the backlight work. I tried connecting the lcd directly to A4/A5 AND SDA/SCL, in all possible configurations, but nothing worked.
It seems something happened after the upgrade. Should I be installing some package or something? I have already created an unofficial opkg repository and run an opkg update. I think the I2C isnt working for some unknown reason... Please HELP!!!
↧
Re: Intel NUC DN2820 as a router
I am adding an attachment of the error-
↧
↧
Re: плата intel s3420gpc и hdd SATA 3Tb
Для тестирования были приобретены диски 3,5" WD Red 3TB.
В BIOS диск определился объемом в 800 Gb.
Плата не работает с такими объемами.
Тему можно закрыть
↧
Can't enable eDrive on Pro 2500 Series
I am trying to enable eDrive to use with bitlocker. It is telling me that the firmware is not up to date.
C:\Intel_SSD_Pro_Administrator_Tool_win64>SSDProAdminTool_1.1.0_win64.exe -drive_index 0 -enable_edrive
------------------------------------------------------------
| Drive Index: | 0 |
------------------------------------------------------------
| Drive Series: | Intel SSD Pro 2500 Series Opal Ready |
| Model Number: | INTEL SSDSC2BF180A5L |
| Serial Number: | |
| Firmware: | LTVi |
| Current MAX LBA: | 0x14F5C82F |
| Drive Status: | Healthy |
| Opal State: | Opal Ready |
| eDrive Supported: | False |
| Native MAX LBA: | 0x14F5C82F |
| Current Percent: | 100.00 |
| Current Capacity: | 180.05 GB |
| SMART: | ON |
| DIPM: | ON |
| Write Cache: | ON |
------------------------------------------------------------
Error: enabling eDrive with this tool is not supported on the selected Intel
SSD. Please ensure the tool and the drive's firmware are up to date.
↧
Re: Drivers Problem for NUC5i3RYH
Problem solved:
First: ACPI\INT3397\2&DABA3FF&1 <== FIXED (automaticly) with upgrade to the new bios
Second: {55BC022C-955B-4D87-A88D-D3E68CBEB2F4}\CT_27B961DB-3057-49BB-BD0D-ACA9FD8FF697\4&F133739&0&00 <== "FIXED" I have disable the NFC in the bios.
Thanks to all for your help.
↧
yocto os built failed while building the EDKII Firmware
Hello everyone,
I am trying to build yocto os for intel galileo gen2 by using UBUNTU 14.04 LTS (64 bit) as build machine.
In this process while building the EDKII firmware i tried
#./buildallconfigs.sh GCC482 QuarkPlatform
and i got the following error (GCC version is same as installed version 4.8.2 on my ubuntu )
root@iot-desktop:/home/iot/Desktop/Quark_EDKII_v1.1.0# ./buildallconfigs.sh GCC48 QuarkPlatform
Missing OpenSSL dir CryptoPkg/Library/OpensslLib/openssl-0.9.8zb
Please follow instructions in CryptoPkg/Library/OpensslLib/Patch-HOWTO.txt
root@iot-desktop:/home/iot/Desktop/Quark_EDKII_v1.1.0#
i dont have any directory like CryptoPkg/Library/OpensslLib in my workspace directory "Quark_EDKII_v1.1.0".
how to get that directory?
please anyone help me how to overcome this error.
↧
↧
Re: SSD DC S3700 series Model SSDSC2BA800G3P compatible with VMWare VSAN6
Hi it came pre-installed in a couple of HP servers which we have since disposed of We kept these drives as we intended to use them in a Dell configured VSAN setup using 3 x R720xd servers as hosts with a hybrid disk storage array consisting of 2 x 691851-001 SSDs as cache and 12 x 3TB HDDs in each host. So in total 36 HDDs and 6 SSDs
↧
galileo gen2 firmware upgrade fail
i use the arduino 1.5.3 to update firmwae but it fail, then i found my board can not connect with computer and usb led not light. how should i do to fix it.
the power led can light.
please help me...
↧
DP55KG will not boot to USB or DVD
Greetings,
I have the DP55KG motherboard that's been in my self-built system since 2010 and has had Windows Vista Ultimate x64, Win 7 Ultimate x64 & Win 8.1 Pro x64. It's been flawless except for one consistent issue: It will not boot to a USB drive/stick or a DVD drive, not matter what I've tried.
I've built a lot of computers and tinker with them all the time and am pretty well versed in configuring them properly. I've done the usual BIOS updates, configured the board for USB or DVD boot, etc., etc., over the years to test variations for getting it to boot to USB/DVD...but nothing has ever worked.
When I create the usual recovery USB sticks or other utilities that are common, my computer will not boot with the stick plugged in.
- If the Windows hard drive is connected, she'll bypass the USB stick and go to the HD and load Windows.
- If I disconnect the hard drive and only the USB stick is remaining on boot, she'll throw the black screen stating that no boot device has been detected and stop.
- Over the years, I've tried different USB sticks on different USB ports on both the motherboard and via USB hubs, with fresh burns of Windows recovery files.
Nothing I've tried has EVER got a USB stick to boot.
This same issue occurs if I try to boot from CD/DVD, such as using the Windows Vista, 7 or 8 install or recovery discs., with one exception:
- With the Windows hard drive connected, the DVD is bypassed on boot (no matter the BIOS settings), and Windows continues to load from the hard drive like normal, instead of going to the DVD.
- If I disconnect the hard drive, THEN the DVD will be seen and booted from, whether it's a Win install disc or recovery disc. A hard disk will not be seen, of course.
- If I then reconnect the hard drive at this point, things progress as normal and I can access tools or install/reinstall the O/S. This is the only way I've found to install/reinstall an operating system or access recovery tools on Win discs.
- Over the years, I've tried different DVDs with fresh burns of Windows recovery files, as well as the original install discs for Vista, Win7 & 8.
Recently, I've been downloading & installing the preview builds of Windows 10 via the MS Insider Program. This same motherboard issue is also present when trying to install the ISO via DVD or USB on to a completely different hard drive connected to this motherboard. During this, my Windows hard drive described above was disconnected because I keep them separate from the Windows 10 install hard drive (When I want to tinker with Win 10, I pull my Win 8 drive and connect my Win 10 drive. I do this on purpose because of early 10 builds that others reported corrupting Win 7 & 8 system drives that were concurrently connected).
- The only way I could get the Win 10 DVD burn to install on the fresh drive was if I disconnected the fresh drive before cold boot. Then during boot up, the motherboard would see the DVD and launch the install program. At this point, I reconnected the fresh drive and the install could progress.
Note: All motherboard USB ports, external USB hubs, and all internal or external DVD drives work normally once Windows boots & loads. I don't have any defective USB ports or connections.
This has been a very frustrating problem because it prevents the usage of any USB sticks for booting to ISO's or recovery tools, or system images on large USB drives. The workaround of disconnecting all drives to get a DVD boot is a band-aide solution that doesn't workaround getting usage of USB booting.
I've searched all over for any resolution to this issue, but have found none. Does anyone have any idea why this occurs and how to resolve it?
Thank you.
↧
Re: galileo gen2 firmware upgrade fail
Hi leo
Since none of the real experts has answered, maybe i could get you started with some troubleshooting. From your description, I guess you were trying to update the firmware and it failed during the updating. If so you may have corrupted the firmware. Do you have a FTDI cable like this Intel® Galileo Boards and Kits — Console Serial Cables? if so connect it up to your computer and run a program like putty. If you have windows you will need to install drivers, see How to Install FTDI Drivers - learn.sparkfun.com for a discussion. Configure Putty with115200 Bit/s, 8 Bit, 1 Stop and No parity seeSetting up the Windows Environment for details. After you have all set up, power up the Galileo and see if you are getting any messages. If get "ASSERT_EFI_ERROR" or nothing, than you need to go through re-flashing the firmware. You can start with Fixing a "bricked" Galileo — Clay and Galileo or if you don't have access to a SF-100 DedProg there are some more instructions that I will have to search for.
If serial shows it boots normally than pass on the error message you get.
regards
rgb
↧
↧
Re: galileo gen2 firmware upgrade fail
Hi Leo
Just noticed that cmata answered a similar question in I think I broke my Galileo Gen 2 and gave the links for recovery
rgb
↧
Weird one; mraa ISR, threading, and opening a serial port = weird problem
Ok, this is going to sound weird, but here's what I'm dealing with. I'm really not sure how else to put it
I have the seeed studio arduino shield and an attached grove button on the Edison/arduino breakout board. I have this set up in code with an interrupt so I can do things when the button is pressed. This is working fine.
Then I add some code that creates a new thread. In the new thread, I open the serial port, and loop to read a constant stream of data and write it a file on the SD card. This also works just fine.
Except, the ISR does not work if it's the first time I ran the program after rebooting the edison
Sequence of events:
- boot the edison (either cold boot, or by 'reboot' from the command line)
- log in
- Execute the program
- Press the button, the ISR does not fire (also ran in the debugger with a breakpoint, the ISR function is never called) (MRAA_SUCCESS is returned, even though it doesn't fire)
- ctrl+C to close the program
- Arrow up, and run the program again
- Press the button, and the ISR does fire this time (and every other time I run the program until cold/reboot).
Below is the entirety of my stripped down program. If I comment out line 38, the ISR will fire every time the program runs, including after the initial reboot.
If I move the opening of the serial port outside the new thread, to the original thread, then everything works fine. I came across this issue since I wanted to kick off the new thread, and have it do all of it's initializing itself, rather than in the main thread. I'm fine with that workaround, but this issue is just so... weird. It seems to me like it should just work, but I've never used threads before, so I may be overlooking something simple. open() should be thread safe, but looking around online, sometimes the file descriptor table isn't?
I've tested on two different Edisons, one using the latest image available, the other is a little older. mraa version is 0.6.1 (I believe, the newest available).
Anyways, I'm out of ideas
#include <iostream>
#include <mraa.h>
using namespace std;
mraa_gpio_context gpioIn, gpioLED;
//Just print a character in the button ISR
void ISR_button4(void *)
{
printf("I\n");
}
//initialize the button input
//The button is pulled down, then tied high when pressed
void ISR_Button_Init()
{
gpioIn = mraa_gpio_init(4); mraa_gpio_dir(gpioIn, MRAA_GPIO_IN); mraa_gpio_mode(gpioIn, MRAA_GPIO_PULLDOWN); int iRet = mraa_gpio_isr(gpioIn, MRAA_GPIO_EDGE_RISING, &ISR_button4, NULL); //create the ISR function if (iRet == MRAA_SUCCESS) printf("ISR good\n"); else printf("ISR bad\n");
}
void *ML_Run(void*ptr)
{
printf("Hello from thread\n"); char portname[] = "/dev/ttyMFD1"; //Open the serial port... int fu = open (portname, O_RDWR); // Opening the serial port like this doesn't work either //FILE * fdsp = fopen(portname, "w+"); while (1) sleep(1);
}
int main()
{
pthread_t tLogThread; mraa_init(); mraa_uart_init(0); ISR_Button_Init(); gpioLED = mraa_gpio_init(13); //initialize the LED output mraa_gpio_dir(gpioLED, MRAA_GPIO_OUT); //make the LED an output //set up ISR call mraa_gpio_isr(gpioIn, MRAA_GPIO_EDGE_RISING, &ISR_button4, NULL); pthread_create (&tLogThread, NULL, ML_Run, NULL); //create the thread to loop and do nothing cout << "Hello world" << endl; //now just sit and wait for stuff to happen while (1) { sleep(1); printf("0\n"); } return 0;
}↧
Re: Another boot problem with SD and Galileo Gen 1 - what can I do next?
Hi Abix
Looking at all of your posts, it seems you have a problem updating the firmware, using Yocto Linux and connecting to the Internet.
Regarding the firmware, when you do an update you need to boot without an SD card, however it seems from the information provided by the update tool your are already at 1.0.4, so I don't think this is a problem.
As for the OS, what you use depends on what you want to do. The Debian versions are fine, as long as you don't want to use the Arduino IDE and are ok with limited support. I have used is the one put out by EmuTek www.emutexlabs.com, but mostly for the Python support.
Regarding Yocto Linux. First make sure you have a good SD card - cat 10 - format the entire card as Fat32 and probably get at least 4GB. Your last image looks like the Galileo couldn't find the image file so you may have a corrupt card.
Instead of the standard Yocto package I use a version put out by AlexT http://alextgalileo.altervista.org/blog/updated-galileo-devtools-image/ which includes development tools and access to a repository (use opkg to update and install new packages). I also use it with the wiring_x86 by emutex so can control devices with Python. You can also try IoT IDK if you are interested in using Node.js. https://software.intel.com/en-us/iot
Once you have a stable version running, you can connect using the serial cable and get the IP address by running ifconfig, or use a tool like Angry IP Scanner, so you can SSH in and check your configuration. (I run a small Python program on startup that displays the IP address on a i2c LCD screen). By default, if you use one of the standard OS versions I mentioned, it should automatically get an IP address.
Hope this is of some help.
rgb
↧