Data calibration method and driver

Abstract

The present invention discloses a data calibration method and a driver. The data calibration method is applied to an NFC reader and includes: when the driver is powered on, writing data into an NFC tag; updating the state of the NFC tag to a first state; checking the state of the NFC tag until the state is a third state; reading feedback from the NFC tag; processing the feedback; and updating the state of the NFC tag to a fourth state.

Description

Technical Field

[0001] Embodiments of the present disclosure relate generally to the field of drives, and more particularly to data calibration methods and drives. Background Art

[0002] This section introduces aspects that may be helpful for a better understanding of the present disclosure. Therefore, the statements in this section should be read from this perspective and should not be understood as an admission that the content in the relevant field is or is not the content in the relevant field.

[0003] In the field of data calibration, one solution is to write data to a transmission buffer (TB) during power-off, and the data will only take effect after power-on, so multiple power-off / power-on may be required during calibration. Figure 1 The operation process of this solution is shown. Figure 2 Another solution is shown in the Figure 2 In the present invention, a factory test mode (FTM) is used, in which the operation is more complicated and much memory size is required to implement the solution. Summary of the invention

[0004] The inventors of the present disclosure have found that in the related art, calibration data can be written to a near field communication (NFC) tag offline, and the data will only take effect after a power cycle. However, if multiple parameters are to be calibrated, multiple power cycles may be required. On the other hand, calibration data can be written to an NFC tag when the drive is powered off, and the data will only take effect after the next power cycle. Therefore, if multiple parameters are to be calibrated, multiple power cycles may be required.

[0005] Generally, embodiments of the present disclosure provide a data calibration method and a driver. In an embodiment, calibration data can be written to an NFC tag at any time when the driver is powered on, the data takes effect immediately after calibration, and the driver does not need to be powered on for the data to take effect.

[0006] In a first aspect, a data calibration method applied to an NFC reader is provided, the data calibration method comprising:

[0007] When the driver is powered on, data is written to the NFC tag;

[0008] Updating the state of the NFC tag to a first state;

[0009] Checking the state of the NFC tag until the state is a third state;

[0010] Read feedback from NFC tags;

[0011] Processing feedback; and

[0012] The state of the NFC tag is updated to the fourth state.

[0013] In another embodiment, the NFC reader is an NFC application configured in the electronic device.

[0014] In another embodiment, the state of the NFC tag is one of:

[0015] The first state is ready.

[0016] The third status is either completed or error, and

[0017] The fourth state is idle.

[0018] In another embodiment, the NFC tag is configured in the driver, and the transmission buffer of the NFC tag includes three fields, which are a status field, a data field, and a CRC field.

[0019] In another embodiment, the data calibration method further comprises:

[0020] After processing the feedback, the processing result is notified.

[0021] In a second aspect, a data calibration method applied to a driver is provided, the driver comprising an NFC tag and a processor, the data calibration method comprising:

[0022] Checking a state of the NFC tag until the state is a first state;

[0023] Updating the state of the NFC tag to a second state;

[0024] Read data from NFC tags;

[0025] Process data;

[0026] Writing feedback to the NFC tag; and

[0027] The state of the NFC tag is updated to a third state.

[0028] In another embodiment, the state of the NFC tag is one of:

[0029] The first state is ready.

[0030] The second state is busy, and

[0031] The third status is completed or error.

[0032] In another embodiment, the transmission buffer of the NFC tag includes three fields, which are a status field, a data field, and a CRC field.

[0033] In a third aspect, an electronic device is provided, the electronic device comprising:

[0034] a memory configured to store an NFC program, and

[0035] a processor coupled to the memory and configured to execute an NFC program to:

[0036] When the driver is powered on, data is written to the NFC tag;

[0037] Updating the state of the NFC tag to a first state;

[0038] Checking the state of the NFC tag until the state is a third state;

[0039] Read feedback from NFC tags;

[0040] Processing feedback; and

[0041] The state of the NFC tag is updated to a fourth state.

[0042] In a fourth aspect, a driver is provided, the driver comprising:

[0043] NFC tags,

[0044] a memory configured to store a plurality of instructions; and

[0045] A processor coupled to the memory and configured to execute a plurality of instructions to:

[0046] Checking a state of the NFC tag until the state is a first state;

[0047] Updating the state of the NFC tag to a second state;

[0048] Read data from NFC tags;

[0049] Process data;

[0050] Writing feedback to the NFC tag; and

[0051] The state of the NFC tag is updated to a third state.

[0052] According to at least one embodiment of the various embodiments of the present disclosure, it is not necessary to power cycle the driver, and if more parameters are to be calibrated, especially for those parameters that need to be calibrated step by step, it can be much faster. Therefore, production efficiency is improved.

[0053] According to at least one embodiment of the various embodiments of the present disclosure, the command is simpler than before, the operation is easier, and there is no need to repeatedly power on / off. When the present disclosure is used to calibrate the current for production, the calibration time during production is saved and the production efficiency is improved. In addition, compared with FTM, the code size is reduced and the memory size is saved. And the present disclosure is easy to implement for software. BRIEF DESCRIPTION OF THE DRAWINGS

[0054] By way of example, the above and other aspects, features and benefits of various embodiments of the present disclosure will become more apparent through the following detailed description with reference to the accompanying drawings, in which like reference numerals or letters are used to represent similar or equivalent elements. The accompanying drawings are shown to facilitate a better understanding of the embodiments of the present disclosure and are not necessarily drawn to scale, wherein:

[0055] Figure 1 A schematic diagram of a solution for a data calibration process in the related art;

[0056] Figure 2 A schematic diagram of another solution for the data calibration process in the related art;

[0057] Figure 3 A schematic diagram of the data calibration process disclosed in the present invention;

[0058] Figure 4 A flow chart of the data calibration process disclosed herein;

[0059] Figure 5 A schematic diagram of the data calibration method disclosed in the present invention;

[0060] Figure 6 A schematic diagram of the transmission buffer of an NFC tag;

[0061] Figure 7 is a schematic diagram of another data calibration method disclosed in the present invention;

[0062] Figure 8 This is a schematic diagram of information exchange between the NFC reader and the MCU;

[0063] Fig. 9 A flowchart of the process for an NFC reader;

[0064] Fig.10 It is a flowchart of the process of MCU;

[0065] Fig.11 is a functional block diagram of a device configured with an NFC reader;

[0066] Fig.12 The figure is a functional block diagram of a driver configured with an MCU and an NFC tag. DETAILED DESCRIPTION

[0067] The present disclosure will now be discussed with reference to several exemplary embodiments. It should be understood that the purpose of discussing these embodiments is only to enable those skilled in the art to better understand the present disclosure and thus implement the present disclosure, rather than to propose any limitation on the scope of the present disclosure.

[0068] As used herein, the terms "first" and "second" refer to different elements. Unless the context clearly indicates otherwise, the singular forms "one" and "a kind of" are intended to also include plural forms. As used herein, the terms "include", "comprise", "have" and / or "contain" specify the presence of the features, elements and / or components, etc., but do not exclude the presence or addition of one or more other features, elements, components and / or combinations thereof. The term "based on" should be understood as "based at least in part". The terms "one embodiment" and "embodiment" should be understood as "at least one embodiment". The term "another embodiment" should be understood as "at least one other embodiment". Other explicit and implicit definitions may be included below.

[0069] First aspect of the implementation plan

[0070] In a first aspect of the embodiment, a data calibration method is provided.

[0071] Figure 3 is a schematic diagram of the data calibration process disclosed in the present invention, Figure 4 FIG. 1 is a flow chart of the data calibration process disclosed in the present invention. Figure 3 and Figure 4 As shown, when the driver is powered on, initial processing is performed, and in production mode, calibration data can be written to the NFC tag for calibration, so the calibration current changes immediately and there is no need to power on / off the driver for calibration.

[0072] Figure 5 A schematic diagram of a data calibration method according to an embodiment of the present disclosure.

[0073] In this embodiment, the data calibration method is applied to the NFC reader, and the NFC reader may be a single device or may be an NFC application (program) stored in a memory of an electronic device, but the embodiment is not limited thereto.

[0074] like Figure 5 As shown, the data calibration method includes:

[0075] 501: When the driver including the NFC tag is powered on, the NFC reader writes data to the NFC tag;

[0076] 502: The NFC reader updates the state of the NFC tag to a first state;

[0077] 503: The NFC reader checks the state of the NFC tag until the state is a third state;

[0078] 504: The NFC reader reads feedback from the NFC tag;

[0079] 505: NFC reader processes feedback; and

[0080] 506: The NFC reader updates the state of the NFC tag to the fourth state.

[0081] According to an embodiment of the present disclosure, an operator can write calibration data to an NFC tag at any time when the drive is powered on. The drive's microcontroller unit (MCU) can immediately check the current change in real time, so no power cycle is required to make it effective.

[0082] In one embodiment, the NFC tag is configured in a driver, and a transmission buffer of the NFC tag includes three fields, namely a status field, a data field, and a cyclic redundancy check (CRC) field, wherein the status field occupies one or more bytes to indicate a communication status of the NFC tag. Figure 6 FIG. 1 is a schematic diagram of a transmission buffer of an NFC tag, showing three fields of the NFC tag, but the embodiment is not limited thereto. The transmission buffer of the NFC tag may include more fields, or may only include a status field and a data field, that is, the CRC field is optional. Figure 6 As shown, CRC is used to check whether the data in the NFC tag is correct by using the CRC checksum, which can reduce radio frequency (RF) interference during transmission.

[0083] In one embodiment, the state of the NFC tag preferably has no less than 5 states, namely, idle, busy, ready, completed and error.

[0084] In one embodiment, the "ready state" means that the NFC tag is ready for some read / write events. When the state of the NFC tag is ready, the MCU can update the state to the second state and read data from the NFC tag. In this embodiment, the ready state is referred to as the first state, however, the embodiment is not limited thereto, and the ready state can also be replaced by other names.

[0085] In one embodiment, "busy state" means that the NFC tag is performing some read / write events. In this embodiment, the busy state is referred to as the second state, but the embodiment is not limited thereto, and the busy state may also be replaced by other names.

[0086] In one embodiment, the "completed state" means that the NFC tag has completed data processing and the result is correct. The "error state" means that the NFC tag has completed data processing, but the result is incorrect. In this embodiment, the completed state or the error state is referred to as the third state, however, the embodiment is not limited thereto, and the completed state or the error state may also be replaced by other names.

[0087] In one embodiment, "idle state" means that the NFC tag is starting and waiting for a save event. In the idle state, the calibration process is completed, the current is immediately effective, and the process enters a normal working mode.

[0088] In operation 501, at the beginning of the calibration process, when the driver is powered on, the NFC reader writes data to the NFC tag. The data can be various parameters related to the calibration, so only one step is required, and when more parameters are to be calibrated, the calibration speed is accelerated, and the production efficiency is improved.

[0089] In operation 502 , after writing data to the NFC tag, the NFC reader updates the state of the NFC tag to a first state, such as a ready state, so that the MCU can read data from the NFC tag.

[0090] In operation 503, the NFC reader keeps checking the state of the NFC tag until the state is the third state, which is a completion state or an error state, so the NFC reader can perform subsequent processing. In operation 503, in one embodiment, the NFC reader reads the status byte in the NFC tag and determines whether the state is completion or error. When the judgment is "yes", the NFC reader considers that the state of the NFC tag is the third state, and the process goes to operation 504; and when the judgment is "no", the NFC reader considers that the state of the NFC tag is not the third state, and continues to read the status byte in the NFC tag, and determines the state of the NFC tag.

[0091] In operations 504 and 505, when the status of the NFC tag is completed or error, the NFC reads feedback from the NFC tag and processes the feedback. The feedback is in the data field of the NFC tag and is written by the MCU of the driver.

[0092] In operation 505 , since the status of the NFC tag is completion or error, the feedback corresponding to different statuses is different, and the NFC reader processes the feedback corresponding to different statuses. The specific processing method is not limited in the present disclosure and is omitted here.

[0093] In operation 506 , after or before the NFC reader processes the feedback, the NFC reader updates the state of the NFC tag to a fourth state, ie, an idle state, and thus the calibration process is completed this time.

[0094] In one embodiment, the NFC reader may also notify the processing entity of the processing result after processing the feedback, which is not limited in the present disclosure.

[0095] In the embodiments of the present application, Figure 5 The execution order of the operations of the method is not limited. For example, the execution order of operations 501 and 502 can be interchanged, and Figure 5 Some operations may be added or some operations may be reduced, depending on the specific implementation.

[0096] Figure 7 It is a schematic diagram of a data calibration method according to another embodiment of the present disclosure.

[0097] In this embodiment, the data calibration method is applied to the MCU of the driver, and the driver also includes the above-mentioned NFC tag, which can be a chip connected to the MCU or a memory coupled to the MCU, and the embodiment is not limited thereto. In this embodiment, the above description of the NFC tag is incorporated herein, which is omitted herein. In this embodiment, the driver can be used for power supply for production, and the embodiment is not limited thereto.

[0098] like Figure 7 As shown, the data calibration method includes:

[0099] 701: MCU checks the state of the tag until the state is the first state;

[0100] 702: The MCU updates the state of the NFC tag to the second state;

[0101] 703: MCU reads data from the NFC tag;

[0102] 704: MCU processes data;

[0103] 705: MCU writes the feedback to the NFC tag; and

[0104] 706: The MCU updates the state of the NFC tag to the third state.

[0105] According to an embodiment of the present disclosure, an operator can write calibration data to an NFC tag at any time when the drive is powered on. The drive's microcontroller unit (MCU) can immediately check the current change in real time, so no power cycle is required to make it effective.

[0106] In operation 701, the MCU keeps checking the state of the NFC tag, and when the state of the NFC tag is the first state (i.e., the ready state), the process goes to operation 702. In operation 701, similar to operation 503, the MCU can read the state byte in the NFC tag and determine whether the state is ready, and when the judgment is "yes", the MCU considers that the state of the NFC tag is the first state, and the process goes to operation 702; and when the judgment is "no", the MCU considers that the state of the NFC tag is not the first state, and continues to read the state byte in the NFC tag, and determines the state of the NFC tag.

[0107] In operations 702 and 703, when the state of the NFC tag is the first state, the MCU considers that the calibration process is ready, the MCU updates the state of the NFC tag to the second state, that is, the busy state, and starts reading data from the NFC tag. The data is stored in the data field of the transmission buffer of the NFC tag, which has been described above and is omitted here.

[0108] In operations 704 and 705 , the MCU processes the data and writes feedback to the NFC tag based on the processing result, and the specific processing method is not limited in the present disclosure, which is omitted here.

[0109] In operation 706 , the MCU updates the state of the NFC tag to a third state, such as a completion state or an error state, which depends on the processing result and is omitted here.

[0110] In the embodiments of the present application, Figure 7 The execution order of the operations of the method is not limited. For example, the execution order of operations 705 and 706 can be interchanged, and Figure 7 Some operations may be added or some operations may be reduced, depending on the specific implementation.

[0111] In order to make the method of the embodiment of the present disclosure more clear and understandable, the following will be described with respect to Figure 8 , Fig. 9 and Fig.10 The method of the embodiment of the present disclosure is described. In the following description, as an example, the first state is a ready state, the second state is a busy state, the third state is a completion or error state, and the fourth state is an idle state.

[0112] Figure 8 This is a schematic diagram of information exchange between the NFC reader and the MCU. Fig. 9 A flowchart of the process for an NFC reader, and Fig.10 Flowchart of the process for the MCU.

[0113] like Figure 8 , Fig. 9 and Fig.10 As shown, the NFC reader writes data to the NFC tag (901) and updates the status byte in the NFC tag to ready (902). The MCU reads the status byte in the NFC tag (1001) and checks whether the status is ready (1002). When the MCU determines that it is "yes", the MCU updates the status byte in the NFC tag to busy (1003), reads data from the NFC tag (1004), processes the data (1005), and writes feedback to the NFC tag (1006). The NFC reader reads the status byte in the NFC tag (903) and checks whether the status is completed or error (904). When the NFC reader determines that it is "yes", the NFC reader reads the feedback from the NFC tag (905), processes the feedback (906) and updates the status byte in the NFC tag to idle (907).

[0114] According to at least one embodiment of the various embodiments of the present disclosure, it is not necessary to power cycle the driver, and if more parameters are to be calibrated, especially for those parameters that need to be calibrated step by step, it can be much faster. Therefore, production efficiency is improved.

[0115] According to at least one embodiment of the various embodiments of the present disclosure, the command is simpler than before, the operation is easier, and there is no need to repeatedly power on / off. When the present disclosure is used to calibrate the current for production, the calibration time during production is saved and the production efficiency is improved. In addition, compared with FTM, the code size is reduced and the memory size is saved. And the present disclosure is easy to implement for software.

[0116] Second aspect of the implementation plan

[0117] In a second aspect of the embodiment, an electronic device is provided. The electronic device may be a mobile phone, a tablet computer, a portable digital camera, a media player, a portable game device, a PDA, a computer, etc., but the embodiment is not limited thereto.

[0118] Fig.11 is a functional block diagram of an electronic device, such as Fig.11 As shown, the electronic device 1100 includes a memory 1101 and a processor 1102, the memory 1101 stores an NFC program, and the processor 1102 is coupled to the memory and configured to execute the NFC program to:

[0119] When the driver is powered on, data is written to the NFC tag;

[0120] Updating the state of the NFC tag to a first state;

[0121] Checking the state of the NFC tag until the state is a third state;

[0122] Read feedback from NFC tags;

[0123] Process feedback; and

[0124] The state of the NFC tag is updated to a fourth state.

[0125] In this embodiment, the above processing of processor 1102 is Figure 5 Same process as the NFC reader in Figure 5 The above description is incorporated in this embodiment, which is omitted here.

[0126] like Fig.11 As shown, the electronic device 1100 may further include a communication module (communication interface) 1103, a camera 1104, an input unit 1105, a display 1106, and a power supply 1107, which are connected to the processor 1102 and run under the control of the processor 1102. The communication module 1103 can be used as a receiver for receiving data from an external device such as a drive, or the communication module 1103 can be used as a transmitter for sending data to an external device. The camera 1104 can be any type of camera. The input unit 1105 can be a keyboard or a mouse, etc.

[0127] It should be noted that Fig.11 Only a portion of the structure of the electronic device 1100 may be shown. The electronic device 1100 does not necessarily include Fig.11 In addition, the electronic device 1100 may include Fig.11 Components not shown in the figure, and reference can be made to the relevant art. It should be noted that the figure is only illustrative, and other types of structures can also be used to supplement or replace the present structure and realize telecommunication functions or other functions.

[0128] As can be seen from the above embodiments, the operator can write calibration data to the NFC tag at any time when the drive is powered on. The drive's microcontroller unit (MCU) can immediately check the current change in real time, so no power cycle is required for it to take effect.

[0129] The third aspect of the implementation plan

[0130] In a third aspect of the embodiment, a driver is provided.

[0131] Fig.12 is the functional block diagram of the driver, such as Fig.11 As shown, the driver 1200 includes an NFC tag 1201, a memory 1202, and a processor 1203, wherein the memory 1202 stores a plurality of instructions and serves as an information storage device, and the processor 1203 is coupled to the memory 1202, serves as a control unit, and is configured to execute a plurality of instructions to:

[0132] Checking the state of the NFC tag 1201 until the state is a first state;

[0133] Update the state of the NFC tag 1201 to a second state;

[0134] Read data from NFC tag 1201;

[0135] Process data;

[0136] Writing feedback to the NFC tag 1201; and

[0137] The state of the NFC tag 1201 is updated to the third state.

[0138] In this embodiment, the above processing of processor 1203 is Figure 7 The processing of the MCU in the Figure 7 The above description is incorporated in this embodiment, which is omitted here.

[0139] like Fig.12 As shown, in some embodiments, the driver 1200 further includes a driving circuit 1204, which is controlled by the control unit 1203 to debug an external device, such as a lighting system (LED). In order to control the driving circuit 1204, the information storage device 1202 is used to store configuration information.

[0140] like Fig.12 As shown, in some embodiments, the driver 1200 also includes an electronic interface (such as a communication interface) 1205 that is configured to retrieve configuration information from a configuration device.

[0141] In some embodiments, such as Fig.12 As shown, the electronic interface 1205 includes a wireless communication interface 12051, which is used to receive configuration information sent from a configuration device. The wireless communication interface 12051 may include a storage unit, such as an EEPROM or a flash memory, to store the received configuration information.

[0142] In some embodiments, such as Fig.12 As shown, the electronic interface 1205 includes a wired communication channel 12052, which can be a wired communication channel 12052. 2 The wired communication channel 12052 is used to provide the received configuration information to the information storage device 1202 of the driver 1200.

[0143] In some embodiments, the wired communication channel 12052 is preferably used to provide the received configuration information to the control unit 1203 of the driver 1200 in the operation mode of the driver 1200. Preferably, when the driver 1200 is powered on, the electronic interface 1205 can read out the configuration information stored in the storage unit of the wireless communication interface 12051 through the wired communication channel 12052.

[0144] It should be noted that Fig.12 Only a portion of the structure of the driver 1200 may be shown. The driver 1200 does not necessarily include Fig.12 All components shown. And in addition, the driver 1200 may include Fig.12 Components not shown in the figure, and reference can be made to the relevant art. It should be noted that the figure is only illustrative, and other types of structures can also be used to supplement or replace the present structure and realize telecommunication functions or other functions.

[0145] In some embodiments, the driver 1200 is an LED driver and the calibration data is a nominal LED current (programming of the nominal LED (= output) current magnitude at 100% operation) of the driver 1200. In these embodiments, after calibration, the driver 1200 can be used to program the nominal LED current of the driver 1200.

[0146] Such programming of the nominal LED current may be done during production of the driver 1200, but may also be done during assembly of the driver 1200 into a luminaire (LED) or after the luminaire (LED) is installed. For example, this function may be performed by an operator with the necessary access rights.

[0147] As can be seen from the above embodiments, the operator can write calibration data to the NFC tag at any time when the drive is powered on. The drive's microcontroller unit (MCU) can immediately check the current change in real time, so no power cycle is required for it to take effect.

[0148] In addition, although the operations are shown in a specific order, this situation should not be understood as requiring such operations to be performed in the specific order shown or in a sequential order or requiring all the operations shown to be performed to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although some specific implementation details are included in the above discussion, these specific implementation details should not be understood as limitations on the scope of the present disclosure, but should be understood as descriptions of features that may be specific to a specific embodiment. Certain feature parts described in the context of a separate embodiment may also be implemented in combination in a single embodiment. On the contrary, the various feature parts described in the context of a single embodiment may also be implemented in multiple embodiments individually or in the form of any suitable sub-combination.

[0149] Although the present disclosure is described in language specific to structural features and / or method actions, it should be understood that the present disclosure defined by the appended claims is not necessarily limited to the specific features or actions described above. Instead, the specific features and actions described above are disclosed as exemplary forms of implementing the claims.

Claims

1. A data calibration method applied to an NFC reader, the data calibration method comprising: When the driver is powered on, the calibration data is written to the NFC tag; Updating the state of the NFC tag to a first state; checking a state of the NFC tag until the state is a third state; Reading feedback of calibration results from the NFC tag; processing the feedback; as well as Updating the state of the NFC tag to a fourth state; Wherein, the first state is ready, the third state is completed or error, and the fourth state is idle.

2. The data calibration method according to claim 1, wherein: The NFC reader is an NFC application configured in an electronic device.

3. The data calibration method according to claim 1, wherein: The NFC tag is configured in the driver, and a transmission buffer of the NFC tag includes three fields, which are a status field, a data field, and a CRC field.

4. The data calibration method according to claim 1, wherein: The data calibration method further comprises: After processing the feedback, a processing result is notified.

5. A data calibration method applied to a driver, the driver comprising an NFC tag and a processor, the data calibration method comprising: Checking a state of the NFC tag until the state is a first state; Updating the state of the NFC tag to a second state; reading calibration data from the NFC tag; calibrating the calibration data; Writing feedback of the calibration result into the NFC tag; as well as Updating the state of the NFC tag to a third state; The first state is ready, the second state is busy, and the third state is completed or error.

6. The data calibration method according to claim 5, wherein: The transmission buffer of the NFC tag includes three fields, which are a status field, a data field, and a CRC field.

7. An electronic device comprising: a memory configured to store an NFC program, and a processor coupled to the memory and configured to execute the NFC program to: When the driver is powered on, the calibration data is written to the NFC tag; Updating the state of the NFC tag to a first state; checking a state of the NFC tag until the state is a third state; Reading feedback of calibration results from the NFC tag; processing the feedback; as well as Updating the state of the NFC tag to a fourth state; Wherein, the first state is ready, the third state is completed or error, and the fourth state is idle.

8. A driver comprising: NFC tags, a memory configured to store a plurality of instructions; and a processor coupled to the memory and configured to execute the plurality of instructions to: Checking a state of the NFC tag until the state is a first state; Updating the state of the NFC tag to a second state; reading calibration data from the NFC tag; calibrating the calibration data; Writing feedback of the calibration result into the NFC tag; as well as Updating the state of the NFC tag to a third state; The first state is ready, the second state is busy, and the third state is completed or error.

9. The driver according to claim 8, wherein: The driver is an LED driver, and the processor is further configured to program a nominal LED current of the driver after calibration.

Images