the Bootloader would just ignore the 'protected' locked pages) (there is no problem with including the Boot code. If the mEDBG.hex only contains the Application code, there is no longer anything in the Boot area. Using an external programmer will automatically erase the Boot area. This handles the data and programs the Flash in the Application area (only erasing pages as required). Most Upgrade through Bootloader procedures work from code in a locked Boot area. I did not set any Lock bits after the Flash Programming was finished. Programmed and Verified the new Firmware. The ATMEL-ICE will have erased the whole chip. So I used the JTAG header.Īs far as I know, the mEDBG firmware is just a standard application. The 'current' 1.10 would not upgrade itself. to mEDBG 1.10 which worked fine for debugWIRE with ASĪS required mEDBG to be upgraded to 1.13. So I soldered JTAG headers and upgraded the firmware with ATMEL-ICE.
#IMAGE PRO PLUS 7.0 INSTALLATION TOOLS NOT WORKING INSTALL#
When I foolishly let Windows install Win10-64, AS7.0 build 1006 would not self-upgrade the XMINI-168PB or the XMINI-328P. The 168PB has upgraded itself several times from different builds of AS6.2 e.g. I own an XMINI-168PB and recently, an XMINI-328P.
You have a regular mega32U4 chip that handles the USB and mEDBG functionality. Surely the mEDBG firmware is exactly the same for an XMINI-168PB, XMINI-328PB, XMINI-328P. Installation failed due to Norton not liking the SAM B flash tool. I'm running Windows 10 Pro and am up-to-date.
0 kommentar(er)
