Frankthetech
Member

Ya I get that kind of break up too. The first two 0x08 and 0x04 are easy to combine. but at only 12 bytes would need to grab 4 bytes from the next line too. just need to compute the right checksum. :04 AD78 00 F8 B5...

Great stuff! It works with my file 8120 lines x 16 bytes = 129920 bytes code size flashed with no problem. Code seems to work as expected, will test and report. Joe thanks for making this work. now we have a way to do...

I was able to get it working. Flasher3b has no problem with 130k code size. uploaded and works. Thanks for all the help! Still some more to do, make code with the flasher and test.

I working on this some more and looking into the code compiled I see this about middle of the code (about 129k total code size) :10FFE000704700BF18EA0100054A02608A7D02716D.....

I did some work on this, just trying to understand the workings of the hex file. I complied a blink program, looked at the hex file and found that at about 3/4 into the file was a misaligned data line....

Thanks for your help, if I can help with coding, testing just let me know.

I'm using notepad++ then arduino only to compile and teensyduino to load. target is t35 code is about 129k

I must be lucky..lol I can still upload the flasher code to the t35. I dont try to :flash xxx if it reports a mismatch. so no bricked teensy yet. I'm still thinking it might be intelhex limits to 64k

I'm testing and am wondering if the problem is with intelhex, seems it only reports memory 0000 to ffff written. the flasher works with code converted thats under ffff bytes in length. ...

I have gotten some success in this with your help, I need some help understanding this output done, 4097 hex lines, address range 0:10000, waiting for :flash 4097 lower FSEC (fffff9deffffffff) and upper FSEC...

Thanks for your help. I will work on this and see if I can get it working.

will this be all I need to add to the code #define FLASH_SIZE 0x80000 // 512Kb of program flash #define FLASH_SECTOR_SIZE 0x1000 // 4Kb sector size #define FLASH_WRITE_SIZE 8 //...

Can the flasher3b version handle the hex file output from the complier? or is it necessary to convert it with intelhex.exe first? when I try to use the hex file as is I get 'flash_block align error cant flash 4 bytes...

That did it, thanks. I missed that somehow. What is the best way to send the file to the teensy? Realterm? other?

I've tried the flasher 3b and it goes well till it responds with lower FSEC and upper FSEC match then stops, the example file never runs. Am I missing something? If I power cycle the t3.5 it still has the flasher code...