SPI with a LIS2DE12 Accelerometer - c

Question

I'm trying to configure and read data from a LIS2DE12 Acc using SPI Comm. The master of the SPI is an EM9304 uC. First, I'm trying to read the "WHO AM I" register, and compare with the ID provided in the datasheet of the LIS2DE12. The module does respond, but using the oscilloscope I've found out that it keeps sending it's ID through MISO at every transaction.
For example, if I write some bytes to LIS2DE12, while the MOSI is sending the byte, the MISO is sending the LIS2DE12 ID. If I try to read another register with a known value, It stills responds with the LIS2DE12 ID and does not send the register content.
I am new to SPI Comm, but I dont think that its a normal behavior.
This is the struct used to pass the bytes.
typedef struct{
struct{
uint8_t address : 6; //6bit address
uint8_t ms : 1; //If 0, keep the address unchanged, else, it increments the address in case of writing/reading multiple bytes
uint8_t mode : 1; //Read/Write
}control;
uint8_t data; //8bit data
}SPIM_Transaction_t;
Some prints of what is going on.
Clock and MOSI signals
Clock and MISO signals
In the MOSI image, the first 2 Bytes represents a write attempt.
First Byte:
00100011 byte:
0 - Write/ 0 - Dont increment address/ 100011 - 0x0F - The register address
Second Byte:
00110000 byte: 0x30 - The value I want to load in the register.
The next 2 Bytes represents an attempt to read this same register: 10100011
1 - Read 0 - Dont increment address 100011 - (0x23) - Register Address
And 8bits of zero, expecting the sensor to answer with an 8bit data.
In the Clock and MISO image, we can see that the sensor answers with 0x33 whenever there's a clock signal. Because of the symmetry it could be just a random or an error signal.
I am using the correct polarity and phase, other combinations doesnt get any result. The slave CS is grounded to be always activated.
I am using an SPI library and using this function to write bytes:
/**
* #brief Performs one or more write operations.
*
* This is a non-blocking operation, the input buffer cannot be modified until
* the transaction is complete.
*
* #note If the buffer is on the stack, you must ensure that the transaction
* completes before the function exits.
*
* #param chipSelectGpio Number of the GPIO to use for the chip select.
* #param[in] pWriteBuffer An array of data to write to the device.
* #param bytes The number of entries in the source array.
* #param[in] callbackFunction The function to call after the transaction is
* complete, the return status is passed as an argument.
* #param[in] pUserData The data to pass to the callback function.
* #param frequency Maximum clock frequency to send the transaction at or 0 to
* not change the clock frequency (previous frequency is used).
* #returns true if the transaction was scheduled, false otherwise.
*/
//lint -function( fopen(1), SPIM_WriteBytes(2) ) // arg cannot be null
bool SPIM_WriteBytes(uint8_t chipSelectGpio, const uint8_t *pWriteBuffer,
uint8_t bytes, Driver_Callback_t callbackFunction, void *pUserData,
uint32_t frequency);