EMMC drive not showing up after copying over files

[SpinnakerDesign]

That did!

Fully functional again.

Thanks for you help!

[Panu]

I was out of office for a while. Now I bit the bullet and wrote the software.
Here's a wiper. first 5 megs are zeroed and SD card is published through USB.
Does this help?

Hi, Hannu, great job!

Could you publish the VSIDE solution also, along with the post-build steps to create the image?

-Panu

[Hannu]

Here is the project. It isn't the highest quality which I have done. The SD erase is possible to disable by commenting one #define out.

The program space is quite full. Only less than 100 bytes left.

I did the post modification of the image with external hack script on Linux. Panu probably knows how to do the same thing with cmd.exe.

Post processor script is eeprom2rl1img.sh and it requires GNU echo.

Code: Select all

#!/bin/sh
(/bin/echo -n -e "\x76\x42\x30\x74\x20\x20"&&tail -c +21 eeprom.img )>runlevel1.img

The recipe is start with
"vB0t " and put the eeprom.img from starting byte 21 to runlevel1.img file. The cut point in the eeprom.img is after the "BoOt" text and then 80 00 00 ad pattern starts.

Code: Select all

$ hexdump -C eeprom.img |head
00000000  56 4c 4e 35 00 02 05 0f  00 5a 00 01 00 01 00 02  |VLN5.....Z......|
00000010  42 6f 4f 74 80 00 00 ad  00 80 00 00 00 24 28 00  |BoOt.........$(.|
00000020  20 c0 00 00 00 24 36 13  00 24 3e 12 00 24 3e 05  | ....$6..$>..$>.|

$ hexdump -C runlevel1.img |head
00000000  76 42 30 74 20 20 80 00  00 ad 00 80 00 00 00 24  |vB0t  .........$|
00000010  28 00 20 c0 00 00 00 24  36 13 00 24 3e 12 00 24  |(. ....$6..$>..$|
00000020  3e 05 b8 14 36 15 00 24  3e 00 38 41 3e 00 b8 44  |>...6..$>.8A>..D|

Now the solution looks so simple, but finding the correct pattern took some time. If there are wishes for some features, just ask. This isn't the easiest part of programming.