Problems flashing Image on Apalis T30

Hi,

I’m unable to flash Linux onto an Apalis T30 by copying files to an SD card, and running run setupdate and run update as seen on the page here:

https://developer.toradex.com/getting-started/module-1-from-the-box-to-the-shell/update-the-linux-image-ixora-carrier-board-apalis-t30?som=apalis-t30&board=ixora-carrier-board

It looks like it’s complaining about a CRC Error. Please see output from the serial console below (subsequently attached as a file).

Any ideas as to why this is happening?

hi @acheng

Welcome to the Toradex Community!

Could you provide the Software Version of your module?
Which carrier board are you using?
How did you copy the files to the SD Card?

As alternative, you can also use Toradex Easy Installer to flash Image to the Apalis T30.

Best regards,
Jaski

We’re using the Ixora carrier board.

Can you clarify what you mean by software version of my module ? U-Boot is 2015.04. If you’re referring to Linux, i loaded your 2.8 build on there. I did try update_uboot as well, but not sure if it worked.

I used the ./update.sh -o /media/{user name}/{device} as mentioned in the instructions.

Also, I setup a tftp server, but it seems to be looking for something completely different than what’s in on the tftp server (ran ./update.sh -o /srv/tftp)

I used the Easy Installer to flash the T30, but I need to modify files on the rootfs which is why I’m trying to flash the module using the instructions provided.

What’s interesting is it seems like version 2.7 flashes fine, but the latest version 2.8 doesn’t flash properly.

Thanks, - Alex

Unfortunately, your introductory console output seems rather garbled. Could you please attach it as a regular text file keeping line endings, white spacing and such intact? Thanks!

We’re using the Ixora carrier board.

And what exact hardware version of it?

Can you clarify what you mean by software version of my module ?

@jaski.tx meant what exact BSP version you have installed on the module.

U-Boot is 2015.04.

Unfortunately, that does not tell us anything. But judging from the date being Jun 28 2016 you still have ancient BSP V2.6 installed.

If you’re referring to Linux, i loaded your 2.8 build on there.

What exactly do you mean by that and which exact version of 2.8 are you referring to?

I did try update_uboot as well, but not sure if it worked.

Yes, obviously, however you tried that, it did not work.

I used the ./update.sh -o /media/{user name}/{device} as mentioned in the instructions.

The update media being an SD card or a USB stick?

Also, I setup a tftp server, but it seems to be looking for something completely different than what’s in on the tftp server (ran ./update.sh -o /srv/tftp)

And your setup followed the following article on our developer website?

https://developer.toradex.com/knowledge-base/boot-from-a-tftpnfs-server

I used the Easy Installer to flash the T30,

But how come then the module still has U-Boot from ancient BSP V2.6 installed?

but I need to modify files on the rootfs which is why I’m trying to flash the module using the instructions provided.

You meant the legacy update procedure as found as follows?

https://developer.toradex.com/software/linux/linux-software#Legacy_Image_Format

What’s interesting is it seems like version 2.7 flashes fine, but the latest version 2.8 doesn’t flash properly.

But why then your module still has an U-Boot from ancient BSP V2.6?

May I suggest you try the Toradex Easy Installer again and ask a new question should that not work as expected. Concerning your desire to modify files on the rootfs, this is of course also easily possible using the Toradex Easy Installer. You may e.g. find the following article on our developer website useful:

https://developer.toradex.com/how-to-clone-embedded-linux-on-emmc-based-toradex-modules#c-21-integrate-artefacts

Unfortunately, your introductory console output seems rather garbled. Could you please attach it as a regular text file keeping line endings, white spacing and such intact? Thanks!

Sure, please see attached file below.

link text

We’re using the Ixora carrier board.

And what exact hardware version of it?

V1.1A

Can you clarify what you mean by software version of my module ?

@jaski.tx meant what exact BSP version you have installed on the module.

U-Boot is 2015.04.

Unfortunately, that does not tell us anything. But judging from the date being Jun 28 2016 you still have ancient BSP V2.6 installed.

Where can I check to see what BSP is installed? I would agree with you that it probably has an old BSP installed, which is why it isn’t booting properly.

If you’re referring to Linux, i loaded your 2.8 build on there.

What exactly do you mean by that and which exact version of 2.8 are you referring to?
**If you look at this page https://developer.toradex.com/software/linux/linux-software#Binary_Images

under Toradex Embedded Linux Beta Releases, the version is 2.8b5**
I did try update_uboot as well, but not sure if it worked.

Yes, obviously, however you tried that, it did not work.

I used the ./update.sh -o /media/{user name}/{device} as mentioned in the instructions.

The update media being an SD card or a USB stick?

Update media is SD Card

Also, I setup a tftp server, but it seems to be looking for something completely different than what’s in on the tftp server (ran ./update.sh -o /srv/tftp)

And your setup followed the following article on our developer website?

https://developer.toradex.com/knowledge-base/boot-from-a-tftpnfs-server

**I used this one: https://developer.toradex.com/knowledge-base//knowlodge-base/flashing-linux-over-ethernet

I’ll try the link you gave me.**

I used the Easy Installer to flash the T30,

But how come then the module still has U-Boot from ancient BSP V2.6 installed?

Not sure. I installed the latest version that was in the easy installer, and we just received the evaluation board and module last week. How would I go about installing the latest BSP on it?

but I need to modify files on the rootfs which is why I’m trying to flash the module using the instructions provided.

You meant the legacy update procedure as found as follows?

https://developer.toradex.com/software/linux/linux-software#Legacy_Image_Format

What’s interesting is it seems like version 2.7 flashes fine, but the latest version 2.8 doesn’t flash properly.

Correct

But why then your module still has an U-Boot from ancient BSP V2.6?

May I suggest you try the Toradex Easy Installer again and ask a new question should that not work as expected. Concerning your desire to modify files on the rootfs, this is of course also easily possible using the Toradex Easy Installer. You may e.g. find the following article on our developer website useful:

https://developer.toradex.com/how-to-clone-embedded-linux-on-emmc-based-toradex-modules#c-21-integrate-artefacts

Sure, I’ll give this a try

Hi

Thanks for the Information you provided.

Sure, please see attached file below.

This is an old U-Boot and Bsp, you should really update to the newer Bsp.

Not sure. I installed the latest version that was in the easy installer, and we just received the evaluation board and module last week. How would I go about installing the latest BSP on it?

Could you write which version exactly did you install. For reinstalling, you can always go to the recovery mode and reinstall the newest Bsp image (2.8b5).

Sure, I’ll give this a try

Please let us know your results.

Best regards,
Jaski

So the problem with the U-Boot and BSP was that I was actually using the old one, my apologies.

I got it updated to the latest U-Boot and BSP, but when I tried flashing the 2.8b5 version of Linux with a main line Linux kernel from the directions in the link below, the board is now to be unresponsive, and it won’t boot.

https://www.toradex.com/community/questions/2387/how-to-compile-main-line-linux-kernel-for-apalis-t.html?childToView=2391#answer-2391

I tried shorting the pins on the module, as well as pin 1 and 2 on the Ixora board to try and get the module in recovery mode, but it doesn’t seem to be detected by the host computer, and there’s no output in the serial console.

Also, whenever I power cycle the board, LED1 is green, and LEDs 4 and 5 are now red.

Any ideas on how to recover the module ?

See attached log file:

link text

I tried shorting the pins on the module, as well as pin 1 and 2 on the Ixora board to try and get the module in recovery mode, but it doesn’t seem to be detected by the host computer, and there’s no output in the serial console.

How do you know that it is not detected by the host computer? Did you connect the second usb cable to your host and X9 on Ixora (X49 on Apalis Evaluation Board)? Did you launch the recovery-linux on your host from a second terminal window?

See attached log file:

The module is not bricked. This is normal when you switch between Bsp 2.7 and Bsp 2.8b5 since the file system is different between these two Bsps.

Best regards, Jaski

It’s not showing up under lsusb (as well as no changes in listed devices), and when I try and run recovery-linux it now says ./tegrarcm: could not open USB device.

Yes, I had the second usb cable connected on the X9, and when I previously ram the easy installer it would work fine.

Right now, I don’t get any HDMI output, no output over serial console, can’t run recovery-linux, LEDs 4 and 5 are both red now instead of green.

I ran both BSP 2.7 and 2.8b5, and output was normal but after following the instructions in the link in the previous post for compiling and flashing the main line kernel, I’m getting no output whatsoever.

So in this case, if it’s not bricked, then what I do need to do to get some kind of output out of the T30 ?

Even though your last console output is incomplete and does not actually show the version print judging from the mmc command usage output you were still not running any later U-Boot version.

Please note that when in USB recovery mode there won’t ever be any output on the serial connection or any of the display interfaces. The only thing that will happen is that it advertises itself as a USB recovery device on the USB device interface when connected to a PC. For this to work on Ixora you need to remove the USB host jumper and connect the USB micro to your PC and subsequently run the recovery-linux.sh script from the Toradex Easy Installer package.

So what I’m trying to say is that whenever I would used the recovery-linux script, I use to always get some kind of output over HDMI or serial console.

Regarding the U-boot version, I was using the 2018 version which was on the 2.8b5 build before it stopped working.

I’ve tried removing the jumper, shorting pins 1 and 2 on recovery pins on the Ixora board, as well as the pins on the module itself.

I am getting ZERO output whatsoever right now.

No matter what I do now, there is no output, and recovery-linux is gives me the could not open USB device error.

If I can’t get any output and the recovery-linux isn’t working no matter what recovery options I try, what should i do in this case?

So what I’m trying to say is that whenever I would used the recovery-linux script, I use to always get some kind of output over HDMI or serial console.

Yeah, but only once you run it. Then you of course do get the Toradex Easy Installer UI showing on HDMI which is where I assume you did select your image to be installed. However, judging from your reports I’m starting to doubt even that.

Regarding the U-boot version, I was using the 2018 version which was on the 2.8b5 build before it stopped working.

But there is no such 2018 version. What exactly are you talking about?

I’ve tried removing the jumper, shorting pins 1 and 2 on recovery pins on the Ixora board, as well as the pins on the module itself.

I assume you did power-cycle while shorting such pins as otherwise it won’t ever really do anything. And JP2 really does have to be removed. Otherwise, the Toradex Easy Installer won’t ever launch.

I am getting ZERO output whatsoever right now.

As mentioned before, if in recovery mode there won’t ever be any output whatsoever.

No matter what I do now, there is no output, and recovery-linux is gives me the could not open USB device error.

And you do have X9 connected properly to your PC?

If I can’t get any output and the recovery-linux isn’t working no matter what recovery options I try, what should i do in this case?

Then, it may be really broken and would need RMAing. However, the likelihood of that is almost zero compared to simple user error somewhere along the way.