Page 3 of 3
Re: OTA update problem
Posted: Wed Oct 28, 2015 9:39 am
by danicampora
Hi Sebastian!
Well done
You also need to modify two more defines in that file. In order to use GP22 (like the LAUNCHXL):
Code: Select all
#define MICROPY_SAFE_BOOT_PRCM PRCM_GPIOA2
#define MICROPY_SAFE_BOOT_PORT GPIOA2_BASE
This is because GP28 belongs to GPIO PORT 3, while GP22 belongs to the GPIO PORT 2.
Cheers,
Daniel
Re: OTA update problem
Posted: Wed Oct 28, 2015 9:11 pm
by Sebastian
Thanks Daniel.
There was another define at the end of the file which has to be changed...
So for anyone who is interested to change the SafeBoot Pin to 22 the mcpconfigboard.h file in the /boards/WIPY folder should look like this:
Code: Select all
#define WIPY
#define MICROPY_HW_BOARD_NAME "WiPy"
#define MICROPY_HW_MCU_NAME "CC3200"
#define MICROPY_HW_ANTENNA_DIVERSITY (1)
#define MICROPY_SYS_LED_PRCM PRCM_GPIOA3
#define MICROPY_SAFE_BOOT_PRCM PRCM_GPIOA2
#define MICROPY_SYS_LED_PORT GPIOA3_BASE
#define MICROPY_SAFE_BOOT_PORT GPIOA2_BASE
#define MICROPY_SYS_LED_GPIO pin_GP25
#define MICROPY_SYS_LED_PIN_NUM PIN_21 // GP25 (SOP2)
#define MICROPY_SAFE_BOOT_PIN_NUM PIN_15 // GP22
#define MICROPY_SYS_LED_PORT_PIN GPIO_PIN_1
#define MICROPY_SAFE_BOOT_PORT_PIN GPIO_PIN_6
#define MICROPY_PORT_SFLASH_BLOCK_COUNT 96
Building the bootloader and application worked for me with
make BTARGET=application BTYPE=release BOARD=WIPY
make BTARGET=bootloader BTYPE=release BOARD=WIPY
Flashing worked perfect with the expansion board and connecting the testpoint to 3.3V.
Re: OTA update problem
Posted: Thu Nov 05, 2015 4:20 am
by drohm
I just got my WiPy today and am experiencing this as well. I got two and both are showing the same exact symptoms. I followed the assembly with the expansion board
here so I know I'm assembling it correctly. Any idea why both WiPy's are bad? Not sure what to do now.
Thanks.