Apalis T30 does not accept software

hi,
I have a problem. I suspect that the MBR may have flooded because I am not getting up with the firmware on Apalis. Although I am not completely sure, these are my suspicions (I am connecting with RS232)…

U-Boot SPL 2015.04-00002-g02fbc1a-dirty (Sep 20 2016 - 08:08:30)

U-Boot 2015.04-00002-g02fbc1a-dirty (Sep 20 2016 - 08:08:30)

TEGRA30

DRAM: 1 GiB

MMC: Tegra SD/MMC: 0, Tegra SD/MMC: 1, Tegra SD/MMC: 2

tegra-pcie: PCI regions:

tegra-pcie: I/O: 0x2000000-0x2010000

tegra-pcie: non-prefetchable memory: 0x20000000-0x30000000

tegra-pcie: prefetchable memory: 0x30000000-0x40000000

tegra-pcie: 4x1, 1x2 configuration

tegra-pcie: probing port 2, using 1 lanes

tegra-pcie: link 2 down, retrying

tegra-pcie: link 2 down, retrying

tegra-pcie: link 2 down, retrying

tegra-pcie: link 2 down, ignoring

In: serial

Out: lcd

Err: lcd

Model: Toradex Apalis T30 1GB IT V1.1B, Serial# 06314862

USB recovery mode, disabled autoboot

Net: No ethernet found.

Apalis T30 #

You mean you are getting that output upon power-up? As it clearly states that it is in USB recovery mode where it’s just the autoboot that is disabled. You may also not be running a stable BSP release. You may use the Toradex Easy Installer or follow the legacy update procedure to (re-)install the BSP.

https://drive.google.com/open?id=1fzNboIWACh-guhIjeSth8mSybUJh3tzB will I help this movie?

Unfortunately, screenshots and videos mostly do not really help much as they say nothing about any of the environment (e.g. what cabling, power supply, SD card or USB media and so forth are connected), what exactly was done prior to whatever behaviour is shown (e.g. did it stop booting before) nor what exactly somebody is trying to achieve.
As you still seem to be using that older version. Could you please try updating using a supported version?
As you seem to create a valid config block, does it still report Missing Toradex config block after a power-cycle?
The same could be tried by writing the environment using saveenv. Does it still report Warning - bad CRC, using default environment after a power-cycle?
Rather than doing a full update you may also try just doing run update_uboot.
Assuming it does still not boot after a power-cycle could you assess whether or not it enters the USB recovery mode upon power-cycle?
As you seem to use a customised update media could you maybe try generating another one from one of our stock images or even better could you try whether the Toradex Easy Installer could successfully install an image?
The Toradex Easy Installer also features a dedicated Erase Flash (c) button. Maybe that could help in clearing this condition.
The textual output of the following U-Boot commands may also be helpful:

Apalis T30 # mmc dev 0
switch to partitions #0, OK
mmc0(part 0) is current device
Apalis T30 # mmc info
Device: Tegra SD/MMC
Manufacturer ID: 11
OEM: 100
Name: 008G7 
Tran Speed: 52000000
Rd Block Len: 512
MMC version 5.0
High Capacity: Yes
Capacity: 7.3 GiB
Bus Width: 8-bit
Erase Group Size: 512 KiB
HC WP Group Size: 4 MiB
User Capacity: 7.3 GiB WRREL
Boot Capacity: 4 MiB ENH
RPMB Capacity: 4 MiB ENH
Apalis T30 # ls mmc 0:1
  4246760   zimage 

1 file(s), 0 dir(s)

Apalis T30 # ls mmc 0:2
<DIR>       4096 .
<DIR>       4096 ..
<DIR>      16384 lost+found
<DIR>       4096 var
<DIR>       4096 run
<DIR>       4096 usr
<DIR>       4096 lib
<DIR>       4096 etc
<DIR>       4096 sbin
<DIR>       4096 boot
<DIR>       4096 dev
<DIR>       4096 bin
<DIR>       4096 mnt
<DIR>       4096 proc
<DIR>       4096 home
<DIR>       4096 sys
<DIR>       4096 media
<DIR>       4096 tmp
Apalis T30 #

The problem is that with 10pcs one after changing the file MBR did not get up which is surprised, because on the second SD card I have a target firmware which I use at work and there it is on other apa1a works. I wanted to make two SD cards, because I need to install your generated card first, then install our firmware. It’s just that now no one’s up.

Apalis T30 # mmc dev 0
switch to partitions #0, OK
mmc0(part 0) is current device
Apalis T30 # mmc info
Device: Tegra SD/MMC
Manufacturer ID: 13
OEM: 14e
Name: Q2J54 
Tran Speed: 52000000
Rd Block Len: 512
MMC version 5.0
High Capacity: Yes
Capacity: 3.6 GiB
Bus Width: 8-bit
Erase Group Size: 512 KiB
HC WP Group Size: 8 MiB
User Capacity: 3.6 GiB WRREL
Boot Capacity: 16 MiB ENH
RPMB Capacity: 512 KiB ENH
Apalis T30 # ls mmc 0:1
  4243840   uimage 

1 file(s), 0 dir(s)
Apalis T30 # ls mmc 0:2
<DIR>       4096 .
<DIR>       4096 ..
<DIR>      16384 lost+found
<DIR>       4096 bin
<DIR>       4096 boot
<DIR>       4096 dev
<DIR>       4096 etc
<DIR>       4096 home
<DIR>       4096 lib
<DIR>       4096 media
<DIR>       4096 mnt
<DIR>       4096 proc
<DIR>       4096 run
<DIR>       4096 sbin
<DIR>       4096 sys
<DIR>       4096 tmp
<DIR>       4096 usr
<DIR>       4096 var
Apalis T30 # run setupdate
MMC: no card present
** Bad device mmc 1 **
reading flash_blk.img
710 bytes read in 13 ms (52.7 KiB/s)
## Executing script at 81000000
reading apalis_t30/flash_blk.img
5080 bytes read in 21 ms (235.4 KiB/s)
## Executing script at 80408000
enter "run update" to update the entire module
Apalis T30 # run update_uboot
reading apalis_t30/apalis_t30.img
569344 bytes read in 51 ms (10.6 MiB/s)
switch to partitions #1, OK
mmc0(part 1) is current device

MMC write: dev # 0, block # 0, count 1112 ... 1112 blocks written: OK
Apalis T30 # 

I also did a previous cleaning of this page

https://developer.toradex.com/knowledge-base/how-to-erase-emmc-flash-memory

and I think I made a mistake here

Apalis TK1 # mmc read ${loadaddr} 0x7fffffff 1

MMC read: dev # 0, block # 2147483647, count 1 ... MMC: block number 0x80000000 exceeds max(0xe90000)
0 blocks read: ERROR
Apalis TK1 # mmc erase 0 0xe90000

MMC erase: dev # 0, block # 0, count 15269888 ... 15269888 blocks erased: OK

I’m using an example after generating my code
0xe90000
I have mistaken the letter.

config block does not lose. cables and everything else is rather ok, because, as I wrote above, I flowed 9 out of 10 tiles and generally on this programmer we program all the tiles.

I really can’t find anything wrong by looking at your U-Boot output. Even the Linux kernel and its root file system seem to be properly written (you may test booting them by entering run emmcboot). So if it still does not boot upon power-cycle I suspect something wrong with either the flashing/programming of U-Boot or it is due to some misconfiguration. Another thought was that the USB recovery mode may just always be asserted. What exact carrier board are you using?