I successfully completed an image build for a Trendnet TEW-810DR. It was low hanging fruit - essentially duplicated the D-Link DIR-810L entries.
The latest OEM image has this signature at the end of the *.bin file:
0057a000: 0000 0000 0000 0000 0954 4557 2d38 3130 .........TEW-810
0057a010: 4452 0104 312e 3152 0202 5757 0303 312e DR..1.1R..WW..1.
0057a020: 3005 0731 2e31 3342 3034 2000 0402 0029 0..1.13B04 ....)
0057a030: 8bca 5739 0a ..W9.
Based on this:
https://openwrt.org/toh/trendnet/trendnet_tew-810dr_1.0_1.1
I believe a signature needs to be appended to my build.
My Build:
0037fff0: ffff ffff ffff ffff ffff ffff ffff ffff ................
00380000: dead c0de 0000 0000 0000 0000 7b20 2022 ............{ "
00380010: 6d65 7461 6461 7461 5f76 6572 7369 6f6e metadata_version
00380020: 223a 2022 312e 3022 2c20 2273 7570 706f ": "1.0", "suppo
00380030: 7274 6564 5f64 6576 6963 6573 223a 5b22 rted_devices":["
00380040: 7465 772d 3831 3064 7222 5d2c 2022 7665 tew-810dr"], "ve
00380050: 7273 696f 6e22 3a20 7b20 2264 6973 7422 rsion": { "dist"
00380060: 3a20 224f 7065 6e57 7274 222c 2022 7665 : "OpenWrt", "ve
00380070: 7273 696f 6e22 3a20 2231 392e 3037 2e31 rsion": "19.07.1
00380080: 222c 2022 7265 7669 7369 6f6e 223a 2022 ", "revision": "
00380090: 7231 3039 3131 2d63 3135 3539 3030 6636 r10911-c155900f6
003800a0: 3622 2c20 2274 6172 6765 7422 3a20 2272 6", "target": "r
003800b0: 616d 6970 732f 6d74 3736 3230 222c 2022 amips/mt7620", "
003800c0: 626f 6172 6422 3a20 2274 6577 2d38 3130 board": "tew-810
003800d0: 6472 2220 7d20 7d0a 4657 7830 bb27 8745 dr" } }.FWx0.'.E
003800e0: 0100 0000 0000 00e4 0000 0164 0000 009b ...........d....
003800f0: 756e 7472 7573 7465 6420 636f 6d6d 656e untrusted commen
00380100: 743a 2073 6967 6e65 6420 6279 206b 6579 t: signed by key
00380110: 2037 3963 3334 3037 6438 3835 3162 3965 79c3407d8851b9e
00380120: 630a 5257 5235 7730 4239 6946 4735 3747 c.RWR5w0B9iFG57G
00380130: 3632 4f7a 4a37 6977 702b 7163 3175 5076 62OzJ7iwp+qc1uPv
00380140: 7663 684c 616c 3264 6776 6251 4343 326c vchLal2dgvbQCC2l
00380150: 655a 6768 7941 4e56 474e 5a6d 4d73 3434 eZghyANVGNZmMs44
00380160: 796f 776a 4f7a 3670 6b49 4755 3253 3171 yowjOz6pkIGU2S1q
00380170: 4767 537a 364d 6774 7633 746d 6c52 4856 GgSz6Mgtv3tmlRHV
00380180: 2b50 6577 4d3d 0a00 0100 00c4 8200 00c0 +PewM=..........
00380190: 0005 7563 6572 7400 8500 0014 0008 6365 ..ucert.......ce
003801a0: 7274 7479 7065 0000 0000 0001 8400 0018 rttype..........
003801b0: 0009 7661 6c69 6466 726f 6d00 0000 0000 ..validfrom.....
003801c0: 5e4e c9f3 8400 0018 0009 6578 7069 7265 ^N........expire
003801d0: 7361 7400 0000 0000 602f fd73 8300 006d sat.....`/.s...m
003801e0: 0006 7075 626b 6579 0000 0000 756e 7472 ..pubkey....untr
003801f0: 7573 7465 6420 636f 6d6d 656e 743a 204c usted comment: L
00380200: 6f63 616c 2062 7569 6c64 206b 6579 0a52 ocal build key.R
00380210: 5752 3577 3042 3969 4647 3537 4d47 5159 WR5w0B9iFG57MGQY
00380220: 6768 6e47 4d32 3544 6642 4750 676a 6552 ghnGM25DfBGPgjeR
00380230: 2f6a 6d4b 4943 7362 4d73 6c54 502b 4c70 /jmKICsbMslTP+Lp
00380240: 3337 5849 4f50 720a 0000 0000 0000 00a0 37XIOPr.........
00380250: 0000 009b 756e 7472 7573 7465 6420 636f ....untrusted co
00380260: 6d6d 656e 743a 2073 6967 6e65 6420 6279 mment: signed by
00380270: 206b 6579 2037 3963 3334 3037 6438 3835 key 79c3407d885
00380280: 3162 3965 630a 5257 5235 7730 4239 6946 1b9ec.RWR5w0B9iF
00380290: 4735 374b 5833 4a55 5858 6f66 2f71 437a G57KX3JUXXof/qCz
I could use ncc_att_hwid or copypasta with gvim. Does it need to match the firmware version V1.00? Is there a recommended way or tool to do this in the build infrastructure? Should I pad the image to match the OEM image?