News about ODROID eMMC Modules

Post Reply
User avatar
odroid
Site Admin
Posts: 42535
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English, Korean
ODROIDs: ODROID
Has thanked: 3733 times
Been thanked: 2102 times
Contact:

News about ODROID eMMC Modules

Post by odroid »

Today, we will tell you two news related to our eMMC modules.

This is the first news.
The price of NAND Flash components has been steadily decreasing over the past half year, and accordingly, our eMMC module prices have been significantly reduced.
Especially in the case of the 32GB model, it has been lowered by about 30%.
Screenshot from 2023-06-02 13-59-27.png
Screenshot from 2023-06-02 13-59-27.png (19.59 KiB) Viewed 44085 times


This is the second news.
We just started selling our new 256GB eMMC modules.
Although the form factor is smaller than a postage stamp, we hope you feel the peace of mind provided by the large capacity storage device.
256GBeMMCModulew.jpg
256GBeMMCModulew.jpg (48.86 KiB) Viewed 44085 times
It costs $49 and is compatible with all ODROID SBC series, including N2, C4, M1, H2, H3, and XU4.
It is available on our webstore at the link below and will soon be available from our distributors as well.
https://www.hardkernel.com/product-cate ... price-desc


The read and write speed is similar to that of the existing 64GB and 128GB products, and the iozone performance test results are as follows.
It was tested with ODROID-C4.

Code: Select all

                                                       random   random
      kB  reclen    write  rewrite     read    reread    read    write
  102400       4    35343    41892    53301    53512    29539    41368
  102400      16    82616    89965   109957   110096    45359    88753
  102400     512   139487   145019   170448   170577   156325   143786
  102400    1024   143326   147521   171274   171498   163135   143271
  102400   16384   146234   141246   172988   173438   172876   147867
Please see our wiki page for more details.
https://wiki.odroid.com/accessory/emmc/ ... n_emmc_v51
These users thanked the author odroid for the post (total 10):
xnd (Fri Jun 02, 2023 3:09 pm) • mctom (Fri Jun 02, 2023 4:25 pm) • Beat96 (Tue Jun 06, 2023 4:26 am) • meveric (Wed Jun 07, 2023 4:22 am) • xabolcs (Mon Jun 19, 2023 11:03 pm) • elatllat (Tue Jul 04, 2023 4:06 am) • secuflag (Sat Jul 22, 2023 6:27 pm) • zyssai (Fri Jul 28, 2023 10:35 pm) • Sebas_Ledesma (Mon Sep 11, 2023 11:56 pm) • domih (Sun Jun 02, 2024 9:12 am)

User avatar
rooted
Posts: 10633
Joined: Fri Dec 19, 2014 9:12 am
languages_spoken: english
Location: Gulf of Mexico, US
Has thanked: 822 times
Been thanked: 737 times
Contact:

Re: News about ODROID eMMC Modules

Post by rooted »

Good news on both fronts, lower price and a higher capacity option. Very nice.
These users thanked the author rooted for the post (total 2):
Beat96 (Tue Jun 06, 2023 4:26 am) • LudiaRemi (Mon Jun 19, 2023 1:14 pm)

RadioAD5GB
Posts: 3
Joined: Tue Apr 11, 2023 5:21 am
languages_spoken: english
ODROIDs: Just the XU4 - so far....
Has thanked: 0
Been thanked: 0
Contact:

Re: News about ODROID eMMC Modules

Post by RadioAD5GB »

Greetings,

I have a couple of questions about this device that I cannot find definitive answers to. One of them might have been answered just by visiting this forum. I've got an XU4 that I've been running ArchLinux on with a 64GB eMMC module Arch just doesn't seem to be updating anything though. Kernels are ancient. Thinking of making a switch. Wasn't sure what the eMMC capacity was on the XU4 but coming here I noticed the 256GB modules. Will it address all of that memory?

The other thing is Arch had an odd install procedure where you flash to a MicroSD card and then transferred it to the eMMC. Cumbersome time consuming and possibly error prone. Seems I've read that it's possible to flash directly to eMMC. I've soft-bricked this thing too many times; time for something more modern I think.

I've been a UNIX/Linux/Android developer as a profession for almost 24 years. No stranger to it on anything from the big iron servers to virtual machines down to embedded devices. I guess I just need to understand those things and probably some guidance when I go to buy another card. I've pulled down the 2 latest Ubuntu images. Going to try to find the kernel src here since that's the thing that's been driving me the most crazy with this thing.

Many thanks and Kind Regards!

User avatar
odroid
Site Admin
Posts: 42535
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English, Korean
ODROIDs: ODROID
Has thanked: 3733 times
Been thanked: 2102 times
Contact:

Re: News about ODROID eMMC Modules

Post by odroid »

Personally, I have not been using Arch Linux for over 7-8 years, so it is difficult to give an exact answer.

Which Kernel version have you used on your XU4?
We are supporting Kernel 6.1 at this moment even 256GB eMMC module could work with very old Kernel 4.4 certainly.
viewtopic.php?f=225&t=47204

If you post your questions in the XU4 sub-forum, other Arch Linux experts will hopefully be able to help you.

RadioAD5GB
Posts: 3
Joined: Tue Apr 11, 2023 5:21 am
languages_spoken: english
ODROIDs: Just the XU4 - so far....
Has thanked: 0
Been thanked: 0
Contact:

Re: News about ODROID eMMC Modules

Post by RadioAD5GB »

Greetings,
Thanks for your thoughts and response. The Odroid-xu4 ArchLinux image ships with 4.14.180-3 yet their other devices and server/desktop will get you pretty close to bleeding edge. I've always loved Arch but when you need functionality your current kernel can't provide reliably, what do you do. I just built your 6.1.67 this morning and SURPRISE! All of my zswap/zpool problems/anomalies have vanished. (I'll be forking the tree and committing a patch for zswap since it really makes a difference on devices with limited memory. I may, yet I already have Arch running on 6.1 and my problems vanished. The jump from 4.14 to 6.1 was remarkably noticeable, especially when stuff starts working.... LOL

Many thanks and kind regards

User avatar
domih
Posts: 809
Joined: Mon Feb 11, 2019 4:48 pm
languages_spoken: English, French
ODROIDs: UX4, HC2, N2, N2+, H2, H2+, C4, HC4, M1, M1S (with UPS, 4 x Relay) H3, H3+, H4+, H4 Ultra - 1GbE, 2.5GbE, 10GbE, 45+ GbE
Location: San Francisco Bay Area
Has thanked: 337 times
Been thanked: 245 times
Contact:

Re: News about ODROID eMMC Modules

Post by domih »

odroid wrote:
Fri Jun 02, 2023 2:24 pm
Today, we will tell you two news related to our eMMC modules.
../..
We just started selling our new 256GB eMMC modules.
Although the form factor is smaller than a postage stamp, we hope you feel the peace of mind provided by the large capacity storage device.
../..
As a matter of fact, provided a 256GB eMMC works OK, the larger the better for the longevity. As detailed there: viewtopic.php?f=171&t=45722&p=377653 computing the write amplification involves the total size of the flash memory. In addition, with eMMC you can use the mmc-utils package to get the LIFE|EOL estimate.

User avatar
domih
Posts: 809
Joined: Mon Feb 11, 2019 4:48 pm
languages_spoken: English, French
ODROIDs: UX4, HC2, N2, N2+, H2, H2+, C4, HC4, M1, M1S (with UPS, 4 x Relay) H3, H3+, H4+, H4 Ultra - 1GbE, 2.5GbE, 10GbE, 45+ GbE
Location: San Francisco Bay Area
Has thanked: 337 times
Been thanked: 245 times
Contact:

Re: News about ODROID eMMC Modules

Post by domih »

domih wrote:
Sun Jun 02, 2024 9:34 am
odroid wrote:
Fri Jun 02, 2023 2:24 pm
Today, we will tell you two news related to our eMMC modules.
../..
We just started selling our new 256GB eMMC modules.
Although the form factor is smaller than a postage stamp, we hope you feel the peace of mind provided by the large capacity storage device.
../..
As a matter of fact, provided a 256GB eMMC works OK, the larger the better for the longevity. As detailed there: viewtopic.php?f=171&t=45722&p=377653 computing the write amplification involves the total size of the flash memory. In addition, with eMMC you can use the mmc-utils package to get the LIFE|EOL estimate.
For those interested here is the information returned by the mmc tool for the 256GB Hardkernel eMMC:

Code: Select all

domih@h4ua:~$ sudo parted -l
../..
Model: MMC Y29256 (sd/mmc)
Disk /dev/mmcblk0: 251GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End    Size   File system  Name                  Flags
 1      1049kB  538MB  537MB  fat32        EFI System Partition  boot, esp
 2      538MB   250GB  250GB  ext4
../..


domih@h4ua:~$ sudo mmc extcsd read /dev/mmcblk0
=============================================
  Extended CSD rev 1.8 (MMC 5.1)
=============================================

Card Supported Command sets [S_CMD_SET: 0x01]
HPI Features [HPI_FEATURE: 0x01]: implementation based on CMD13
Background operations support [BKOPS_SUPPORT: 0x01]
Max Packet Read Cmd [MAX_PACKED_READS: 0x3c]
Max Packet Write Cmd [MAX_PACKED_WRITES: 0x20]
Data TAG support [DATA_TAG_SUPPORT: 0x01]
Data TAG Unit Size [TAG_UNIT_SIZE: 0x03]
Tag Resources Size [TAG_RES_SIZE: 0x00]
Context Management Capabilities [CONTEXT_CAPABILITIES: 0x05]
Large Unit Size [LARGE_UNIT_SIZE_M1: 0x4f]
Extended partition attribute support [EXT_SUPPORT: 0x03]
Generic CMD6 Timer [GENERIC_CMD6_TIME: 0x32]
Power off notification [POWER_OFF_LONG_TIME: 0xff]
Cache Size [CACHE_SIZE] is 1536 KiB
Background operations status [BKOPS_STATUS: 0x00]
1st Initialisation Time after programmed sector [INI_TIMEOUT_AP: 0x64]
Power class for 52MHz, DDR at 3.6V [PWR_CL_DDR_52_360: 0x00]
Power class for 52MHz, DDR at 1.95V [PWR_CL_DDR_52_195: 0x00]
Power class for 200MHz at 3.6V [PWR_CL_200_360: 0x00]
Power class for 200MHz, at 1.95V [PWR_CL_200_195: 0x00]
Minimum Performance for 8bit at 52MHz in DDR mode:
 [MIN_PERF_DDR_W_8_52: 0x00]
 [MIN_PERF_DDR_R_8_52: 0x00]
TRIM Multiplier [TRIM_MULT: 0x05]
Secure Feature support [SEC_FEATURE_SUPPORT: 0x55]
Boot Information [BOOT_INFO: 0x07]
 Device supports alternative boot method
 Device supports dual data rate during boot
 Device supports high speed timing during boot
Boot partition size [BOOT_SIZE_MULTI: 0x20]
Access size [ACC_SIZE: 0x09]
High-capacity erase unit size [HC_ERASE_GRP_SIZE: 0x01]
 i.e. 512 KiB
High-capacity erase timeout [ERASE_TIMEOUT_MULT: 0x22]
Reliable write sector count [REL_WR_SEC_C: 0x01]
High-capacity W protect group size [HC_WP_GRP_SIZE: 0x10]
 i.e. 8192 KiB
Sleep current (VCC) [S_C_VCC: 0x08]
Sleep current (VCCQ) [S_C_VCCQ: 0x08]
Sleep/awake timeout [S_A_TIMEOUT: 0x15]
Sector Count [SEC_COUNT: 0x1d298000]
 Device is block-addressed
Minimum Write Performance for 8bit:
 [MIN_PERF_W_8_52: 0x08]
 [MIN_PERF_R_8_52: 0x08]
 [MIN_PERF_W_8_26_4_52: 0x08]
 [MIN_PERF_R_8_26_4_52: 0x08]
Minimum Write Performance for 4bit:
 [MIN_PERF_W_4_26: 0x08]
 [MIN_PERF_R_4_26: 0x08]
Power classes registers:
 [PWR_CL_26_360: 0x00]
 [PWR_CL_52_360: 0x00]
 [PWR_CL_26_195: 0x00]
 [PWR_CL_52_195: 0x00]
Partition switching timing [PARTITION_SWITCH_TIME: 0xff]
Out-of-interrupt busy timing [OUT_OF_INTERRUPT_TIME: 0xff]
I/O Driver Strength [DRIVER_STRENGTH: 0x1f]
Card Type [CARD_TYPE: 0x57]
 HS200 Single Data Rate eMMC @200MHz 1.8VI/O
 HS Dual Data Rate eMMC @52MHz 1.8V or 3VI/O
 HS eMMC @52MHz - at rated device voltage(s)
 HS eMMC @26MHz - at rated device voltage(s)
CSD structure version [CSD_STRUCTURE: 0x02]
Command set [CMD_SET: 0x00]
Command set revision [CMD_SET_REV: 0x00]
Power class [POWER_CLASS: 0x00]
High-speed interface timing [HS_TIMING: 0x43]
Erased memory content [ERASED_MEM_CONT: 0x00]
Boot configuration bytes [PARTITION_CONFIG: 0x00]
 Not boot enable
 No access to boot partition
Boot config protection [BOOT_CONFIG_PROT: 0x00]
Boot bus Conditions [BOOT_BUS_CONDITIONS: 0x00]
High-density erase group definition [ERASE_GROUP_DEF: 0x01]
Boot write protection status registers [BOOT_WP_STATUS]: 0x00
Boot Area Write protection [BOOT_WP]: 0x00
 Power ro locking: possible
 Permanent ro locking: possible
 ro lock status: not locked
User area write protection register [USER_WP]: 0x80
FW configuration [FW_CONFIG]: 0x00
RPMB Size [RPMB_SIZE_MULT]: 0x20
Write reliability setting register [WR_REL_SET]: 0x1f
 user area: the device protects existing data if a power failure occurs during a write operation
 partition 1: the device protects existing data if a power failure occurs during a write operation
 partition 2: the device protects existing data if a power failure occurs during a write operation
 partition 3: the device protects existing data if a power failure occurs during a write operation
 partition 4: the device protects existing data if a power failure occurs during a write operation
Write reliability parameter register [WR_REL_PARAM]: 0x15
 Device supports writing EXT_CSD_WR_REL_SET
 Device supports the enhanced def. of reliable write
Enable background operations handshake [BKOPS_EN]: 0x00
H/W reset function [RST_N_FUNCTION]: 0x00
HPI management [HPI_MGMT]: 0x01
Partitioning Support [PARTITIONING_SUPPORT]: 0x07
 Device support partitioning feature
 Device can have enhanced tech.
Max Enhanced Area Size [MAX_ENH_SIZE_MULT]: 0x0026e2
 i.e. 81543168 KiB
Partitions attribute [PARTITIONS_ATTRIBUTE]: 0x00
Partitioning Setting [PARTITION_SETTING_COMPLETED]: 0x00
 Device partition setting NOT complete
General Purpose Partition Size
 [GP_SIZE_MULT_4]: 0x000000
 [GP_SIZE_MULT_3]: 0x000000
 [GP_SIZE_MULT_2]: 0x000000
 [GP_SIZE_MULT_1]: 0x000000
Enhanced User Data Area Size [ENH_SIZE_MULT]: 0x000000
 i.e. 0 KiB
Enhanced User Data Start Address [ENH_START_ADDR]: 0x00000000
 i.e. 0 bytes offset
Bad Block Management mode [SEC_BAD_BLK_MGMNT]: 0x00
Periodic Wake-up [PERIODIC_WAKEUP]: 0x00
Program CID/CSD in DDR mode support [PROGRAM_CID_CSD_DDR_SUPPORT]: 0x01
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[127]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[126]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[125]]: 0x20
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[124]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[123]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[122]]: 0x20
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[121]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[120]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[119]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[118]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[117]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[116]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[115]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[114]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[113]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[112]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[111]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[110]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[109]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[108]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[107]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[106]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[105]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[104]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[103]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[102]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[101]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[100]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[99]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[98]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[97]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[96]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[95]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[94]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[93]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[92]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[91]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[90]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[89]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[88]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[87]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[86]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[85]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[84]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[83]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[82]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[81]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[80]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[79]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[78]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[77]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[76]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[75]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[74]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[73]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[72]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[71]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[70]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[69]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[68]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[67]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[66]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[65]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[64]]: 0x00
Native sector size [NATIVE_SECTOR_SIZE]: 0x00
Sector size emulation [USE_NATIVE_SECTOR]: 0x00
Sector size [DATA_SECTOR_SIZE]: 0x00
1st initialization after disabling sector size emulation [INI_TIMEOUT_EMU]: 0x00
Class 6 commands control [CLASS_6_CTRL]: 0x00
Number of addressed group to be Released[DYNCAP_NEEDED]: 0x00
Exception events control [EXCEPTION_EVENTS_CTRL]: 0x0000
Exception events status[EXCEPTION_EVENTS_STATUS]: 0x0000
Extended Partitions Attribute [EXT_PARTITIONS_ATTRIBUTE]: 0x0000
Context configuration [CONTEXT_CONF[51]]: 0x00
Context configuration [CONTEXT_CONF[50]]: 0x00
Context configuration [CONTEXT_CONF[49]]: 0x00
Context configuration [CONTEXT_CONF[48]]: 0x00
Context configuration [CONTEXT_CONF[47]]: 0x00
Context configuration [CONTEXT_CONF[46]]: 0x00
Context configuration [CONTEXT_CONF[45]]: 0x00
Context configuration [CONTEXT_CONF[44]]: 0x00
Context configuration [CONTEXT_CONF[43]]: 0x00
Context configuration [CONTEXT_CONF[42]]: 0x00
Context configuration [CONTEXT_CONF[41]]: 0x00
Context configuration [CONTEXT_CONF[40]]: 0x00
Context configuration [CONTEXT_CONF[39]]: 0x00
Context configuration [CONTEXT_CONF[38]]: 0x00
Context configuration [CONTEXT_CONF[37]]: 0x00
Packed command status [PACKED_COMMAND_STATUS]: 0x00
Packed command failure index [PACKED_FAILURE_INDEX]: 0x00
Power Off Notification [POWER_OFF_NOTIFICATION]: 0x01
Control to turn the Cache ON/OFF [CACHE_CTRL]: 0x01
eMMC Firmware Version: [
eMMC Life Time Estimation A [EXT_CSD_DEVICE_LIFE_TIME_EST_TYP_A]: 0x01
eMMC Life Time Estimation B [EXT_CSD_DEVICE_LIFE_TIME_EST_TYP_B]: 0x01
eMMC Pre EOL information [EXT_CSD_PRE_EOL_INFO]: 0x01
Secure Removal Type [SECURE_REMOVAL_TYPE]: 0x39
 information is configured to be removed using a vendor defined
 Supported Secure Removal Type:
  information removed by an erase of the physical memory
  information removed using a vendor defined
Command Queue Support [CMDQ_SUPPORT]: 0x01
Command Queue Depth [CMDQ_DEPTH]: 16
Command Enabled [CMDQ_MODE_EN]: 0x00
As expected this new 256GB eMMC is in pretty good shape:

Code: Select all

eMMC Life Time Estimation A [EXT_CSD_DEVICE_LIFE_TIME_EST_TYP_A]: 0x01
eMMC Life Time Estimation B [EXT_CSD_DEVICE_LIFE_TIME_EST_TYP_B]: 0x01
eMMC Pre EOL information [EXT_CSD_PRE_EOL_INFO]: 0x01
Where 0x01 means "Normal: consumed less than 80% of the reserved blocks."

Reference: https://developer.toradex.com/software/ ... mmc-linux/

User avatar
odroid
Site Admin
Posts: 42535
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English, Korean
ODROIDs: ODROID
Has thanked: 3733 times
Been thanked: 2102 times
Contact:

Re: News about ODROID eMMC Modules

Post by odroid »

@domih,
We have another thread about the eMMC health status. ;)
viewtopic.php?f=54&t=30081

Post Reply

Return to “News”

Who is online

Users browsing this forum: No registered users and 3 guests