I know you were having problems while creating a project, I would like to verify that you do not have the problem on Fatal error: can't create ../drivers/debug/quark_d2000/obj/qm_adc.o: No such file or directory anymore.
Also, is this the first time you upload a code to the board or have you been able to upload a code before?
Could you post a screenshot of what you get in Device Manager > Ports and Device Manager > Universal Serial Bus controllers while having the board connected?
We have seen this issue with the ROM Flash/Verify timing out on some versions of Windows - Intel® Quark™ Microcontroller D2000 - Update Target ROM Fails : Could not update the ROM. Flash Rom Failed
If you are still having an issue with Flashing from ISSM the workaround is to try updating the ROM from the command line Intel® Quark™ Microcontroller D2000 - How to flash the ROM from the Windows Command Line
When i tried to do multiple times it was OK.
When i started updating ROM initially it got passed at one shot. Later i have written program to put the system into SLEEP mode and waking up through GPIO. Looks like MCU is not coming out from Sleep mode and i could not able to load any other program. so, i have decided to update ROM then observed this problem.
However, when i am trying it for multiple times (20 times) ROM has got updated successfully. As per your suggestion, let me try with command line mode.
Need more help, can you please send me sample code to put the system into SLEEP mode and waking up out (WITH RTC mode)
Thanks for your support.
Have you already had a look at the 'power' example provided in the ISSM Sample Applications ? It includes code to do the following :
Halt CPU -- Wake up on RTC Alarm
Go to Sleep -- Wake up on RTC Alarm
Go to Deep Sleep -- Wake up on Comparator Interrupt
If running the code as it is make sure to connect pin A5 on the CRB to GND before you start.. in order to bring it out of deep sleep.
Thanks for the update. I will ask my team to check on this.
I have two clarifications.
1. What is the necessity of connecting A5 on the CRB to GND before we start?
2. Can we configure RTC to wake up SoC for every 12hrs ?
3. Can you please post small code snippet to configure GPIO to wake up the SoC
Please do the needful.
Q1 . Explanation of why you need to connect A5 to GND is provided in the coments of the 'power' example
/* On the Quark Microcontroller D2000 Development Platform this pin is marked
* as "A5".
* This pin should be connected to ground before running the example!
* If not, the irq would be run before going into deep sleep. The callback
* will turn-of the gpio/comparator irq. This will result in the board not being
* able to recover from deep sleep.
#define WAKEUP_COMPARATOR_PIN (6)
#define USE_COMPARATOR_FOR_DEEP_SLEEP (1)
Yes - just set the rtc_cfg.alarm_val e.g.
rtc_cfg.alarm_val = QM_RTC_ALARM_HOUR * 12;
Available QM_RTC_ALARM_* values are ....
#define QM_RTC_ALARM_SECOND (32768 / BIT(QM_RTC_DIVIDER))
#define QM_RTC_ALARM_MINUTE (QM_RTC_ALARM_SECOND * 60)
#define QM_RTC_ALARM_HOUR (QM_RTC_ALARM_MINUTE * 60)
#define QM_RTC_ALARM_DAY (QM_RTC_ALARM_HOUR * 24)