(Cross-posted from support ticket #35547 .)
I'm really sorry, I made a big mistake trying to diagnose this issue: I didn't do a full uninstall/reinstall. I'd forgotten that the packcode symlink was one I made back in December when first trying to figure this issue out before getting distracted by ...
Search found 4 matches
- Fri May 05, 2017 12:24 pm
- Forum: NetBurner's Eclipse IDE
- Topic: _APP.s19 built incorrectly on macOS?
- Replies: 3
- Views: 5429
- Tue May 02, 2017 1:49 pm
- Forum: NetBurner's Eclipse IDE
- Topic: _APP.s19 built incorrectly on macOS?
- Replies: 3
- Views: 5429
Re: _APP.s19 built incorrectly on macOS?
Spoke too soon: Application record checksum fail That's what the debug port tells me after AutoUpdating or FLAshing any new builds, including self-built copies of the dualserial firmware. (I can flash the stock dualserial_APP.s19 OK so I don't think there's a problem with the way I'm feeding the ...
- Tue May 02, 2017 12:44 pm
- Forum: NetBurner's Eclipse IDE
- Topic: _APP.s19 built incorrectly on macOS?
- Replies: 3
- Views: 5429
Re: _APP.s19 built incorrectly on macOS?
Looks like the packcode binary on macOS is just a symlink to bpackcode which produces a binary output file, not an S-record as on Windows. I've made a POSIX-safe port of the real packcode; see the change history of that Gist for details.
- Mon May 01, 2017 2:49 pm
- Forum: NetBurner's Eclipse IDE
- Topic: _APP.s19 built incorrectly on macOS?
- Replies: 3
- Views: 5429
_APP.s19 built incorrectly on macOS?
I'm developing for the SBL2e using NBEclipse and NNDK 2.8.3 on macOS. When I build my project, the .s19 file produced seems reasonable: $ head sbl2e-acc.bpr.s19
S014000073626C32652D6163632E6270722E73313942
S315FFC04010207C20007FFCB1FC0000000067022E4818
S315FFC040204E56FFF841F92000040045F9FFC18CE068 ...
S014000073626C32652D6163632E6270722E73313942
S315FFC04010207C20007FFCB1FC0000000067022E4818
S315FFC040204E56FFF841F92000040045F9FFC18CE068 ...