# Can't get rom.bin to boot

**URL:** https://forums.digi.com/t/cant-get-rom-bin-to-boot/4915
**Category:** NET+OS
**Tags:** jtag, recover
**Created:** [March 26, 2010, 9:14pm UTC](https://forums.digi.com/t/cant-get-rom-bin-to-boot/4915 "2010-03-26T21:14:38Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![burl](https://avatars.discourse-cdn.com/v4/letter/b/47e85d/32.png) [@burl](https://forums.digi.com/u/burl)
#### Post date: [March 26, 2010, 9:14pm UTC](https://forums.digi.com/t/cant-get-rom-bin-to-boot/4915/1 "2010-03-26T21:14:38Z")

</div>

I’m trying to build a release version of my application. When I ftp the rom.bin file, I see the following come out the serial port:

```auto

Download complete, writing to flash...
Firmware updated, quit the session to restart.
Resetting the system in 2 seconds...

Starting TFTP recovery...

```

I never boots back up. At that point, the only way I can run is with the JTAG. What am I doing wrong?

I’m using:  
Digi ESP for NET+OS  
Version: 1.4.0  
Build id: 03132009 NET+OS 7.4.2

---

<div class="post-metadata">

### Author: ![burl](https://avatars.discourse-cdn.com/v4/letter/b/47e85d/32.png) [@burl](https://forums.digi.com/u/burl)
#### Post date: [March 26, 2010, 9:58pm UTC](https://forums.digi.com/t/cant-get-rom-bin-to-boot/4915/2 "2010-03-26T21:58:56Z")

</div>

I’m also having a problem with image.bin:

```auto

Checksum passed, writing to flash...
_NAAppOffsetInFlash or _NABackupRecoveryOffsetInFlash in the linker customizatiom file is set incorrectly.  
The application image must start on a sector boundary.
Failed to write flash [-8]

```

Here’s my flash memory map:

Total Flash Size: 4096K  
Bootloader: 64K  
Application Image: 832K  
Backup Image: Disabled  
Unused Space: Disabled  
File System: 3072K  
NVRAM: 128K

---

<div class="post-metadata">

### Author: ![LeonidM](https://avatars.discourse-cdn.com/v4/letter/l/d26b3c/32.png) [@LeonidM](https://forums.digi.com/u/LeonidM)
#### Post date: [March 27, 2010, 11:29am UTC](https://forums.digi.com/t/cant-get-rom-bin-to-boot/4915/3 "2010-03-27T11:29:38Z")

</div>

check rom.bin properties and make sure it is under 64k, otherwise it will corrupt top of the rom.bin

---

<div class="post-metadata">

### Author: ![charliek](https://avatars.discourse-cdn.com/v4/letter/c/94ad74/32.png) [@charliek](https://forums.digi.com/u/charliek)
#### Post date: [April 1, 2010, 8:49pm UTC](https://forums.digi.com/t/cant-get-rom-bin-to-boot/4915/4 "2010-04-01T20:49:42Z")

</div>

Also your offset for your application (see bootldr.dat) needs to be a multiple of 0x10000 (64k), you can’t start writing an image.bin in the middle of a sector of flash.

---

<div class="post-metadata">

### Author: ![michael1](https://avatars.discourse-cdn.com/v4/letter/m/eada6e/32.png) [@michael1](https://forums.digi.com/u/michael1)
#### Post date: [April 2, 2010, 6:25am UTC](https://forums.digi.com/t/cant-get-rom-bin-to-boot/4915/5 "2010-04-02T06:25:56Z")

</div>

In recent BSP updates digi added a new feature  
" … Now use the WAKE UP button for forced recovery …" i.e. TFTP

This is triggered by the SW\_CONG dip switch on the development board

See customizeBootloader.c in platform folder