Home
JAQForum Ver 24.01
Log In or Join  
Active Topics
Local Time 08:40 12 May 2025 Privacy Policy
Jump to

Notice. New forum software under development. It's going to miss a few functions and look a bit ugly for a while, but I'm working on it full time now as the old forum was too unstable. Couple days, all good. If you notice any issues, please contact me.

Forum Index : Microcontroller and PC projects : Armmite L4 battery miser, first beta

     Page 7 of 8    
Author Message
TassyJim

Guru

Joined: 07/08/2011
Location: Australia
Posts: 6220
Posted: 01:49am 01 Jan 2019
Copy link to clipboard 
Print this post

The Armites have a builtin RTC which is why RTC SETTIME does nothing
You would have to roll your own code to talk to a separate RTC

My HTU21 is running happily even with the I2C error messages.

Jim
Edited by TassyJim 2019-01-02
VK7JH
MMedit
 
palcal

Guru

Joined: 12/10/2011
Location: Australia
Posts: 1965
Posted: 02:33am 01 Jan 2019
Copy link to clipboard 
Print this post

Well that explains that, I will have a bit more of a play around.

Flashed the chip again with the code Peter just posted and now I am getting
40c and 10%. Every time I re flash I get different readings and the readings don't change with changed temperature or humidity. So I guess there is a problem with the I2C bus on this L4. E-28 here I come.Edited by palcal 2019-01-02
"It is better to be ignorant and ask a stupid question than to be plain Stupid and not ask at all"
 
TassyJim

Guru

Joined: 07/08/2011
Location: Australia
Posts: 6220
Posted: 06:24am 01 Jan 2019
Copy link to clipboard 
Print this post

  TassyJim said  
  matherp said  
Does this solve it?


In fact, I can remove all references to I2C OPEN from the program.

Jim


I blame it on the festivities.
Breaking out of a running program with I2C open leaves it open (I think)

Doing things properly works as it should.

@palcal
Try this version.
I have added the CRC. It will give values of -999 if the CRC is not correct.

  Quote   OPTION BASE 0
DIM AS INTEGER TDATA(3) '2 bytes of temp data plus CRC
 DIM AS INTEGER HDATA(3) '2 bytes of humidity data plus CRC
ON ERROR SKIP 1
I2C OPEN 400,1000
SETTICK 10000, doRead
doRead
DO
k$ = INKEY$
LOOP UNTIL k$ <>""
I2C CLOSE
END

SUB doRead
HTU21D
PRINT TIME$;" ";STR$(Temperature,4,1);"c ";STR$(RELHUMID,4,0);"% ";STR$(RFHUMID,4,0);"%"
END SUB

SUB HTU21D 'TEMPERATURE SENSOR, This is the SUB routine for talking to the HTU21
 I2C WRITE &H40,0,1,&HF3 'HTU21 addr= 40 hex, request temp = F3 hex
 PAUSE 60
I2C READ &H40,0,3,TDATA() 'reads temperature
 TEMP1!=TDATA(0)*256 + TDATA(1) 'combines both data bytes
 IF checkCRC(TEMP1!,TDATA(2)) THEN
Temperature = -999
ELSE
TEMP1! = TEMP1! AND &hFFFC ' mask off status bits
 Temperature=(175.72*(TEMP1!/65536))-46.85 'HTU21 formula for temp
 ENDIF
TEMPCOMP= (Temperature-25)*0.15 'for RH temp comp
 I2C WRITE &H40,0,1,&HF5 'request humidity
 PAUSE 30
I2C READ &H40,0,3,HDATA()
HUMIDACT!=HDATA(0)*256 + HDATA(1)
IF checkCRC(HUMIDACT!,HDATA(2)) THEN
RELHUMID= -999
ELSE
HUMIDACT! = HUMIDACT! AND &hFFFC ' mask of status bits
 RELHUMID= ((HUMIDACT!/65536)*125)-6 ' measured humidity
 RFHUMID= RELHUMID + TEMPCOMP 'Temperature compensated humidity
 ENDIF

END SUB

FUNCTION checkCRC(message_from_sensor, check_value_from_sensor)
' Give this function the 2 byte message (measurement) and the check_value byte from the HTU21D
 ' If it returns 0, then the transmission was good
 LOCAL INTEGER i, remainder, divisor
divisor = &h988000 'This is the 0x0131 polynomial shifted to farthest left of three bytes
 '
 remainder = message_from_sensor << 8 'Pad with 8 bits because we have to add in the check value
 remainder = remainder OR check_value_from_sensor ' Add on the check value
 '
 FOR i = 0 TO 15 'Operate on only 16 positions of max 24. The remaining 8 are our remainder and should be zero when we're done.
 IF (remainder AND (1 << (23 - i)) ) THEN ' Check if there is a one in the left position
 remainder = remainder XOR divisor
ENDIF
divisor = divisor >> 1 ' Rotate the divsor max 16 times so that we have 8 bits left of a remainder
 NEXT i
checkCRC = remainder
END FUNCTION


Jim
VK7JH
MMedit
 
matherp
Guru

Joined: 11/12/2012
Location: United Kingdom
Posts: 10068
Posted: 08:29am 01 Jan 2019
Copy link to clipboard 
Print this post

  Quote  Define 'solve'
I no longer get the error with I2C CLOSE but I still need the ON ERROR SKIP before opening.
I2C CLOSE doesn't seem to do anything.


Hopefully this time

2019-01-01_182552_ArmmiteL4.zip

The Armmite L4 version is the only one with built in I2C display drivers and I was testing for an I2C driver being loaded by looking for the display type being less than or equal to a specific value. Unfortunately I forgot that this test included zero which is the default value for no driver - duh........
 
palcal

Guru

Joined: 12/10/2011
Location: Australia
Posts: 1965
Posted: 07:05pm 01 Jan 2019
Copy link to clipboard 
Print this post

Flashed again with the latest and loaded your code JIM, but no go.
  Quote  > run
00:04:03 -999.0c -999% 0%


Thanks for your efforts but I2C on my L4 just won't work.
  Quote  The Armites have a builtin RTC which is why RTC SETTIME does nothing

Which pin is for the battery?Edited by palcal 2019-01-03
"It is better to be ignorant and ask a stupid question than to be plain Stupid and not ask at all"
 
matherp
Guru

Joined: 11/12/2012
Location: United Kingdom
Posts: 10068
Posted: 08:11pm 01 Jan 2019
Copy link to clipboard 
Print this post

  Quote  Thanks for your efforts but I2C on my L4 just won't work.


I assume you are using a NUCLEO-L432KC?

Please check the usual:

SDA is the pin labelled A4, SCL is A5
There are no pullups on the Nucleo - these must be supplied externally
Check the wires for continuity - so many time things don't work and I find it is the stupid test wires.

I haven't got a HTU21 but my test BMP180 works perfectly

  Quote  Which pin is for the battery?


No separate pin on the 32-pin chip
 
TassyJim

Guru

Joined: 07/08/2011
Location: Australia
Posts: 6220
Posted: 08:13pm 01 Jan 2019
Copy link to clipboard 
Print this post

The L4 32 pin chip doesn't have a separate pin for battery power. The 48 pin one does (I think)

If you are getting -999 it definitely indicates bad checksum. I run my modules without any extra pullups. I don't know what the value of the ones on the module are.
I am also running it off 3.3V

I can't think of anything else to try.

Jim
VK7JH
MMedit
 
palcal

Guru

Joined: 12/10/2011
Location: Australia
Posts: 1965
Posted: 09:13pm 01 Jan 2019
Copy link to clipboard 
Print this post

  Quote  SDA is the pin labelled A4, SCL is A5

Page one of this thread has a table of pin outs

  Quote  NULL, 0,"D5"}, // pin 29 I2C-SCL

  Quote  NULL, 0,"D4"}, // pin 30 I2C-SDA

So is it A4 and A5 or D4 and D5

  Quote  The L4 32 pin chip doesn't have a separate pin for battery power.

So how is the RTC powered when the board is shut down.

I found another Pin Out that says D4 and D5 so I suppose that is it.Edited by palcal 2019-01-03
"It is better to be ignorant and ask a stupid question than to be plain Stupid and not ask at all"
 
TassyJim

Guru

Joined: 07/08/2011
Location: Australia
Posts: 6220
Posted: 09:52pm 01 Jan 2019
Copy link to clipboard 
Print this post

D4 = data
D5 = clock

The L4 32 pinner is designed to put in sleep and keep the power to the chip on for the RTC.
I do prefer the versions with a dedicated RTC backup pin.

Jim
VK7JH
MMedit
 
palcal

Guru

Joined: 12/10/2011
Location: Australia
Posts: 1965
Posted: 10:08pm 01 Jan 2019
Copy link to clipboard 
Print this post

That is how I have connected.
On the card that came with the board it says Green LED blinks, my green LED does not blink. I tried removing the jumper from D3 to GND made no difference.
"It is better to be ignorant and ask a stupid question than to be plain Stupid and not ask at all"
 
TassyJim

Guru

Joined: 07/08/2011
Location: Australia
Posts: 6220
Posted: 11:09pm 01 Jan 2019
Copy link to clipboard 
Print this post

  palcal said  
On the card that came with the board it says Green LED blinks, my green LED does not blink. I tried removing the jumper from D3 to GND made no difference.

I assume you are talking about the NUCLEO board.
The jumper and flashing light is only with the initial firmware. Not reliant once MMBasic is loaded.

Jim
VK7JH
MMedit
 
matherp
Guru

Joined: 11/12/2012
Location: United Kingdom
Posts: 10068
Posted: 08:20am 02 Jan 2019
Copy link to clipboard 
Print this post

  Quote  On the card that came with the board it says Green LED blinks


That is with the originally loaded demo firmware. D13 is just a standard I/O pin when the Armmite firmware is loaded.

  Quote  So is it A4 and A5 or D4 and D5


Sorry typo, D4=SDA, D5=SCLEdited by matherp 2019-01-03
 
lew247

Guru

Joined: 23/12/2015
Location: United Kingdom
Posts: 1702
Posted: 06:10pm 02 Jan 2019
Copy link to clipboard 
Print this post

Is there a PDF for this chip yet?
I've got a use for it where it would be ideal as it's such low power and I would only need a couple of pins so there isn't much point in buying a full development board just for it.
Other than power I'd only need SPI and 5 other pins
 
OA47

Guru

Joined: 11/04/2012
Location: Australia
Posts: 982
Posted: 12:51am 05 Jan 2019
Copy link to clipboard 
Print this post

Should I be able to save embedded fonts into the library area?




Not sure which commands are supported by the L4.

OA47
 
palcal

Guru

Joined: 12/10/2011
Location: Australia
Posts: 1965
Posted: 01:08am 05 Jan 2019
Copy link to clipboard 
Print this post

FRom Page one:
  Quote  Missing:
all drawing, font and TFT capability
obsolete commands and functions as per MM2 manual
RANDOMIZE command, STM32 has hardware random number generator so not needed
LIBRARY command

Added:
DISTANCE command as per earlier versions of MM2
DHT22 command as per earlier versions of MM2
LONGSTRING commands and functions as per MMX/ARMMITE H7
WS2812 command as per MMX/ARMMITE H7
DAC command as per ARMMITE H7
DAY$ function as per ARMMITE H7
SPI2 commands and functions as per MM+/MMX/ARMMITE H7

Different:
TIME$ command sets the value from the RTC
TIME$ function returns the value in the RTC
DATE$ command sets the value from the RTC
DATE$ function returns the value in the RTC
MM.DEVICE$ returns "ARMMITE L4"
Edited by palcal 2019-01-06
"It is better to be ignorant and ask a stupid question than to be plain Stupid and not ask at all"
 
OA47

Guru

Joined: 11/04/2012
Location: Australia
Posts: 982
Posted: 01:37am 05 Jan 2019
Copy link to clipboard 
Print this post

Thanks Palcal, I did read through that description this morning but missed the "LIBRARY command" bit at the end. I was a little bit confused when Peter posted his 7 segment clock code for the e-Paper display in an earlier post and used font 8 without it in his program code.

OA47
 
lizby
Guru

Joined: 17/05/2016
Location: United States
Posts: 3313
Posted: 05:26pm 19 Feb 2019
Copy link to clipboard 
Print this post

I've looked through this and other Armmite L4 threads, and while I may well have missed it, I didn't note anything which correlated the mmbasic pins to the text in the first post to the NUCLEO-L432KC (other than by comparing the D# and A# designations). This is my first pass at producing an image:



I have a number of questions.

Which are console RX & TX?

What is A7?

What are pin 23 SWDIO and pin 24 SWCLK? Are they rightly assigned to D7 & D8?

Are there errors or assigned usage for other pins?

Are there count pins?
PicoMite, Armmite F4, SensorKits, MMBasic Hardware, Games, etc. on fruitoftheshed
 
matherp
Guru

Joined: 11/12/2012
Location: United Kingdom
Posts: 10068
Posted: 07:47pm 19 Feb 2019
Copy link to clipboard 
Print this post

  Quote  Which are console RX & TX?

PA2 is console TX (broken out as A7)
PA15 is console RX (not broken out on Nucleo)

  Quote  What are pin 23 SWDIO and pin 24 SWCLK? Are they rightly assigned to D7 & D8?

No, these pins are not broken out on the Nucleo
D7 and D8 are the 32KHz xtal pins so not usable

The Nucleo manual is the source for the pin allocation of D0 to 12 and A0 to 7

All MMBasic special purpose pins by chip size are given below:

The syntax : INT1PIN (HAS_32PINS ? 6 : (HAS_48PINS ? 10 : 14)) //PA0

means INT1PIN is on pin 6 for 32-pin, pin 10 for 48 pin and pin 14 for 64 pin and uses PA0 in all cases. INT pins are the COUNT pins

INT1PIN (HAS_32PINS ? 6 : (HAS_48PINS ? 10 : 14)) //PA0
INT2PIN (HAS_32PINS ? 22 : (HAS_48PINS ? 33 : 45)) //PA12
INT3PIN (HAS_32PINS ? 15 : (HAS_48PINS ? 19 : 27)) //PB1
IRPIN (HAS_32PINS ? 6 : (HAS_48PINS ? 10 : 14)) //PA0
//COUNT5 (HAS_32PINS ? 11 : 15) //PA5
// I2C pin numbers
P_I2C_SCL (HAS_32PINS ? 29 : (HAS_48PINS ? 42 : 58)) //PB6
P_I2C_SDA (HAS_32PINS ? 30 : (HAS_48PINS ? 43 : 59)) //PB7

// Console pin numbers
CONSOLE_RX_PIN (HAS_32PINS ? 25 : (HAS_48PINS ? 13 : 17)) //PA15/PA3/PA3 USART2
CONSOLE_TX_PIN (HAS_32PINS ? 8 : (HAS_48PINS ? 12 : 16)) //PA2
// COMx: port pin numbers
COM1_TX_PIN (HAS_32PINS ? 19 : (HAS_48PINS ? 30 : 42)) //PA9 USART1
COM1_RX_PIN (HAS_32PINS ? 20 : (HAS_48PINS ? 31 : 43)) //PA10
COM1_EN_PIN (HAS_32PINS ? 22 : (HAS_48PINS ? 33 : 45)) //PA12

COM2_TX_PIN (HAS_32PINS ? 0 : (HAS_48PINS ? 21 : 29)) //PB10 USART3
COM2_RX_PIN (HAS_32PINS ? 0 : (HAS_48PINS ? 22 : 30)) //PB11

// SPI pin numbers
SPI_CLK_PIN (HAS_32PINS ? 7 : (HAS_48PINS ? 11 : 15)) //PA1
SPI_INP_PIN (HAS_32PINS ? 12 : (HAS_48PINS ? 16 : 22)) //PA6
SPI_OUT_PIN (HAS_32PINS ? 13 : (HAS_48PINS ? 17 : 23)) //PA7

SPI2_CLK_PIN (HAS_32PINS ? 26 : (HAS_48PINS ? 39 : 55)) //PB3
SPI2_INP_PIN (HAS_32PINS ? 27 : (HAS_48PINS ? 40 : 56)) //PB4
SPI2_OUT_PIN (HAS_32PINS ? 28 : (HAS_48PINS ? 41 : 57)) //PB5

SPI3_CLK_PIN (HAS_32PINS ? 0 : (HAS_48PINS ? 26 : 34)) //PB13
SPI3_INP_PIN (HAS_32PINS ? 0 : (HAS_48PINS ? 27 : 35)) //PB14
SPI3_OUT_PIN (HAS_32PINS ? 0 : (HAS_48PINS ? 28 : 36)) //PB15

// DAC pin numbers
DAC_1_PIN (HAS_32PINS ? 10 : (HAS_48PINS ? 14 : 20)) //PA4
DAC_2_PIN (HAS_32PINS ? 11 : (HAS_48PINS ? 15 : 21)) //PA5
//
// PWM pin numbers
PWM_CH1_PIN (HAS_32PINS ? 18 : (HAS_48PINS ? 29 : 41)) //PA8 - PWM1A
PWM_CH2_PIN (HAS_32PINS ? 21 : (HAS_48PINS ? 32 : 44)) //PA11 - PWM1B
PWM_CH3_PIN (HAS_32PINS ? 19 : (HAS_48PINS ? 30 : 42)) //PA9 - PWM1C
PWM_CH4_PIN (HAS_32PINS ? 20 : (HAS_48PINS ? 31 : 43)) //PA10 - PWM1D
PWM_CH5_PIN (HAS_32PINS ? 9 : (HAS_48PINS ? 45 : 61)) //PA3/PB8/PB8 - PWM2A
Edited by matherp 2019-02-21
 
lizby
Guru

Joined: 17/05/2016
Location: United States
Posts: 3313
Posted: 11:46pm 19 Feb 2019
Copy link to clipboard 
Print this post

Ok, so I think this is right:



So basically, if you have serial i/o, a display on SPI, a winbond flash file system on SPI2, and I2C, you have 9 i/os left (not counting additional you need for the SPI devices). If you can use an I2C display, you have 3+ more available.


PicoMite, Armmite F4, SensorKits, MMBasic Hardware, Games, etc. on fruitoftheshed
 
matherp
Guru

Joined: 11/12/2012
Location: United Kingdom
Posts: 10068
Posted: 07:52am 20 Feb 2019
Copy link to clipboard 
Print this post

  Quote  a display on SPI


in-built display drivers share SPI2
 
     Page 7 of 8    
Print this page
The Back Shed's forum code is written, and hosted, in Australia.
© JAQ Software 2025