[SOLVED] NSA325 v2, new uBoot succesfully flashed, now can't boot any os (4 replies)

I was running Debian on my NSA325 v2 for a few days and then decided to flash the new uBoot for NSA325. I did that successfully after a few good UART boots with a serial cable. After flashing the new uboot, I wasn't able to boot any os anymore and after fiddling with it for 10 hours today, I'm starting to get frustrated. I'm pretty sure that the problem is with my environments.

printenv gives this:

arcNumber=4495
baudrate=115200
bootargs=$(bootargs_linux)
bootargs_stock=console=ttyS0,115200 mtdparts=nand_mtd:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2) root=/dev/nfs rw init=/init
bootargs_linux=console=ttyS0,115200 mtdparts=nand_mtd:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2) root=LABEL=rootfs loglevel=8
bootcmd='run bootcmd_linux
bootcmd_linux=setenv bootargs $(bootargs_linux); mw.l f1010100 0020c000; usb reset; ext2load usb 0:1 $(loadaddr) /uImage; ext2load usb 0:1 0x01100000 /uInitrd; bootm $(loadaddr) 0x01100000 
bootcmd_stock=setenv bootargs $(bootargs_stock); nand read.e $(loadaddr) $(kernel_addr) 0xA00000; bootm $(loadadr)
bootdelay=5
ethact=egiga0
ethaddr=xx:xx:xx:xx:xx:xx
filesiza=5d4c1f
mainlineLinux=yes
stderr=serial
stdin=serial
stdout=serial

I'm trying to boot Debian from USB
bootm $loadaddr 0x1100000 gives:

## Booting kernel from Legacy Image at 01100000 ...
Image Name: initramfs-3.17.0-kirkwood-tld-1
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size 6114271 Bytes = 5.8 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Wrong Image Type for bootm command
Error occured, error code = 5
ERROR: can't get kernel image!

I have two partitions on my USB-stick, one is a 100MB that is labeled boot and flagged as bootable, the other partition is labeled rootfs.