add a UART port

[Madouc]

@davidc

Hiya,
Getting all the bus stuff running was not all that straightforward - especially decoding what Wavecom mean when the API is talking about op-codes and addressing in the adl_busAccess_t structure. I spent a lot of time experimenting by sending data down the bus and staring at CRO screen captures to see what actually was happening.

ciao, Dave

that sounds awfully familiar

i’m also ashamed to admit that it took me a week to find out that the CS channel is inverted…

[Madouc]

@Madouc

@blackyblack

Both I2C (@ 100kHz) and SPI (@2MHz) are working fine for me on the Q2686, OS R7.1 - R7.3.

My I2C code freezes after 10 minutes of using. The only difference is that on R7 it does not freeze the entire application - multitasking in action.

I’d love to see your I2C code to compare with. Probably wavecom’s I2C just does not work properly with clock stretching mode and the overall result depends on slave. Also I have not seen succesfull using of multiple slaves with wavecom module. Have you tried it?

problems arose indeed with clock-stretching, wrong pullup-resistor values and also with disturbences in the 3v3 pullup voltage. (is still kills the whole processor even on R7.x)

i’m currently using 2 nxp led-dimmers (on th I2C bus).

I need to correct my own statement (since i now own a logic analyser, and i’ve seen clock-stretching happen on the i2c bus)

the current firmware (7.3) no longer freezes when something fales on the i2c bus, it reboots.
and this firmware seems to support clock-stretching (propably up to a limit.)

[blackyblack]

the current firmware (7.3) no longer freezes when something fales on the i2c bus, it reboots.
and this firmware seems to support clock-stretching (propably up to a limit.)

Will try. Thank you.
But does 7.3 firmware fit Q2686H? I heard about some memory problems…

[fer.caballero]

If you are not going to use the USB port it’s a got chance to send “traces” using it

[awneil]

@fer.caballero

If you are not going to use the USB port it’s a got chance to send “traces” using it

The trouble with using the USB for traces is that it it dies whenever the unit restarts.

[fer.caballero]

I’m not sure I understand what you mean with: “USB dies”.
If you “overide” TRACE macro and use an intermediate function that sends text to the USB port when you build as “release” and uses TRACE when build as “debug” it gives you valuable information. Of course you must initialize the USB service aditionally.
The problem of using Terminal Emulator is that some times is not easy to behave manually as the equipment you want to connect to the UART1.

[Madouc]

@blackyblack

the current firmware (7.3) no longer freezes when something fales on the i2c bus, it reboots.
and this firmware seems to support clock-stretching (propably up to a limit.)

Will try. Thank you.
But does 7.3 firmware fit Q2686H? I heard about some memory problems…

from the documentation my distributor send me i understand that the newer functions (ids) will lead to memory problems on the older H models.

[awneil]

@fer.caballero

I’m not sure I understand what you mean with: “USB dies”.

When the unit restarts, its USB function restarts.
This means that the PC has to repeat the enumeration of the device.

In my experience (WMP100 + Win-XP), this doesn’t work properly unless you physically unplug and then re-plug the USB cable

[tomalex]

Hello all,

I think USB is good for debugging and it also has enough speed, one advantage is that you can send AT commands as well through USB port.

Regading the USB restart issue. If the module restarts the windows gives a new handle for the device. But in case of a hyperterminal a simple close/reopen sequence is enough for proper working. The Selima and TMT is said to be to detect if the USB device is reconnected so it will able to communicate with device without intervention. Anyway, you can easily hear the USB reconnection because ot the sound produced by windows USB connect/reconnect event.

At least this is the case with the latest USB driver and the firmware 7.3, 7.3a. I have no experince about USB with previous firmwares.

BR
tom