The ICC-A-1 module have an Gecko Application Bootloader installed that only works with OTAU files downloaded thrue Zigbee and stored on the external flash.
So first we need to flash one new bootloader in the internal flash for loading the NCP app in the internal flash.
Flashing new bootloader to the gecko must being done with J-tag or SWD and using elf (not recomended) or s37 files.
Its normaly OK flashing without erasing the internal flash, then you can flash the icc-a-1-bootloader.s37 that contain only the secund stage (Main) bootloader.
If erasing the internal flash you must flashing the icc-a-1-bootloader-combined.s37 or BTL_STD_S1_256-COM_PB14-PB15-PA0.s37 that contains both the first stage and secund stage (Main) bootloader, or your gecko dont boot at all or making cracy GECKO things !
I have booting in to bootloader after erasing internal flash and flashing botloader and reading it back and the first 0x0800 wos only ff = empty, and from the bootloader flashing one app and it wos written it ofset and coruppted the perfials and lockbits aria = Hard brick !!!
NCP app can being flashed from main bootloader with gbl files or with J-tag / SWD with elf file @0x04000 (not recomended) or s37 file.
My first set of NCP gbl file its not accsepted bye the bootloader but the s37 version flashed over SWD works OK.
The NCP_USW_115K2_S1_F256_676_PB14-PB15.s37 its EZSP version 6.7.6.0 and NCP_USW_115K2_S1_F256_664_PB14-PB15.s37 its version 6.6.4.0 of EZSP = our NCP.
My new EZSP 6.7.8.0 can being flashed with SWD NCP_USW_115k2_F256_678_PB14-PB15-PA0.s37 or bootloader NCP_USW_115k2_F256_678_PB14-PB15-PA0.gbl.
If all was going well your Mighty Gecko its transformed in to a "Billy EZSP" and sending "hallo world" in gecko lang...
Windows with Extra PTTY:
▒▒�~
And in Lubuntu with Minicom -H:
Welcome to minicom 2.7.1
OPTIONS: I18n
Compiled on May 3 2018, 15:20:11.
Port /dev/ttyUSB1, 14:13:41
Press CTRL-A Z for help on special keys
1a c2 02 8b c2 8a 7e
And you have a very happy Mighty Gecko !!!
and grobasoz one more time !
for helping making firmware and putting all things together to a working firmware set for the "Billy EZSP" ! ! !
For flashing your module look at Flashing-MG:
If you like populating the user data with custom manufactur info then flash the LED1836G9_UD_MW.elf in at 0x0fe00000 and you getting the data loged in your HA logfile :-)))
2020-08-30 10:17:39 INFO (MainThread) [bellows.zigbee.application] EZSP Radio manufacturer: IKEA of Sweden
2020-08-30 10:17:39 INFO (MainThread) [bellows.zigbee.application] EZSP Radio board name: Billy EZSP by MW
2020-08-30 10:17:39 INFO (MainThread) [bellows.zigbee.application] EmberZNet version: 6.7.6.0 build 327
(Its one dumped user data from one IKEA LED1836G9 and patched with manifactur name, board name and manuactur ID and stay in the flash untill doing one device erase)
New version that is adding the tocken with Simplicity commander:
.\commander.exe flash --tokengroup znet --tokenfile .\tokens-MW.txt -d EFR32MG1P132F256IM32
WARNING: The string for token MFG_BOARD_NAME (Billy EZSP by MW) fills all 16 bytes of the token space. The string will not be zero terminated.
Writing 2048 bytes starting at address 0x0fe00000
Comparing range 0x0FE00000 - 0x0FE007FF (2 KB)
Erasing range 0x0FE00000 - 0x0FE007FF (1 sector, 2 KB)
Programming range 0x0FE00000 - 0x0FE001FF (512 Bytes)
Programming range 0x0FE00200 - 0x0FE003FF (512 Bytes)
DONE
Shall being posssiblee adding to the firmware file 2 with this syntax only adapting it to the privius command:
$ commander convert blink.s37 --tokengroup znet --tokenfile tokens.txt --device EFR32MG1P --outfile blink.hex Converts blink.s37 to hex format, while simultaneously defining the tokens defined in tokens.txt and on the command line.
S37 as in file and the out file difrernt with s37 fille or one GBL. Both method shall prudusing this from bellow info:
Manufacturer: IKEA of Sweden
Board name: Billy EZSP by MW
EmberZNet version: 6.9.0.0 build 178
But with one other EZSP version ;-))
The token is stored in the user data and is staying if doing flash erase and normal firmwar flashing but not chip erase.
More firmware for Billys is putted in EFR32 FW like one router with button joining / leaving and newer EZSP allso with direct shildren = 0 for forcing end device using routers.