Home
JAQForum Ver 19.8.18
Log In or Join  
Active Topics
Local Time 08:30 23 Sep 2019 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 F4: programming the firmware

     Page 9 of 10    
Author Message
lizby
Guru

Joined: 17/05/2016
Location: United States
Posts: 612
Posted: 12:19am 31 Jul 2019
Copy link to clipboard 

PM sent.

  matherp said  
  Quote  Have you patched your displays to use 1963_PWM? This is quite important as it stops there being a current surge to the backlight when the Micromite is powered on.


I saw that you mentioned that, but didn't understand it. I see that it's also in the H7 manual: "SSD1963 displays should be configured for backlight control using 1963_PWM. Controlling the backlight using an Armmite H7 pin like the MM+ is not supported."

And now I see that there are pads marked for it, with a 0V resistor on the LED_A pads. I'll fix it. Thanks.
 
lizby
Guru

Joined: 17/05/2016
Location: United States
Posts: 612
Posted: 03:19pm 31 Jul 2019
Copy link to clipboard 

  lizby said  I'll fix it

I can't say that went well. I managed to lift a pad on the 1963_PWM link on the 4.3" panel. With the 7" panel, with the adapter jumper on BL, the panel started off very dim. It increased in brightness up to BACKLIGHT 70, but still dimmer than it had been. BACKLIGHT 80 made it dimmer still, and BACKLIGHT 99 made it almost invisible.

That was with the adapter 5V disconnected. There was little difference when I plugged adapter 5V pin into 3V3 or 5V on the F4. Switch the adapter jumper to 5V and the adapter 5V pin to 3V3 and all is nice and bright as originally.

The 4.3" panel with no jumpers on the panel's backlight settings works fine in this same configuration (with OPTION LCDPANEL changed, of course).

GUI CALIBRATE still doesn't work on the 7" panel, but does on the 4.3". GUI CALIBRATE had worked on the H7--I'll try that again. It's certainly possible that I damaged the panel.
 
matherp
Guru

Joined: 11/12/2012
Location: United Kingdom
Posts: 2900
Posted: 03:37pm 31 Jul 2019
Copy link to clipboard 

As with the MM+, all my ports expect SSD19623 displays to have the backlight jumper in the 1963_PWM position. The backlight command in the MM firmware sends commands to the SSD which itself runs a PWM output which drives the backlight circuitry.

The BL pin from the STM32F407 is a 1KHz PWM which was configured specifically for the ILI9341 display. The output is inverted for the SSD1963 wiring if the SSD is left in the LED_A configuration so BACKLIGHT 0 will give the brightest output for a SSD. The LED_A pin is a logic level on the SSD displays - it doesn't power the backlight. The power comes either from the 3.3V pin (4.3" and 5") or the 5V pin which is only connected on the 7"
 
disco4now

Guru

Joined: 18/12/2014
Location: Australia
Posts: 374
Posted: 11:38am 12 Aug 2019
Copy link to clipboard 

Hi Peter,
I am trying to access the pins on the LCD header, but they all seem to be invalid when trying to access with SETPIN etc.
e.g.

setpin pd14,dout
Error: Pin 61 is invalid
>

The pin definitions previously posted seem to support this as they show as unused.
I was starting to play with writing a BASIC LCD DRIVER but have fallen at the first hurdle.
Would it be possible to make the following pins available,
36,61,62,81,82,38-46,55-57,85,86,60,88

Regards
Gerry
PS I did OPTION LCDPANEL DISABLE, but this did not help.

  matherp said  

All pins:

const struct s_PinDef PinDef100[NBR_PINS_100CHIP + 1]={
{ NULL, 0, PUNUSED , NULL, 0}, // pin 0
{ GPIOE, GPIO_PIN_2, DIGITAL_IN | DIGITAL_OUT , NULL, 0}, // pin 1 IR
{ GPIOE, GPIO_PIN_3, DIGITAL_IN | DIGITAL_OUT , NULL, 0}, // pin 2 Count 3/KEY1
{ GPIOE, GPIO_PIN_4, DIGITAL_IN | DIGITAL_OUT , NULL, 0}, // pin 3 Count 4/KEY0
{ GPIOE, GPIO_PIN_5, DIGITAL_IN | DIGITAL_OUT , NULL, 0}, // pin 4 PWM-3A
{ GPIOE, GPIO_PIN_6, DIGITAL_IN | DIGITAL_OUT , NULL, 0}, // pin 5 PWM-3B
{ NULL, 0, PUNUSED , NULL, 0}, // pin 6 VBAT
{ GPIOC, GPIO_PIN_13, DIGITAL_IN | DIGITAL_OUT, NULL, 0}, // pin 7
{ NULL, 0, PUNUSED , NULL, 0}, // pin 8 OSC32_IN
{ NULL, 0, PUNUSED , NULL, 0}, // pin 9 OSC32_OUT
{ NULL, 0, PUNUSED , NULL, 0}, // pin 10 VSS
{ NULL, 0, PUNUSED , NULL, 0}, // pin 11 VDD
{ NULL, 0, PUNUSED , NULL, 0}, // pin 12 OSC8_IN
{ NULL, 0, PUNUSED , NULL, 0}, // pin 13 OSC8_OUT
{ NULL, 0, PUNUSED , NULL, 0}, // pin 14 NRST
{ GPIOC, GPIO_PIN_0, DIGITAL_IN | DIGITAL_OUT | ANALOG_IN , ADC1, ADC_CHANNEL_10}, // pin 15
{ GPIOC, GPIO_PIN_1, DIGITAL_IN | DIGITAL_OUT | ANALOG_IN , ADC2, ADC_CHANNEL_11}, // pin 16
{ GPIOC, GPIO_PIN_2, DIGITAL_IN | DIGITAL_OUT | ANALOG_IN , ADC3, ADC_CHANNEL_12}, // pin 17
{ GPIOC, GPIO_PIN_3, DIGITAL_IN | DIGITAL_OUT | ANALOG_IN , ADC1, ADC_CHANNEL_13}, // pin 18
{ NULL, 0, PUNUSED , NULL, 0}, // pin 19 VDD
{ NULL, 0, PUNUSED , NULL, 0}, // pin 20 VSSA
{ NULL, 0, PUNUSED , NULL, 0}, // pin 21 VREF+
{ NULL, 0, PUNUSED , NULL, 0}, // pin 22 VDDA
{ GPIOA, GPIO_PIN_0, DIGITAL_IN | DIGITAL_OUT | ANALOG_IN , ADC1, ADC_CHANNEL_0}, // pin 23 COM3-TX/COUNT-0/WK_UP
{ GPIOA, GPIO_PIN_1, DIGITAL_IN | DIGITAL_OUT | ANALOG_IN , ADC1, ADC_CHANNEL_1}, // pin 24 COM3-RX
{ GPIOA, GPIO_PIN_2, DIGITAL_IN | DIGITAL_OUT | ANALOG_IN , ADC1, ADC_CHANNEL_2}, // pin 25 COM4-TX
//
{ GPIOA, GPIO_PIN_3, DIGITAL_IN | DIGITAL_OUT | ANALOG_IN , ADC1, ADC_CHANNEL_3}, // pin 26 COM4-RX
{ NULL, 0, PUNUSED , NULL, 0}, // pin 27 VSS
{ NULL, 0, PUNUSED , NULL, 0}, // pin 28 VDD
{ NULL, 0, PUNUSED , NULL, 0}, // pin 29 DAC-1
{ NULL, 0, PUNUSED , NULL, 0}, // pin 30 DAC-2
{ GPIOA, GPIO_PIN_6, DIGITAL_IN | DIGITAL_OUT | ANALOG_IN , ADC1, ADC_CHANNEL_6}, // pin 31 PWM-1A +LED-D2
{ GPIOA, GPIO_PIN_7, DIGITAL_IN | DIGITAL_OUT | ANALOG_IN , ADC1, ADC_CHANNEL_7}, // pin 32 PWM-1B +LED-D3
{ GPIOC, GPIO_PIN_4, DIGITAL_IN | DIGITAL_OUT | ANALOG_IN , ADC2, ADC_CHANNEL_14}, // pin 33
{ GPIOC, GPIO_PIN_5, DIGITAL_IN | DIGITAL_OUT | ANALOG_IN , ADC2, ADC_CHANNEL_15}, // pin 34 T_IRQ
{ GPIOB, GPIO_PIN_0, DIGITAL_IN | DIGITAL_OUT | ANALOG_IN , ADC1, ADC_CHANNEL_8}, // pin 35 PWM-1C/F_CS
{ NULL, 0, PUNUSED , NULL, 0}, // pin 36 LCD_BL
{ GPIOB, GPIO_PIN_2, DIGITAL_IN | DIGITAL_OUT , NULL, 0}, // pin 37
{ NULL, 0, PUNUSED , NULL, 0}, // pin 38 FSMC_D4
{ NULL, 0, PUNUSED , NULL, 0}, // pin 39 FSMC_D5
{ NULL, 0, PUNUSED , NULL, 0}, // pin 40 FSMC_D6
{ NULL, 0, PUNUSED , NULL, 0}, // pin 41 FSMC_D7
{ NULL, 0, PUNUSED , NULL, 0}, // pin 42 FSMC_D8
{ NULL, 0, PUNUSED , NULL, 0}, // pin 43 FSMC_D9
{ NULL, 0, PUNUSED , NULL, 0}, // pin 44 FSMC_D10
{ NULL, 0, PUNUSED , NULL, 0}, // pin 45 FSMC_D11
{ NULL, 0, PUNUSED , NULL, 0}, // pin 46 FSMC_D12
{ GPIOB, GPIO_PIN_10, DIGITAL_IN | DIGITAL_OUT , NULL, 0}, // pin 47 I2C2-SCL
{ GPIOB, GPIO_PIN_11, DIGITAL_IN | DIGITAL_OUT , NULL, 0}, // pin 48 I2C2-SDA
{ NULL, 0, PUNUSED , NULL, 0}, // pin 49 VCAP
{ NULL, 0, PUNUSED , NULL, 0}, // pin 50 VDD
//
{ GPIOB, GPIO_PIN_12, DIGITAL_IN | DIGITAL_OUT , NULL, 0}, // pin 51 T_CS
{ GPIOB, GPIO_PIN_13, DIGITAL_IN | DIGITAL_OUT , NULL, 0}, // pin 52 SPI2-CLK
{ GPIOB, GPIO_PIN_14, DIGITAL_IN | DIGITAL_OUT , NULL, 0}, // pin 53 SPI2-IN
{ GPIOB, GPIO_PIN_15, DIGITAL_IN | DIGITAL_OUT , NULL, 0}, // pin 54 SPI2-OUT
{ NULL, 0, PUNUSED , NULL, 0}, // pin 55 FSMC_D13
{ NULL, 0, PUNUSED , NULL, 0}, // pin 56 FSMC_D14
{ NULL, 0, PUNUSED , NULL, 0}, // pin 57 FSMC_D15
{ GPIOD, GPIO_PIN_11, DIGITAL_IN | DIGITAL_OUT , NULL, 0}, // pin 58 Drive_VBUS_FS
{ GPIOD, GPIO_PIN_12, DIGITAL_IN | DIGITAL_OUT , NULL, 0}, // pin 59 PWM-2A
{ NULL, 0, PUNUSED , NULL, 0}, // pin 60 FSMC_A18
{ NULL, 0, PUNUSED , NULL, 0}, // pin 61 FSMC_D0
{ NULL, 0, PUNUSED , NULL, 0}, // pin 62 FSMC_D1
{ GPIOC, GPIO_PIN_6, DIGITAL_IN | DIGITAL_OUT, NULL, 0}, // pin 63 COM2-TX
{ GPIOC, GPIO_PIN_7, DIGITAL_IN | DIGITAL_OUT, NULL, 0}, // pin 64 COM2-RX
{ NULL, 0, PUNUSED , NULL, 0}, // pin 65 SDIO_D0
{ NULL, 0, PUNUSED , NULL, 0}, // pin 66 SDIO_D1
{ GPIOA, GPIO_PIN_8, DIGITAL_IN | DIGITAL_OUT , NULL, 0}, // pin 67
{ GPIOA, GPIO_PIN_9, DIGITAL_IN | DIGITAL_OUT , NULL, 0}, // pin 68 COM1-TX
{ GPIOA, GPIO_PIN_10, DIGITAL_IN | DIGITAL_OUT , NULL, 0}, // pin 69 COM1-RX
// { NULL, 0, PUNUSED , NULL, 0}, // pin 68 CONSOLE-TX
// { NULL, 0, PUNUSED , NULL, 0}, // pin 69 CONSOLE-51,34X
{ NULL, 0, PUNUSED , NULL, 0}, // pin 70 USB-DM
{ NULL, 0, PUNUSED , NULL, 0}, // pin 71 USB-DP
{ GPIOA, GPIO_PIN_13, DIGITAL_IN | DIGITAL_OUT , NULL, 0}, // pin 72 SWDIO
{ NULL, 0, PUNUSED , NULL, 0}, // pin 73 VCAP
{ NULL, 0, PUNUSED , NULL, 0}, // pin 74 VSS
{ NULL, 0, PUNUSED , NULL, 0}, // pin 75 VDD
//
{ GPIOA, GPIO_PIN_14, DIGITAL_IN | DIGITAL_OUT , NULL, 0}, // pin 76 SWCLK
{ GPIOA, GPIO_PIN_15, DIGITAL_IN | DIGITAL_OUT , NULL, 0}, // pin 77 KBD_CLK
{ NULL, 0, PUNUSED , NULL, 0}, // pin 78 SDIO_D2
{ GPIOC, GPIO_PIN_11, DIGITAL_IN | DIGITAL_OUT, NULL, 0}, // pin 79 SDIO_D3
{ NULL, 0, PUNUSED , NULL, 0}, // pin 80 SDIO_CK
{ NULL, 0, PUNUSED , NULL, 0}, // pin 81 FSMC_D2
{ NULL, 0, PUNUSED , NULL, 0}, // pin 82 FSMC_D3
{ NULL, 0, PUNUSED , NULL, 0}, // pin 83 SDIO_CMD
{ GPIOD, GPIO_PIN_3, DIGITAL_IN | DIGITAL_OUT , NULL, 0}, // pin 84 KBD_DATA
{ NULL, 0, PUNUSED , NULL, 0}, // pin 85 FSMC_NOE
{ NULL, 0, PUNUSED , NULL, 0}, // pin 86 FSMC_NWE
{ GPIOD, GPIO_PIN_6, DIGITAL_IN | DIGITAL_OUT , NULL, 0}, // pin 87
{ NULL, 0, PUNUSED , NULL, 0}, // pin 88 FSMC_NE1
{ GPIOB, GPIO_PIN_3, DIGITAL_IN | DIGITAL_OUT , NULL, 0}, // pin 89 SPI_CLK
{ GPIOB, GPIO_PIN_4, DIGITAL_IN | DIGITAL_OUT , NULL, 0}, // pin 90 SPI_IN
{ GPIOB, GPIO_PIN_5, DIGITAL_IN | DIGITAL_OUT , NULL, 0}, // pin 91 SPI-OUT
{ GPIOB, GPIO_PIN_6, DIGITAL_IN | DIGITAL_OUT , NULL, 0}, // pin 92 I2C-SCL/NRF_CE
{ GPIOB, GPIO_PIN_7, DIGITAL_IN | DIGITAL_OUT , NULL, 0}, // pin 93 I2C-SDA/NRF_CS
{ NULL, 0, PUNUSED , NULL, 0}, // pin 94 BOOT0
{ GPIOB, GPIO_PIN_8, DIGITAL_IN | DIGITAL_OUT , NULL, 0}, // pin 95 PWM-2B
{ GPIOB, GPIO_PIN_9, DIGITAL_IN | DIGITAL_OUT , NULL, 0}, // pin 96 PWM-2C
{ GPIOE, GPIO_PIN_0, DIGITAL_IN | DIGITAL_OUT , NULL, 0}, // pin 97
{ GPIOE, GPIO_PIN_1, DIGITAL_IN | DIGITAL_OUT , NULL, 0}, // pin 98 COUNT 1
{ NULL, 0, PUNUSED , NULL, 0}, // pin 99 VSS
{ NULL, 0, PUNUSED , NULL, 0}, // pin 100 VDD
};

Edited 2019-08-12 21:42 by disco4now
 
matherp
Guru

Joined: 11/12/2012
Location: United Kingdom
Posts: 2900
Posted: 11:51am 12 Aug 2019
Copy link to clipboard 

The LCD pins are always unavailable to MMBasic. They are configured when you enable an LCD - ILI9341_16 or SSD1963_n_16. The Armmite F4 uses the FSMC port on the processor which maps the display as an area of memory.
 
disco4now

Guru

Joined: 18/12/2014
Location: Australia
Posts: 374
Posted: 12:12pm 12 Aug 2019
Copy link to clipboard 

OK,understand.
I was getting excited about this
800*480 IPS display as the other IPS one is very clear.

$AU22 here

I made an adaptor and plugged into the F4. Touch calibrated (blind) and seem to work, and BACKLIGHT 0/100 turned the backlight on off.

I will try to get it to go as 8bit on an MM+

Gerry
 
Decoy
Regular Member

Joined: 02/08/2019
Location: Denmark
Posts: 44
Posted: 05:24pm 12 Aug 2019
Copy link to clipboard 

I just tried this, works great. Thanks for the awesome instruction!!

I am just sad that I cannot get VGA output (or composite - even B&W would be great) output, or keyboard input.
Edited 2019-08-13 03:25 by Decoy
 
lizby
Guru

Joined: 17/05/2016
Location: United States
Posts: 612
Posted: 09:44pm 12 Aug 2019
Copy link to clipboard 

I'm baffled by a problem on a PCB I designed for the F4. Among other things it is set up to read 8 DS18B20s on pins 1,4,5,7,15,16,17,18.

I tested each of these pins successfully with a single DS18B20 3-pin module with built-in 4K7 resistor.

I soldered up my board with a bussed 4K7 resistor array. All the temperatures read fine, but I get "SD card not present" if I issue the FILES command. I tracked it down, and if I don't connect pin 7 (PC13), the other temperatures work and the SD card also works.

I went back and checked with the single DS18B20 module. Each TEMPR command works (pins 1,4,5,7,15,16,17,18), and FILES works after each one.

I wondered if it might be a power draw, but it sits between 65 and 69 mA.

I can find another pin to use besides 7, but I wonder what the reason is for this behavior? (I see that pin 7 has for "Function" "Digital, 3mA total for PC13-PC15", but I'm not sure how this would be related.)



Edited 2019-08-13 07:46 by lizby
 
matherp
Guru

Joined: 11/12/2012
Location: United Kingdom
Posts: 2900
Posted: 08:39am 13 Aug 2019
Copy link to clipboard 

  Quote  but I wonder what the reason is for this behavior


I suspect some sort of crosstalk internal to the chip between PC13 and PC12 (SD-CLK). I had huge problems getting the SDcard to work reliably. Eventually I had to use 1-bit SDIO rather than the faster 4-bit and slow the SDIO clock as I was seeing this sort of problem. Could be an issue with the ST driver or, as I suspect, some sort of hardware crosstalk.
 
matherp
Guru

Joined: 11/12/2012
Location: United Kingdom
Posts: 2900
Posted: 12:25pm 13 Aug 2019
Copy link to clipboard 

Minor update to fix bug in ARC command


ArmmiteF4.zip
 
SWA-Guy
Newbie

Joined: 01/02/2019
Location: Germany
Posts: 1
Posted: 02:44pm 13 Aug 2019
Copy link to clipboard 

Hi guys,

I can confirm lizbys problem with the 1-wire communication on PIN PC13. I use a DHT22 and sometimes I have no connection to the sd-card. If I disconnect the DHT22 the communcation to the sd-card directly works.

Greeting from Germany

Juergen
 
lizby
Guru

Joined: 17/05/2016
Location: United States
Posts: 612
Posted: 04:26pm 13 Aug 2019
Copy link to clipboard 

  SWA-Guy said  I can confirm lizby's problem with ... PIN PC13
  matherp said  
  lizby said  but I wonder what the reason is for this behavior


I suspect some sort of crosstalk internal to the chip between PC13 and PC12 (SD-CLK)

Thanks for the confirmation (and welcome to the forum) and thanks for the explanation (even if the root remains a mystery). Mysteries do abound--I'm glad MMBasic has relatively few of them, thanks to the efforts of Peter and Geoff.
Edited 2019-08-14 02:27 by lizby
 
lizby
Guru

Joined: 17/05/2016
Location: United States
Posts: 612
Posted: 03:00pm 24 Aug 2019
Copy link to clipboard 

When I hook LEDs up to pins 92,93,89,91,87,84,77,67, two--89 and 77 (PB3 and PA15)-- are on weakly. They respond normally (with brightness corresponding to the other pins) to, e.g., PIN(89)=1 and PIN(89)=0.

What am I seeing here with these pins? After setting them low, "NEW" brings them back on weakly.

Are all of these pins OK to use digitally? Is there a way to have 89 and 77 not doing whatever they are doing upon power-up?




Edited 2019-08-25 01:05 by lizby
 
matherp
Guru

Joined: 11/12/2012
Location: United Kingdom
Posts: 2900
Posted: 10:07pm 24 Aug 2019
Copy link to clipboard 

PB3 and PA15 have 10K pullups on the PCB. Remove R1 and R3 if you don't want them
 
lizby
Guru

Joined: 17/05/2016
Location: United States
Posts: 612
Posted: 03:03pm 25 Aug 2019
Copy link to clipboard 

  matherp said  PB3 and PA15 have 10K pullups on the PCB. Remove R1 and R3 if you don't want them

Thanks. That did the trick.

option base 1: dim integer i,p(8)=(92,93,89,91,87,84,77,67)
for i=1 to 8: setpin p(i),dout: pin(p(i))=1: pause 500: next i
for i=1 to 8: pin(p(i))=0: pause 500: next i
Edited 2019-08-26 01:03 by lizby
 
Chopperp

Guru

Joined: 03/01/2018
Location: Australia
Posts: 509
Posted: 12:22am 28 Aug 2019
Copy link to clipboard 

  matherp said  
  Quote  Otherwise it looks like I have a dud card/chip


One last try: This version slows down flash access and disables cacheing. It is about 20% slower but does it work?

2019-05-25_213711_ArmmiteF4.zip"


Hi matherp

I also have problems with one of my F4 boards with the USB OK in programming but not for normal the normal connection. (Device unrecognised)

I ended up trying the above version first & it DID work for me. Great!!!

I then tried the first version but that didn't work. (2019-05-25_191158_ArmmiteF4.zip )

Reloading the second version brought it back to life.

I don't suppose that there has been any updates on the later version has there?  

I uploaded a small program & it looks like the board will be usable for this purpose so all is not lost if no updates are available.

Brian
ChopperP
 
TassyJim

Guru

Joined: 07/08/2011
Location: Australia
Posts: 3080
Posted: 06:22am 29 Aug 2019
Copy link to clipboard 

My F4 boards arrived and I have had a chance to play today.
I had to upgrade my STMCube software before it was recognised but after that, it was plane sailing thanks to your clear instructions.

I used the 13/8/19 firmware.
File system seems to work well using MMEdit file manager.

One oddity.
The first time I plugged the boards in after loading the firmware, the device was not recognised but unplugging and reinserting and all was well. This happened for both boards.

Jim
Edited 2019-08-29 16:32 by TassyJim
It all started with the ZX81....
VK7JH
http://www.c-com.com.au/MMedit.htm
 
Chopperp

Guru

Joined: 03/01/2018
Location: Australia
Posts: 509
Posted: 07:09am 29 Aug 2019
Copy link to clipboard 

  TassyJim said   One oddity.
The first time I plugged the boards in after loading the firmware, the device was not recognised but unplugging and reinserting and all was well. This happened for both boards.
Jim


It's when the boards aren't recognised the second time you really start to worry.
Have fun playing. Be careful with the unsupported end of the Panel. They crack easily & destroy the F4 board.

I just uploaded another small program on my troublesome board mentioned in my previous post. All OK.
COM3 OK on Tx & COM4 OK on GPS Rx.

Did some time checks overnight & today on both the RTC (not powered) & also running. Also OK.
ChopperP
 
CaptainBoing

Guru

Joined: 07/09/2016
Location: United Kingdom
Posts: 955
Posted: 11:44am 29 Aug 2019
Copy link to clipboard 

  TassyJim said  

One oddity.
The first time I plugged the boards in after loading the firmware, the device was not recognised but unplugging and reinserting and all was well. This happened for both boards.

Jim


This happens with both my boards all the time and has been reported by others - it seems to be a toggle... first time ok, then not, then next ok...  I seem to remember it was something to do with the little "break-off" board at the top (can't remember its name) and its USB device. If you remove the jumpers (J6?) and go straight onto the console pins with your own USB adapter is works fine.

hth
 
lizby
Guru

Joined: 17/05/2016
Location: United States
Posts: 612
Posted: 05:32pm 29 Aug 2019
Copy link to clipboard 

Upon power-up, pins 31 and 32 (PA6--Digital, Analog, ADC1, ADC_CHANNEL_6, PWM1A, TIM3_CH1, LED-D2--and PA7--Digital, Analog, ADC1, ADC_CHANNEL_7, PWM1B, TIM3_CH2, LED-D3) have voltages around 1.78.

The LEDs they're associated with, D2 and D3 are dimly lit. If I do
SETPIN 31,DOUT: SETPIN 32,DOUT
then the LEDs show inverted values: PIN(31)=0: PIN(32)=0 turns them on and PIN(31)=1: PIN(32)=1 turns them off.

I'd really like to use these a digital inputs.

If I do SETPIN 31,DIN: SETPIN 32,DIN the voltage are back at 1.78. Is there a way I can deal with this so that I can easily enough use them as digital inputs?
Edited 2019-08-30 03:33 by lizby
 
     Page 9 of 10    
© JAQ Software 2019