• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 31 subscribers
  • Views 180 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Original question:

TMAG3001: 3D Magnetic Hall Sensor ,TMAG3001 measuring range and Resolution Confirmation.

TMAG3001: 3D Magnetic Hall Sensor ,TMAG3001 eval board scb connection

Priya Konda
Prodigy 70 points
Part Number: TMAG3001

Tool/software:

The evaluation board of tmag3001 connected to SCB, by flashing the bsl and it works fine with A2 series but A1 series. It defaults all the register values to 0x00. And the I2c address in datasheet and gui are mismatching. Can you please explain what is the issue. 

  • 0
    Prodigy 70 points

    Also summed up the above question more clearly here,

     A2 Variant (±120mT / ±240mT):

    • Works perfectly.

    • GUI auto-detects the sensor.

    • Default registers populate correctly (e.g., DEVICE_ID = 0x0008, MANUFACTURER_ID = 0x5449).

    • I²C address is auto-detected as 0x68 when ADDR is tied to GND.

    • Sensor outputs update correctly when a magnet is moved.

     A1 Variant (±40mT / ±80mT):

    • GUI does not detect the sensor.

    • All registers read as 0x0000, including DEVICE_ID and MANUFACTURER_ID.

    • I manually wrote 0x0036 to register 0x0C (I2C_ADDRESS), assuming ADDR is tied to SDA and  0x0068 to register 0x0C (I2C_ADDRESS), assuming ADDR is tied to GND

    • Even after doing this, all register values remain 0x0000, and no communication seems to happen.

    • Tried with both deferred write and immediate write, and verified correct jumper settings.

    • No visible sensor output or response when a magnet is moved near the A1 chip.

  • 0 in reply to Priya Konda
    TI__Expert 7485 points

    Hi Priya,

    Our TMAG3001 expert is out today.  I will ask her to take a look at your questions when she is back tomorrow.

    Regards,

    Mekre

  • 0 in reply to Priya Konda
    TI__Genius 13475 points

    Hi Priya,

    Thank you for your patience.

    Regarding the differences in the I2C addresses between the datasheet and the GUI, it looks like the GUI has the wrong values and will need to be updated. Apologies for any confusion caused there.

    Are you able to measure the current consumption of the A1 variant? I just want to verify that the current consumption levels are where they should be just incase the device has died for some reason. 

    I would also recommend using I2C Address 0x00 to try and communicate to the A1 variant to see if it responds at all, as 0x00 is a generic I2C address that all TMAG3001s should respond to.

    Best,

    ~Alicia

  • 0 in reply to Alicia Rosenberger
    Prodigy 70 points

     not just the i2c address, the device id and maufacturer id, all parameters are zero. I tried giving magnetic axis by keeping in deferred write, when i click write all registers it automatically brings to zero. Whenever A2 is connected the GUI automatically detects and whenever the A1 is connected i should manually go to ports and than give the port number than it detects.

  • 0 in reply to Priya Konda
    Prodigy 70 points

    Here is the gui image when A2 is connected

  • 0 in reply to Priya Konda
    TI__Genius 13475 points

    Hi Priya,

    Are you able to measure the current consumption of the A1 device?

    Best,

    ~Alicia

  • +1
    TI__Genius 13475 points

    Hi Priya,

    The easiest way to measure the current consumption of the device would be to use a multimeter connected in series with the TMAG3001. The video below shows an example of how this can be done:

    https://www.youtube.com/shorts/fvofeRNyHCA 

    While the current consumption readings with a multimeter may not be as accurate as using a specialized power meter, it will at least let you know if the device is even consuming any power. If it is not, then the device is dead which would explain why it is no longer responding to any I2C communication. 

    Best,

    ~Alicia